Chatbase

Add a message to a ticket Posts an agent reply to a ticket on behalf of a team member. Delivery to the customer is asynchronous; a 201 confirms the reply was recorded, not delivered. Posting a reply may transition the ticket status, matching dashboard behavior.

chatbase_create_ticket_message

Chat with an agent Send a message to an agent and receive a response. Streaming is not available over MCP; responses are always returned complete.

chatbase_chat

Reports the authenticated Chatbase workspace, the calling user, and the scopes granted to the current OAuth grant. Use this first when a tool is missing or a call is refused — a short tool list usually means the grant is narrowly scoped rather than that the capability does not exist.

chatbase_whoami

Clone agent Creates a full deep-clone of an agent, including all its sources (excluding Notion). Returns the new agent ID. Same response shape as Create Agent — `pendingSteps` indicates if training could not start automatically. The clone is a new, independent agent; changes to the original do not affect it. Subject to plan agent limits — returns `AGENT_LIMIT_REACHED` (403) when the account has reached its maximum number of agents.

chatbase_clone_agent

Create a ticket Creates a ticket on behalf of a customer. Unless an assignee is provided, the ticket is auto-assigned via the agent's routing rules.

chatbase_create_ticket

Create agent Creates a new agent. If `url` is provided, a link source is created from that URL and training is queued automatically. The agent is always created even if source setup or training fails — `id` is always returned. Check `pendingSteps` in the response to see which steps need to be retried: - `ADD_SOURCE` — the URL could not be added as a source. Add the source with `chatbase_create_source`. - `TRAIN_AGENT` — training did not start. There is no way to trigger it directly: sources train when they are written, so re-save the source with `chatbase_update_source`, and check the result with `chatbase_get_source`. When `pendingSteps` is absent, all steps succeeded. Subject to plan agent limits — returns `AGENT_LIMIT_REACHED` (403) when the account has reached its maximum number of agents.

chatbase_create_agent

Create source Creates a new source. Accepts text, qna, and link source types. File sources cannot be created from here — a remote MCP server has no filesystem to read the bytes from; use the Chatbase CLI. Ticket and Notion sources are not accepted. The source starts training immediately — no separate training call is needed. It is returned as `untrained` and flips to `trained` when it is live, or `failed` if training did not land; call `chatbase_get_source` to follow it. **Q&A size limit:** A Q&A source must not exceed 4.5 MB.

chatbase_create_source

Delete agent Permanently deletes an agent and all its sources. Also disconnects any active integrations (Slack, WhatsApp, etc.). This action is irreversible.

chatbase_delete_agent

Delete source Deletes a source. Its knowledge is removed from the agent immediately; the response carries the final state (`deleted`, or `toBeDeleted` while the purge finishes).

chatbase_delete_source

Export conversations Export all conversations with full message history for an agent. Includes conversations from all sources. Tool results are sanitized to remove internal data. Supports cursor-based pagination. Pass `conversationId` to fetch a single conversation from any source (widget, API, WhatsApp, etc.). Pass `include=summary` to omit message bodies for a cheaper triage pass, `source` to restrict to one or more conversation sources, and `startDate` / `endDate` to restrict to a createdAt window.

chatbase_export_conversations