Connect an MCP client

Choose OAuth or a scoped token

OAuth opens MonCha’s approval flow in your browser. A scoped token is useful when the client supports custom authorization headers or you need a specific bot allowlist. Start with read scopes to verify the connection. The client configuration below follows the linked official documentation; always complete the connection check in your own workspace.

Claude Code

Run /mcp in Claude Code and complete the browser authentication when prompted. After connecting, ask it to list the MonCha bots. Confirm the workspace before enabling write actions.

claude mcp add --transport http moncha https://api.dev-moncha.com/mcp
claude mcp get moncha

• Official Claude Code MCP setup

Codex

Add the following entry to your Codex config.toml. Make MONCHA_API_TOKEN available in the environment that starts the client. Keep the actual value outside the configuration. For OAuth instead, omit bearer_token_env_var and use codex mcp login moncha after configuring the URL.

[mcp_servers.moncha]
url = "https://api.dev-moncha.com/mcp"
bearer_token_env_var = "MONCHA_API_TOKEN"

• Official Codex MCP configuration

Cursor

Add a remote entry to .cursor/mcp.json for the project or your personal global MCP configuration. Make MONCHA_API_TOKEN available to the client process, then reload its MCP connection. Never commit an actual secret.

{
  "mcpServers": {
    "moncha": {
      "url": "https://api.dev-moncha.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:MONCHA_API_TOKEN}"
      }
    }
  }
}

• Official Cursor MCP configuration

Claude connectors and other remote clients

For a client with a custom connector UI, add the copied MCP URL and follow its OAuth flow. The MonCha dashboard includes a connector URL for this purpose. Availability depends on the client’s plan and organization policy. Generic mcpServers JSON is not interchangeable with every client’s file format.

Verify and troubleshoot

1. Confirm the server is connected/authenticated in the client.
2. Run list_bots and check the expected bot list.
3. Run a read such as list_knowledge for an allowed chatbotId.
4. If the request fails, check API & Agents for the token/connection and inspect the returned status.
5. For write tools, review the exact target and action before approving the client request.

• Do not use /vendor/v1 as the MCP URL.
• An API token from UAT is not a production credential.
• If an environment variable is unset, start/restart the client with the correct environment.
• An organization may block a custom server even when your MonCha account is eligible.