# Chatbase MCP connector

The Chatbase connector lets Claude, ChatGPT, Cursor, and the Elaichi Agent manage your Chatbase AI agents and their sources, search past conversations, and work help desk tickets, with each person signed in as themselves.

Source: https://elaichi.ai/connectors/chatbase/

## Facts

| | |
| --- | --- |
| Application | Chatbase |
| Category | Artificial Intelligence |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | No |
| Native MCP | Yes. Chatbase builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top |
| Support for its tools | www.chatbase.co/help |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Chatbase is connected

- Show me open help desk tickets from this morning
- What did customers ask the support agent about refunds this week?
- Add the new pricing page as a source on the website agent

## Connect Chatbase in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Chatbase.
2. Optionally set Share with, then press Connect.
3. Approve it in Chatbase. Chatbase's own window opens. Whoever approves it decides what this connection can reach.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Chatbase tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Chatbase MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Chatbase MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

## Chatbase MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Connect Chatbase to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Only Read is granted by default, which is not enough to call a Chatbase tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with Chatbase through Elaichi

### Clear the ticket queue before standup

Support. Pull up the open help desk tickets in Chatbase, see which ones the AI agent could not resolve, and reply to or close them from the chat you already have open.

### Find the conversations where the agent got stuck

Support. Search Chatbase conversations for a product name or an error message, read how the AI agent answered, and spot the questions it keeps missing.

### Keep an agent's sources current after a launch

Customer success. When a feature changes, add the new help article or document as a source on the Chatbase agent so its answers match what actually shipped.

### See what website visitors are asking

Marketing. Search the past week of Chatbase conversations on the website agent and summarize the questions prospects asked before they filled in a form.

### Turn repeated questions into a backlog

Product. Search Chatbase conversations for complaints about a feature and group them, so the recurring ones land in the planning doc with real customer quotes.

### Audit every agent and its training sources

Operations. List the Chatbase AI agents in the workspace along with their sources, and flag the ones that have not been refreshed so stale knowledge gets caught.

## Elaichi vs Zapier MCP vs Composio for Chatbase

All three can connect Chatbase to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Chatbase tools | Allow or restrict single Chatbase tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Chatbase call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Chatbase to Claude?

Connect Chatbase in Elaichi first, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Chatbase connects over OAuth, so you sign in to your Chatbase account in a normal browser window and approve access. There is no client ID or secret to generate, and nothing to register inside Chatbase.

### Does Chatbase work with ChatGPT and Cursor as well as Claude?

Yes. Once Chatbase is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Chatbase once and every client picks it up.

### What can an AI agent actually do with my Chatbase data?

An AI agent can list your Chatbase AI agents, add or update the sources they are trained on, search past conversations for a topic or a customer, and read, reply to, or close help desk tickets. Exactly what is available depends on what your Chatbase account has set up. Short, concrete asks work better than long sentences, so 'show open tickets from today' gets a cleaner answer than a paragraph.

### Does connecting Chatbase give the AI access to my whole workspace?

No. The AI works inside the Chatbase access of the person who signed in, so it sees the agents, conversations, and tickets that person can already see in Chatbase and nothing more. Elaichi can narrow that access further with roles and restrictions, but it can never widen it beyond what Chatbase grants.

### Can my team share one Chatbase connection?

Yes. One person connects Chatbase in Elaichi and shares the connection with a team, and nobody else ever handles a credential. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who read a conversation or closed a ticket, not the person who connected the account.

### Can I stop an agent from deleting or changing things in Chatbase?

Yes. Restrictions in Elaichi work per action, so you can allow searching Chatbase conversations and reading tickets while blocking anything that deletes an agent or removes a source. A restricted action is never advertised to Claude, ChatGPT, or Cursor, so no prompt, however it is worded, can reach it.

### What happens to a Chatbase connection when someone leaves?

Offboarding a person in Elaichi ends their access to Chatbase through every client at once. If they had connected a shared Chatbase account, that connection keeps working for everyone else on the team. Disconnecting Chatbase once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client in one step.

### Does the Chatbase MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Chatbase is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Chatbase?

Yes. Both let Claude, ChatGPT or Cursor use Chatbase. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Chatbase call.

### How is Elaichi different from Composio for Chatbase?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Chatbase: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.