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.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Chatbase to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Chatbase once
-
Open Connections, choose Add connection, and pick Chatbase.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Chatbase. Chatbase's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Chatbase MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Chatbase to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Chatbase through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Support
Clear the ticket queue before standup
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.
-
Support
Find the conversations where the agent got stuck
Search Chatbase conversations for a product name or an error message, read how the AI agent answered, and spot the questions it keeps missing.
-
Customer success
Keep an agent's sources current after a launch
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.
-
Marketing
See what website visitors are asking
Search the past week of Chatbase conversations on the website agent and summarize the questions prospects asked before they filled in a form.
-
Product
Turn repeated questions into a backlog
Search Chatbase conversations for complaints about a feature and group them, so the recurring ones land in the planning doc with real customer quotes.
-
Operations
Audit every agent and its training sources
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.
Try asking
- “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”
Compare
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.
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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
See it in Elaichi
What connecting Chatbase gets you
5 screens from the product, each doing one job for your Chatbase account.
The agent
Ask Chatbase what your customers asked.
Plain questions, answered from live Chatbase conversations, tickets, and agents.
- agents
- sources
- conversations
- tickets
Ask Elaichi to work across your apps.
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
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint brings Chatbase to every client.
Claude, ChatGPT, and Cursor reach Chatbase through one governed endpoint, no SDK, no shared key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Toolboxes
Each team gets its own Chatbase toolbox.
Support handles tickets, Marketing reads conversations, Product manages sources, each from a separate toolbox.
- Support
- Customer success
- Marketing
- Product
ElaichiToolboxesShared connections
Share Chatbase once, keep the credential private.
Teammates work tickets and conversations through a shared connection and never see a credential.
- Support
- Customer success
- Marketing site
- Product
ElaichiConnectionsAudit log
Every Chatbase action is logged with a name.
When, who, what happened, and which agent, ticket, or conversation, in one append-only log.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule turns Chatbase tickets into a digest.
Tickets are fetched, grouped, drafted, approved by a person, then posted back to Chatbase.
Chatbase digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch agents
Chatbase
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Chatbase
Queued
Collections and dashboards
Chatbase health, counted without a model.
Conversations per day, open tickets, and agents by team, refreshed on a schedule.
Chatbase health
Refreshed 4 minutes ago · every 15 minutes · from the agents collection
Agents
1,284 ↓ 12%
Sources
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Agents created
Last 14 days
By team
Share of activity
Support 34%
Customer success 27%
Marketing site 21%
Product 18%
FAQ
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 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.
Put Chatbase in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.