Connect an AI agent to your Coffee Chats account

Claude on the web and Claude Desktop

Claude Desktop uses the same client as Claude on the web.

1. Open Settings, then Connectors, then add a custom connector.
2. Paste https://mcp.coffeechats.me/mcp as the server address.
3. Under OAuth client, keep Use Claude's published identity selected; there is no client identifier to enter.

If you choose Use your own OAuth client instead, enter the client identifier claude-ai and leave the client secret empty.

Claude Code

Run this command:

claude mcp add --transport http coffeechats https://mcp.coffeechats.me/mcp

Claude Code identifies itself with its published client address, so no client identifier is needed. Claude Code is a native client, so it receives its authorization code on a loopback address on your own machine. If your version of Claude Code does not send its published address, add --client-id claude-code and leave the client secret unset.

ChatGPT

OpenAI's page for connecting an MCP server to ChatGPT gives these steps. Open Settings, select Security and login, and turn on Developer mode. Then open the Plugins page in ChatGPT and select the plus button. Enter a user-facing name and description, and under Connection choose the public endpoint and enter https://mcp.coffeechats.me/mcp, including the /mcp path.

The form OpenAI documents asks for a name, a description and the server address. It has no field for a client identifier, and none is needed: ChatGPT identifies itself with the client address it publishes, and the address it is sent back to after sign-in is registered with Coffee Chats already. If your version of the form does ask for a client identifier, enter chatgpt and leave the client secret empty.

Codex CLI

Run this command:

codex mcp add coffeechats --url https://mcp.coffeechats.me/mcp --oauth-client-id codex

Then sign in:

codex mcp login coffeechats

OpenAI's Codex MCP page says to provide a client identifier when the authorization server requires a pre-registered client, and that a configured client identifier takes precedence and skips registration. Coffee Chats requires a pre-registered client, so pass codex as shown. Leave the client secret unset.

When you add the server, Codex prints the callback address it wants you to register with the provider. Coffee Chats has registered that address already. Codex is a native client, so it receives its authorization code on a loopback address on your own machine, and Coffee Chats ignores the port.

Cursor

Cursor's MCP page documents a configuration file rather than a form. Create .cursor/mcp.json in your project for one project, or ~/.cursor/mcp.json in your home directory for every project, and add the server under mcpServers:

{
  "mcpServers": {
    "coffeechats": {
      "url": "https://mcp.coffeechats.me/mcp",
      "auth": {
        "CLIENT_ID": "cursor-desktop"
      }
    }
  }
}

Cursor's page asks for an auth object on a remote server entry when the provider gives you a fixed client identifier. Coffee Chats gives you one and uses no client secret, so leave CLIENT_SECRET out. Cursor's page then says to enable or disable MCP servers from Customize in the sidebar.

Cursor uses a different return address for each surface you sign in from, so Coffee Chats registers each surface as its own client. The desktop app uses cursor-desktop, which is the value written above. Web and Cursor Agents use cursor. Cursor's page documents no form for adding a personal MCP server on the web surface. It documents Dashboard > Plugins & MCPs for servers a team shares with its Cloud Agents.