Home › Blog › Chatbase MCP server

Chatbase MCP server: manage your Chatbase agents from Claude

Updated 2026-10-25

This page has affiliate links, each marked "Affiliate link, #ad". We may be paid if you sign up, at no extra cost to you. See our affiliate disclosure.

The Chatbase MCP server lets Claude, Codex, Cursor and other MCP clients manage your Chatbase workspace: agents, training sources, conversations and help desk tickets. Add https://mcp.chatbase.co/api/mcp to your client and sign in with OAuth, no API key needed. Here are the steps from Chatbase's docs and the permissions to pick.

What is the Chatbase MCP server?

It is Chatbase's official MCP server, which lets Claude, Codex, Cursor and other MCP clients (see Claude connectors trend) manage your Chatbase workspace. (Affiliate link, #ad: we may be paid if you sign up, at no extra cost to you.) Your assistant can create and update AI agents, add training sources, read conversations and work help desk tickets. You sign in with OAuth and pick which permissions the app gets.

Who is it for?

Teams that already run a Chatbase support or sales agent (see AI agent use cases) and want to manage it from the tools they code in. Instead of clicking through the dashboard, you ask Claude to add a new help page as a source, summarize last week's conversations or list open tickets. New to Chatbase? Build your first agent with our setup guide first.

Related: Chatbase setup guide

Related: Chatbase in the directory

How do you connect Chatbase MCP to Claude Code?

Add the server URL as an HTTP server, then authenticate. Run the command below, open Claude Code, type /mcp, pick chatbase and choose Authenticate. Your browser opens Chatbase, where you choose the workspace and the permissions. No API key or Authorization header is needed.

1. Add the server. Run: claude mcp add --transport http chatbase https://mcp.chatbase.co/api/mcp
2. Authenticate. In Claude Code, run /mcp, select chatbase and choose Authenticate.
3. Approve permissions. In the browser, pick your Chatbase workspace and approve only the permissions the job needs. Read-only is fine for reporting.
4. Check access. Ask Claude to call chatbase_whoami. It reports the workspace, the user and the exact permissions in use.

Claude Code, from Chatbase's docs:

claude mcp add --transport http chatbase https://mcp.chatbase.co/api/mcp

Claude Code plugin (alternative), from Chatbase's docs:

claude plugin marketplace add Chatbase-co/chatbase-plugin
claude plugin install chatbase@chatbase

Open Chatbase → Affiliate link, #ad: we may be paid if you sign up, at no extra cost to you.

Is there a Chatbase plugin for Claude Code?

Yes. Chatbase publishes a plugin you add from its marketplace in Claude Code, with two commands listed in its docs. The plugin bundles the MCP server connection, so you skip the manual add. Either path ends in the same OAuth sign-in and the same permission screen, so pick whichever fits how you manage Claude Code.

Related: best MCP servers for Claude Code

How do you add Chatbase MCP to Cursor, Codex and VS Code?

Cursor reads an HTTP server entry from ~/.cursor/mcp.json; VS Code, Windsurf, Zed and OpenCode use the same shape in their own config files. Codex adds the server with codex mcp add, then signs in with codex mcp login. Every client ends at the same Chatbase OAuth screen.

Cursor (~/.cursor/mcp.json), from Chatbase's docs:

{
  "mcpServers": {
    "chatbase": {
      "type": "http",
      "url": "https://mcp.chatbase.co/api/mcp"
    }
  }
}

Codex, from Chatbase's docs:

codex mcp add chatbase --url https://mcp.chatbase.co/api/mcp
codex mcp login chatbase

Why do I see only a few Chatbase tools?

A client only sees the tools its permissions cover, so a short list usually means a narrow approval, not a missing feature. Ask the assistant to call chatbase_whoami to see what was granted. To widen access, revoke the app under Connected apps in Chatbase, reconnect, and approve the permissions the task needs.

Related: MCP context cheat sheet

Related: best MCP servers for Codex

What can Claude do in Chatbase through MCP?

The server exposes 27 tools: chatbase_whoami plus 26 grouped into AI agents, sources, conversations and help desk. Claude can create, clone and update agents, add or retrain sources, read and export chat logs, and list or update tickets. MCP tool access depends on your Chatbase plan; see vendor site.

Which actions can't be undone?

Deleting a source purges its knowledge at once, and editing a source overwrites it and retrains the agent; Chatbase says neither can be undone. Deleting an agent removes its sources and integrations too. Chatbase marks these as sensitive writes that a client should confirm before every call, and delete permissions are off by default.

Related: Botpress

How do you keep the Chatbase connection safe?

Approve the fewest permissions that do the job. Each area, agents, sources, chat logs and help desk tickets, has separate read, write and delete scopes, and delete and export start unselected. Review every connected app under Settings, General, Connected apps, and revoke any you don't recognize.

Can you trust the app name on the approval screen?

Not on its own. Chatbase notes that app names are not verified, so check that you started the sign-in from your own client a moment ago. Revoking an app under Connected apps takes effect on its next request. If something looks wrong, revoke first, then reconnect from a client you control.

Related: is it safe to connect an MCP server

See how we run our own agent crew in the playbook.

Building on Grok Bot? Start a crew from the DartzDabz Crew Builder template.

We may be paid by X based on how many people use our Crew Builder template.

See real agent setups you can copy, browse the agent tool directory, or submit a tool; listings are free.