Multi-client MCP architecture

One AI client. Many monday.com accounts. Nothing shared by accident.

This gateway sits between your consumers (Claude, Codex, Gemini CLI, Cursor) and monday.com’s hosted MCP server. It holds each client’s credentials, enforces who may use them, and records what happened.

Open the chat portal Get my endpoints Admin console

Consumers

Claude · Codex · Gemini CLI · Cursor

→

/api/public/mcp/c/<slug>

→

monday.com MCP

https://mcp.monday.com/mcp

The four rails

Identity: Consultants sign in with the gateway's own OAuth 2.1 server. AI clients register themselves and get a user-scoped token, no shared secrets pasted into config files.
Routing: Each monday.com account gets a slug and its own endpoint. The slug in the URL picks the account; the consultant's grants decide whether they may reach it.
State: monday.com API tokens are stored encrypted with AES-GCM and decrypted only for the duration of a single relayed call.
Governance: Every JSON-RPC call is logged with caller, client, tool and outcome. Rotation dates are tracked, and bulk GraphQL writes are refused unless an approver is named.