Connectors · AI

Chatbase MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Chatbase and the rest of your systems. It gives your agent 40 Chatbase actions (19 reads, 19 writes and 2 that wait for a confirmation) and holds the Chatbase credential itself, so the agent never does. It paces Chatbase's limits and records every call.

Connect Chatbase free See pricing

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

claude mcp add --transport http actionlake https://connect.actionlake.com/mcp

40actionsin one signed file
19readlook, never change
19writecreate and update
2wait for a yesdestructive, confirmed first

Set up

Connect Chatbase in three steps.

01
Add actionlake to Claude.
Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.
https://connect.actionlake.com/mcp
02
Connect Chatbase.
Bearer token. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.
- access_tokenChatbase API key (Workspace settings > API keys)
```
account { op: "connections.requirements", service: "chatbase" }
# free: exactly what to paste, and what is found for you
```

Make the first call. Check before a write.

Ask in plain words; Claude picks the action. Before anything changes, check validates the call and prices it, for free.

do    { action: "chatbase.agents.list" }# agents: list · read · 1 upstream callcheck { action: "chatbase.tickets.create", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

Chatbase at a glance

Sign-in: Bearer token. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.
You provide: access_token
Limits we pace to: 100 calls a minute, per connection
API covered: Chatbase API v2 (AI agents, chat, conversations, sources, helpdesk, WhatsApp) API v2 (OpenAPI 2.0.0)www.chatbase.co
Built from: Chatbase's documentation, read 23 October 2026chatbase.co chatbase.co
Service file: Version 1.0.0, signed (Ed25519)
Cached reads: 19 of 19 reads, for up to 5 minutes; a write clears what it affects
Shared entities: 2, so ask can line Chatbase up with your other systems
Data: Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in Chatbase.

40 actions in 1 area. Every one carries its effect, so a key can allow the reads and hold the rest.

19readlook, never change
19writecreate and update
2destructivewait for a confirmation

Agents
40
19 read · 19 write · 2 destructive
Tickets: list · Tickets: create · Tickets: get · Tickets: update

Top actions

The Chatbase API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 14 of Chatbase's 14 action names are shared with at least one other connector, so an agent learns them once.

Action	What it does	Effect	Same name in
`chatbase.tickets.list`Tickets: list	Returns tickets for an agent, sorted by `updatedAt` descending by default.	read	`service.ticket.list`56 connectors
`chatbase.tickets.create`Tickets: create	Creates a ticket on behalf of a customer.	write	`service.ticket.create`54 connectors
`chatbase.conversations.list`Conversations: list	List conversations created through the API for an agent, ordered by createdAt date.	read	`service.conversation.list`19 connectors
`chatbase.conversations.get`Conversations: get	Get conversation metadata and its most recent messages.	read	`service.conversation.get`19 connectors
`chatbase.ticket_messages.create`Ticket messages: create	Posts an agent reply to a ticket on behalf of a team member.	write	`service.ticket_note.create`24 connectors
`chatbase.ticket_messages.list`Ticket messages: list	Returns a ticket's message thread in chronological order.	read	`service.ticket_note.list`20 connectors
`chatbase.ticket_statuses.list`Ticket statuses: list	Returns the active (non-archived) ticket statuses configured for an agent, ordered by category then position.	read	`service.ticket_status.list`8 connectors
`chatbase.conversation_messages.list`Conversation messages: list	List all messages in a conversation with cursor-based pagination.	read	`service.conversation_message.list`6 connectors
`chatbase.teams.list`Teams: list	Returns the teams configured for an agent, ordered by creation date.	read	`service.ticket_team.list`3 connectors
`chatbase.conversations.export`Conversations: export	Export all conversations with full message history for an agent.	read	this connector
`chatbase.agents.chat`Agents: chat	Send a message to an agent and receive a response.	write	this connector
`chatbase.agents.delete`Agents: delete	Permanently deletes an agent and all its sources.	destructive	this connector

Try it

Prompts to paste into Claude.

Each one names the Chatbase actions it will call, so you know what it reads and what it changes before you send it.

Readread
Which Chatbase tickets have been open the longest? Show me the ten oldest with their status.
callschatbase.tickets.list
Writewrite
Tickets: create in Chatbase. Show me exactly what you will send before you save it.
callschatbase.tickets.create

Governance for Chatbase

Destructive actions wait for a yes.

2 Chatbase actions are destructive. These are all of them:

