Connect another MCP client

iyedy serves its 24 tools over the Model Context Protocol. Claude, ChatGPT and the coding assistants (Codex, VS Code with GitHub Copilot, Zed, Cursor, Gemini CLI) sign in with OAuth on its address. Any other MCP client connects to your organisation's endpoint with a personal access token sent in a header.

Two ways in

Both endpoints speak MCP over Streamable HTTP: stateless, POST only, JSON answers. They offer the same 24 tools and apply the same rules: your roles, the classification ceiling, the organisation's MCP policy.

Before you start

• An MCP client that can send a header with each request to a remote server over Streamable HTTP.
• A personal access token with the scopes your client needs: cartouche.read for the reading tools, cartouche.graph for search and impact, cartouche.propose to preview and submit proposals. See Create and manage API tokens and Scopes.
• In a Team or Enterprise organisation, MCP turned on by support at an owner's request: Claude and MCP for your organisation.

Connect with a personal access token

1. Find your organisation's id

   Ask the API who the token is. Any token can call this route:

   GET /v1/token HTTP/1.1
   Host: app.iyedy.com
   Authorization: Bearer crt_pat_…
   

   The answer names the token's organisation in tenantId, and lists the workspaces it reaches in workspaces, each with its id, name and your role.

2. Add the server to your client

   In your client's settings, add a remote MCP server over HTTP with:

   • the address https://app.iyedy.com/v1/t/{tenantId}/mcp, where {tenantId} is the value of step 1;
   • the header Authorization: Bearer crt_pat_…, with your token.

   Keep the token in your client's secret store or an environment variable, never in a file you commit.

3. Check the connection

   Ask your agent to list the iyedy workspaces, or call the tool list_workspaces from the client.

   You are done when the answer lists the workspaces of step 1, with your role in each.

What the token can and cannot do

• It acts as you. The token's scopes meet your role: a cartouche.propose scope on a viewer's account stores nothing. A diagram you cannot read answers “not found”.
• It never changes a model. Over MCP, the only writes are a proposal and its withdrawal; a person applies proposals in iyedy. See How proposals reach your team.
• It reads up to the ceiling. Confidential on a personal workspace, Internal in Team and Enterprise. Listings and searches stay under it too.
• It is refused once it is revoked or expired, on the next request. Revoking it is the way to disconnect the client.

If it doesn't work

More: Rate limits and errors.