Social’s MCP server · Escouade documentation

Your assistant prepares the team’s posts, submits them to the workflow, reads the results and the calendar, through Social’s MCP server. It acts on behalf of the person who connected it, with their current rights. It never publishes or sends anything: the employee always clicks in LinkedIn themselves.

The addresses

For	Address
A space (one brand)	`https://social.escouade.io/w/<space>/mcp`
A brand group	`https://social.escouade.io/g/<group>/mcp`

<space> and <group> are the identifier of the space or the group, the one in their address in Social. The "Connections & MCP" page of the space or the group gives the exact address. The old address, https://app.advoq.fr/…/mcp, still answers: a connector already connected has nothing to do.

Connecting

In Claude: Settings › Connectors › "Add custom connector", paste the address, then "Connect": sign in with your Escouade account and allow. The connection appears in "Connections & MCP" under the name "Claude (OAuth)", from where it can be revoked.

In ChatGPT: in developer mode, a custom connector takes the same address, with OAuth authentication.

An MCP client that accepts a token: create a token in "Connections & MCP", read-only or read and write, and pass it as Authorization: Bearer.

JSON

{
  "mcpServers": {
    "escouade-social": {
      "url": "https://social.escouade.io/w/<space>/mcp",
      "headers": { "Authorization": "Bearer <token>" }
    }
  }
}

A collection token, the extension’s, cannot query the MCP server.

The tools

Read

Tool	What it returns
`linkedin_publications_rechercher`	Collected posts, by profile, period or text.
`linkedin_publications_statistiques`	Post indicators, by profile or by team.
`linkedin_publication_historique`	A post’s successive observations.
`linkedin_profils_lister`	Followed profiles.
`linkedin_collections_lister`	Collections.
`advoq_agenda`	The team calendar.
`advoq_preparations_lister`	Prepared items and their step.
`advoq_synchros_lister`	Requested syncs and their status.
`advoq_utilisateurs_lister`	The space’s users.
`advoq_circuits_lister`	Approval workflows.
`advoq_plan_resultats`	The editorial plan’s results: planned, approved, published, found by the collection.
`advoq_abonnement_lire`	The subscription: status, seats, renewal date.

Social’s own tools keep their original names, with the advoq_ prefix.

Write (read and write token, or OAuth connection)

Tool	What it does
`advoq_preparation_creer`	Prepares a post, a private message or a comment.
`advoq_preparations_creer_lot`	Prepares a whole plan (100 items at most), all or nothing.
`advoq_preparation_modifier`	Changes a prepared item.
`advoq_preparation_decider`	Submits an item, or decides it at its step in the workflow.
`advoq_profil_ajouter`, `advoq_profil_archiver`	Adds or archives a followed profile.
`advoq_synchro_demander`	Requests a sync, for one person or for the team.
`advoq_collection_creer`, `advoq_collection_publication`	Files posts into collections.
`advoq_circuit_enregistrer`, `advoq_circuit_archiver`	Sets up approval workflows.

The decision history reads "Name (assistant)". What commits money (payment, seats, cancellation) stays an action in Social: the assistant reads it, it does not decide it.

A group’s MCP server

A group’s MCP server exposes the same tools with a marque (brand) parameter, plus advoq_marques_lister. When reading without a brand, it answers brand by brand; when writing, the brand is required.

Views

In an assistant that displays them, Social’s tools render their view in the conversation: a table, the calendar, buttons that decide in the right brand. A missing value is written "unknown" there.