Connect ChatGPT or Claude to Your Customer Conversations, Without an API Key

You can connect ChatGPT, claude.ai or Claude Code to your MonoChat customer conversations by signing in, with no API key to create or paste. Add the MonoChat MCP Server address to the AI app, approve it on MonoChat’s approval page with your two-step verification code, and choose whether it may only read or also make changes. The app can then answer questions such as “What did customers complain about on WhatsApp this week?” from your real conversations, and you can revoke it with one click.

Until this release, connecting an AI app meant creating an access key in MonoChat and pasting it into a configuration file, which suits developers using Claude Code or Cursor. Since MonoChat 3.8.45 MonoChat is also an OAuth 2.1 authorization server, so the apps that managers and support leads already use in the browser connect the same way they connect to any other account.

What the AI app can do once it is connected

The MonoChat MCP Server gives an AI app a fixed set of tools. Today all of them read:

Tool	What it answers
list_tenants	Which workspaces can I reach?
list_sessions	Which conversations match a status, a customer name, a phone number in any format, an agent, a tag or a date?
get_session	What is the state of this conversation?
list_messages	What did the customer or the agents write, optionally since a given time?
search_customers	Which customers match this keyword?
list_message_templates	Which templates does this channel have?

That is enough for the questions a manager asks every Monday:

In the Northwind Home workspace, list the WhatsApp conversations closed
since Friday where the customer mentioned a late delivery. Group them
by city and quote one message from each group.

Which customers tagged "wholesale" wrote to us in October and have no
reply from an agent yet?

The app reads the messages and writes the summary. Message text comes from customers and agents, so the help center is explicit: it is data for the AI app to read, not instructions.

Why sign-in is safer than a pasted key

The Model Context Protocol has its own authorization specification, based on the OAuth 2.1 draft. It makes the MCP server a resource server that accepts access tokens, requires clients to use PKCE so an intercepted authorization code cannot be redeemed by someone else, and recommends dynamic client registration so an app can register itself without you creating a client by hand.

For you, that changes four things:

• No secret to leak. The app receives a short-lived token and renews it on its own. It never sees your password or a key, so there is nothing to paste into a chat, a ticket or a shared document by mistake.
• You approve each app. The approval page names the app, the address it identifies itself with and where you are sent back after approval. An app running on your own computer is marked as such.
• The access level is a choice. Read your MonoChat data is always granted. Also make changes is a separate switch, off by default. A read-only connection never even sees tools that change data.
• Access ends on its own. A sign-in connection ends 90 days after the app last renewed its token, when you revoke it, or when you change or reset your password.

Connect claude.ai or Claude Desktop

1. Set up two-step verification in MonoChat first, by e-mail or an authenticator app.
2. In Claude, add a custom connector with the server address https://app.monochat.ai/api/mcp-server (your own address if you run MonoChat on your own servers). Leave the OAuth client ID and secret empty: Claude registers itself.
3. Claude opens MonoChat’s approval page. Sign in if you are not signed in.
4. Leave Also make changes off unless you need it, enter the 6-digit confirmation code and click Allow.

Anthropic’s own guidance on custom connectors is worth following: connect only to servers from organizations you trust, review the permissions requested at sign-in, and turn off tools you do not need.

Connect ChatGPT

Add the MonoChat MCP Server to ChatGPT as a custom app with the same server address. ChatGPT uses OAuth and opens the same approval page. ChatGPT cannot use access keys, so sign-in is the only way to connect it.

Connect Claude Code

claude mcp add --transport http monochat https://app.monochat.ai/api/mcp-server

Then run /mcp in Claude Code and choose Authenticate: the approval page opens in your browser. Claude Code, Cursor and other MCP clients can still use an access key instead, as described in our MCP Server guide for developer tools.

What a connection can reach

A connection acts as your MonoChat user. It reaches the workspaces you can access and nothing else, and inside them it sees what your role lets you see. Two consequences are worth planning for:

• Give managers the role they need, not more. If an AI app connected by a team lead should not read the finance workspace, the team lead should not have access to it in the first place. See roles and permissions.
• Workspace admins keep the last word. In Settings › Tenant › MCP Server, a user who can change the workspace settings can turn off MCP access for the whole workspace, from every connection of every user. The same screen lists every MCP call: the user, the connection, the tool, the status, the IP address and the time.

Calls are also limited per minute (60 per connection, 300 per account and 600 per workspace, at most 4 at the same time per connection), so one runaway assistant cannot slow the workspace down. You can have up to 10 active connections, sign-in connections included.

Manage and revoke connections

Every connection appears on the MCP connections tab of your profile settings, with its status, scope, expiry and last use. A sign-in connection is marked OAuth and named after the app. Revoke cuts the app off immediately; connecting the same app again replaces its earlier connection.

Make revoking part of your offboarding: when someone leaves, their connections go with their account, and a password reset revokes every grant and key at once.

Before you connect: three questions for your data team

1. Which AI provider will process the messages? Whatever the app reads goes to its provider. Check its retention, training and region settings, and your contract with it. Our AI chatbot privacy checklist walks through each point.
2. Who should be allowed to connect? Connections follow user roles; decide which roles may use them before you announce the feature.
3. Should any workspace stay closed? Turn MCP access off in the workspaces whose conversations must never leave MonoChat.

Getting started

The MonoChat MCP Server is available on every plan, with no limits by plan. Create a free Basic account at app.monochat.ai, connect a channel, and connect your AI app from the MCP integration instructions or the help center guide.

Sources

• Model Context Protocol specification, Authorization (2025-06-18), opened 4 Nov 2026
• Claude Help Center: Getting started with custom connectors using remote MCP, opened 4 Nov 2026
• MonoChat help center: Connect AI apps (MCP), opened 4 Nov 2026
• MonoChat changelog 3.8.45, 3 Nov 2026