Agents: deletechatbase.agents.delete
Sources: deletechatbase.sources.delete

A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

dochatbase.agents.deleteconfirm_policy: human

Agents: delete?

intent: the user asked me to agents: delete

run suspended · waiting for a named person · key chatbase-agent cannot confirm itself

In the console, or from an emailed signed link.

a key for this connector

account {  op: "keys.create", name: "chatbase-agent",  allowed_actions: ["chatbase.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "chatbase.agents.delete", approver: "[email protected]" },    { match: "chatbase.sources.delete", approver: "[email protected]" }  ]}

Illustrative. Scoped to Chatbase only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

What Chatbase costs on actionlake.

Every Chatbase action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Chatbase refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

1upstream call per actionall 40 Chatbase actions
9actions pageeach page of a long list is one call
19reads can be cacheda cache hit costs nothing
100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Chatbase action.

40 actions by area: the id your agent calls, what it does, and its effect.

Agents40

chatbase.agents.chatAgents: chatwrite
chatbase.agents.cloneAgents: clonewrite
chatbase.agents.createAgents: createwrite
chatbase.agents.deleteAgents: deletedestructive
chatbase.agents.getAgents: getread
chatbase.agents.listAgents: listread
chatbase.agents.set_auto_retrainAgents: set auto retrainwrite
chatbase.agents.updateAgents: updatewrite
chatbase.agents.update_stylesAgents: update styleswrite
chatbase.conversation_messages.listConversation messages: listread
chatbase.conversation_messages.update_feedbackConversation messages: update feedbackwrite
chatbase.conversations.exportConversations: exportread
chatbase.conversations.getConversations: getread
chatbase.conversations.listConversations: listread
chatbase.conversations.list_for_userConversations: list for userread
chatbase.conversations.retry_messageConversations: retry messagewrite
chatbase.conversations.searchConversations: searchread
chatbase.conversations.submit_tool_resultConversations: submit tool resultwrite
chatbase.conversations.update_statusConversations: update statuswrite
chatbase.health.getHealth: getread
chatbase.sources.create_linkSources: create linkwrite
chatbase.sources.create_qnaSources: create qnawrite
chatbase.sources.create_textSources: create textwrite
chatbase.sources.deleteSources: deletedestructive
chatbase.sources.getSources: getread
chatbase.sources.listSources: listread
chatbase.sources.summarySources: summaryread
chatbase.sources.updateSources: updatewrite
chatbase.teams.listTeams: listread
chatbase.ticket_messages.createTicket messages: createwrite
chatbase.ticket_messages.listTicket messages: listread
chatbase.ticket_statuses.listTicket statuses: listread
chatbase.tickets.createTickets: createwrite
chatbase.tickets.getTickets: getread
chatbase.tickets.listTickets: listread
chatbase.tickets.searchTickets: searchread
chatbase.tickets.updateTickets: updatewrite
chatbase.voice_sessions.createVoice sessions: createwrite
chatbase.whatsapp_templates.listWhatsapp templates: listread
chatbase.whatsapp_templates.sendWhatsapp templates: sendwrite

Questions

The Chatbase MCP server, answered.

Is there a Chatbase MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 40 Chatbase actions, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Chatbase.

What do I need to connect Chatbase?

Chatbase API key (Workspace settings > API keys). The free call account { op: "connections.requirements", service: "chatbase" } lists exactly what to paste.

Can an AI agent delete or change things in Chatbase?

Only if its key allows it, and only with an explicit confirmation. 2 Chatbase actions are destructive, including agents: delete and sources: delete. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

Will an AI agent use up my Chatbase API limit?

actionlake paces every call to the limits in the Chatbase service file: 100 calls a minute per connection. Repeated reads are answered from cache (19 Chatbase actions can be), which never reaches Chatbase.

What does a Chatbase action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (9 Chatbase actions page). Cache hits, searches, dry runs and calls Chatbase refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

Which Chatbase API does it cover?

The Chatbase API v2 (AI agents, chat, conversations, sources, helpdesk, WhatsApp) API v2 (OpenAPI 2.0.0) at www.chatbase.co. It is built from Chatbase's documentation as read on 23 October 2026. 40 actions in 1 area, each one in the signed service file (version 1.0.0).

Does actionlake keep my Chatbase data, and where?

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Chatbase credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Which AI clients can use it?

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

Give your agent Chatbase today.