Skip to main content

Connect AI apps (MCP)

The MonoChat MCP Server lets an AI app that supports the Model Context Protocol (MCP), such as Claude Code or Cursor, work with your MonoChat account. The AI app asks MonoChat for data through a fixed set of tools; it can only see what you can see.

The MonoChat MCP Server is available on every plan, with no limits by plan.

A connection acts as you

An AI app connected with your access key acts as your user. It reaches the tenants you can access and nothing else. Revoke connections you no longer use.

What the AI app can do​

These tools are available to every connection:

ToolWhat it does
list_tenantsLists the tenants the connection can access.
list_sessionsLists the conversation sessions of a tenant, newest first, optionally only opened, assigned or closed ones.
get_sessionReturns one conversation session.
list_messagesLists the messages of a session, newest first.
search_customersSearches the customers of a tenant by keyword.
list_message_templatesLists the message templates of one channel of a tenant.

Message text comes from customers and agents. It is data for the AI app to read, not instructions.

A connection has a scope, Read-only or Read and write. A read-only connection never sees tools that change data. All tools listed above only read.

Create a connection​

A connection belongs to your account, not to a tenant. You need two-step verification (by e-mail or an authenticator app) set up first.

  1. Open your profile settings, select the MCP connections tab and click Create.
  2. Enter a name, choose the scope (Read-only by default) and the expiry in days (90 by default, 365 at most).
  3. Enter the 6-digit confirmation code from your two-step verification method. If you use e-mail verification, click Send confirmation code first.
  4. Copy the access key. It is shown only once; it starts with mcp_sk_.

You can have up to 10 active connections.

Connect an AI app​

The server is at https://app.monochat.ai/api/mcp-server (use your own MonoChat address if you run MonoChat on your own servers) and expects the access key as a bearer token in the Authorization header.

Claude Code​

claude mcp add --transport http monochat https://app.monochat.ai/api/mcp-server \
--header "Authorization: Bearer <access key>"

Cursor​

Add the server to ~/.cursor/mcp.json:

{
"mcpServers": {
"monochat": {
"url": "https://app.monochat.ai/api/mcp-server",
"headers": { "Authorization": "Bearer <access key>" }
}
}
}

Any other MCP client that supports the streamable HTTP transport and custom headers connects the same way.

Limits​

Calls are counted per minute: 60 per connection, 300 per account and 600 per tenant, and at most 4 calls at the same time per connection. Some tools count as more than one call. When a limit is hit, the server answers with a 429 status and a Retry-After header; the AI app should wait that many seconds.

Revoke a connection​

Each connection in the MCP connections tab shows its status, scope, expiry and last use. Click Revoke to cut off the AI app immediately. A connection that is revoked or expired cannot be used again; create a new one instead.

Manage MCP access for a tenant​

Users who can change a tenant's settings manage its MCP access in Settings › Tenant › MCP Server.

  • Turn off MCP access for this tenant: switch it on and click Save to refuse every MCP call to this tenant, from every connection of every user. The tenant no longer appears in list_tenants. Switch it off and save to allow MCP access again.
  • MCP calls: every call to a tool that names this tenant, newest first, refused calls included. Each row shows the user, the connection, the tool, the status (Success or Failed), the IP address and the time. Calls from users who are not members of this tenant are not shown.