Docs › Escouade
Escouade’s MCP servers
Escouade has three MCP servers. Your assistant (Claude, ChatGPT, or any MCP client) connects to them with an address and your Escouade account sign-in, and acts with your rights: it reads what you read, writes what you can write, and every write carries your signature.
The three servers
| Server | Address | For | Sizes |
|---|---|---|---|
| Read | https://app.escouade.io/mcp | Searching, reading and summarising records, documents and emails. | All |
| Write | https://app.escouade.io/mcp/ecriture | Creating and changing records on behalf of the signed-in member; every write is logged. | All |
| Integrator | https://app.escouade.io/mcp/integration | Setting up the model, the objects and the workspace, as an administrator would on screen. | Pro and Max |
The three connect side by side: read first, write when the assistant has to act, the integrator for configuration.
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 ("Escouade read", for example) and paste the address.
- "Connect": sign in with your Escouade account, choose the organisation, allow.
In a Claude Team or Enterprise organisation, an owner adds the connector; each member then connects to it themselves.
In ChatGPT: its settings, then the connectors, with developer mode switched on; create a connector with the address and OAuth authentication, then sign in with your Escouade account. ChatGPT’s labels change often: only the address matters.
In Claude Code:
claude mcp add --transport http escouade https://app.escouade.io/mcp
then /mcp in a session to sign in.
The addresses of all the family’s servers are also on the account’s Connectors page, and on The family’s MCP servers.
The tools
On app.escouade.io, the tools carry the escouade_ prefix. On an Escouade hub instance, they carry the instance’s name.
Read
| Tool | What it does |
|---|---|
escouade_trouver | Searches everything at once (records, documents, emails, dated facts), by words and by meaning, with filters, and returns a selection. |
escouade_selection | Reads the rest of a selection, or narrows it, without running the search again. |
escouade_consulter | Opens an item by its identifier: its summary, its full record; for a document, its text, a search within the document, its neighbouring passages or a download link. |
escouade_relations | What surrounds a record: linked records, timeline, files, emails, and the history (who changed what). |
escouade_modele | Describes the objects and their fields, read afresh at each call: it is the reference when the model has changed. |
The read server says on whose behalf it answers ("Connecté en tant que …", signed in as): a real call shows whether the connector was connected under the right account.
Write
| Tool | What it does |
|---|---|
escouade_ecrire | Creates, changes, links, unlinks, puts in the bin and restores records. A creation sets its links in the same call. Each call carries a unique key: replayed, it does not write twice. |
escouade_envoyer | Sends an email from your connected mailbox, with an optional blind copy, then attaches it to the chosen records and leaves a "Follow-up sent" note on them. |
escouade_journal | The log of writes made by assistants: who wrote what, when, through which route, with what result, most recent first. It is read by an administrator. |
escouade_modele | An object’s fields, to read before writing. |
escouade_artefact | Sends a page created in Claude into Escouade, or a new version of it, then shares it with a member. |
Identifiers come from the read server: the write server does not search by text. A refusal names the problem: the assistant corrects its call rather than guessing.
Sending emails is closed by default. An administrator opens it role by role, in Settings › MCP, Write tab ("Envoyer des courriels", send emails). Claude asks for confirmation before each send, and a send never goes out twice under the same key.
Integrator
| Tool | What it does |
|---|---|
escouade_superviser | Ingestion: the traces, the "To review" queue, the scenarios, the thresholds, the alerts, the decision model’s test bench. |
escouade_parametrer | The data model and every setting of the workspace, through the same functions and the same safeguards as on screen. It also tests a person’s access, lists Claude’s connections, shares a record or a mailbox. |
escouade_ecrire | The data of any object. |
escouade_modele | The objects and their fields. |
escouade_artefact | The workspace’s artefacts. |
The integrator is the configuration server: an administrator sets through it what they would set on screen, without touching the database. It is included from Pro.
Under which rights
- Through Claude, each person has exactly their rights in the application: what their role, their groups and their exceptions open to them, and none of what is withdrawn from them (a hidden field stays hidden).
- The MCP server settings are added on top, in Settings › MCP: which roles have which server, at which level, object by object.
- Every write carries the signature of the signed-in member and leaves a line in the log.
- A Claude connection unused for 14 days is erased on its own; each use extends it. When you come back, Claude simply asks for your consent again.
The call log
Every call to the MCP servers (read, write, integrator), refusals and abandoned calls included, is kept for six months: who, from which device, which tool, which result. An administrator reads it through the integrator.
The protocol
The servers speak MCP over Streamable HTTP. Authorisation follows the OAuth part of the MCP specification: a client only needs the address; it discovers the authorisation server through the protected resource metadata, and the person signs in through the Escouade account.