The family’s MCP servers · Escouade documentation

Each application of the family has its MCP server, at its own address, and Escouade has three. Your assistant connects with the address alone; signing in goes through your Escouade account, and the assistant acts with your rights, in the organisation you choose.

The addresses

Application	Server	Address	For
Escouade	Read	`https://app.escouade.io/mcp`	Searching, reading and summarising records, documents and emails.
Escouade	Write	`https://app.escouade.io/mcp/ecriture`	Creating and changing records, sending an email, in your name.
Escouade	Integrator	`https://app.escouade.io/mcp/integration`	Setting up the model, the objects and the workspace. From Pro.
Meet		`https://meet.escouade.io/mcp`	Reading your meetings, minutes, actions and transcriptions; preparing an action you confirm.
Mail	For assistants	`https://mail.escouade.io/mcp`	Your mailboxes, threads, drafts and campaigns, from Claude or ChatGPT.
Mail	For agents	`https://api.subagent.fr/mcp`	A mailbox of its own for an autonomous agent, with an `sak_…` key.
Social	A space	`https://social.escouade.io/w/<space>/mcp`	Preparing, getting approval, reading a brand’s results.
Social	A group	`https://social.escouade.io/g/<group>/mcp`	The same tools, brand by brand.
Tools		`https://tools.escouade.io/mcp`	Opening a tool, reading the Library, dropping a file into it.

The account’s Connectors page, on https://compte.escouade.io, gives the same addresses, and says which ones your size opens.

Connecting a server

In Claude (claude.ai, and the desktop app, which picks up the account’s connectors):

Open Claude’s connectors, then "Add custom connector".
Give it a name and paste the address.
"Connect": sign in with your Escouade account, choose the organisation, allow.

In ChatGPT: in the settings, the connectors, with developer mode switched on; create a connector with the address and OAuth authentication, then sign in with your Escouade account.

In Claude Code:

Terminal

claude mcp add --transport http escouade https://app.escouade.io/mcp
claude mcp add --transport http escouade-meet https://meet.escouade.io/mcp
claude mcp add --transport http escouade-tools https://tools.escouade.io/mcp

then /mcp in a session to sign in to each.

A connector only sees what your rights open, and what the organisation’s size includes.

What each server can do

Escouade: escouade_trouver, escouade_consulter, escouade_relations… for reading; escouade_ecrire, escouade_envoyer… for writing; escouade_parametrer, escouade_superviser… for the integrator. See Escouade’s MCP servers.
Meet: twenty-one tools, including search_meetings, get_report, ask_meetings, and five that prepare an action to confirm. See Meet for developers.
Mail: Mail’s operations (send_email, list_threads, approve_message…), the same through MCP and through the HTTP API. See the Mail tool reference (in French).
Social: prepare, submit, decide, read the calendar and the results. See Social’s MCP server.
Tools: tools_catalogue, tools_ouvrir, tools_documents, tools_dossiers, tools_enregistrer. See Escouade Tools.

What holds for all of them

One sign-in: the Escouade account’s. The assistant never sees your Google or Microsoft password, and there is no key to keep for online assistants.
Your rights, and nothing more: each server applies the rights of the signed-in person, in their organisation.
Writes are signed: what an assistant writes carries your name and leaves a trace.
Actions with no way back wait for a human: an email sent through Escouade’s write server (Claude asks for confirmation), an action prepared by Meet, a Social post, which only the employee publishes. Mail, for its part, follows its sending rules and the approval you require on a mailbox.
Authorisation follows the MCP specification: OAuth 2.1, PKCE, and discovery of the authorisation server from the address alone.