chatbase_chat
ChatGPTChat with an agent Send a message to an agent and receive a response. Streaming is not available over MCP; responses are always returned complete.
Overview
Chatbase lets teams build and operate AI agents trained on their own business content, and run support end to end - chat widgets, help-desk tickets, and the sources those agents are trained on. This connector gives an MCP client direct access to a connected Chatbase account: list and inspect agents, create and update knowledge sources, update agent configuration, export conversations, and read, create, and update help-desk tickets and their messages.
Tools
chatbase_clone_agent
ChatGPTClone 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_create_agent
ChatGPTCreate 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_source
ChatGPTCreate 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_ticket
ChatGPTCreate 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_message
ChatGPTAdd 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_delete_agent
ChatGPTDelete agent Permanently deletes an agent and all its sources. Also disconnects any active integrations (Slack, WhatsApp, etc.). This action is irreversible.
chatbase_delete_source
ChatGPTDelete 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_export_conversations
ChatGPTExport 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_get_agent
ChatGPTGet agent Returns a single agent by ID.
chatbase_get_source
ChatGPTGet source Returns a single source by ID.
chatbase_get_sources_summary
ChatGPTGet sources summary Returns aggregated counts and sizes for each source type, plus a flag if the chatbot knowledge base requires a retrain to reflect any changes
chatbase_get_ticket
ChatGPTGet a ticket Returns a single ticket by its per-agent ticket number.
chatbase_list_agents
ChatGPTList agents Returns a paginated list of all agents for the authenticated account.
chatbase_list_helpdesk_teams
ChatGPTList teams Returns the teams configured for an agent, ordered by creation date. Exactly one team is marked as the default for the agent.
chatbase_list_sources
ChatGPTList sources Returns a paginated list of sources for an agent. Ticket sources are excluded. For link sources only individual or sitemap/crawl parent links are returned with aggregated children metadata.
chatbase_list_ticket_messages
ChatGPTList ticket messages Returns a ticket's message thread in chronological order. Supports cursor-based pagination.
chatbase_list_ticket_statuses
ChatGPTList ticket statuses Returns the active (non-archived) ticket statuses configured for an agent, ordered by category then position. Each category has exactly one default status.
chatbase_list_tickets
ChatGPTList tickets Returns tickets for an agent, sorted by
updatedAt descending by default. Supports filtering and cursor-based pagination. Filters combine with AND across parameters.chatbase_search_conversations
ChatGPTSearch conversations Search an agent's conversations by text, filters, or both. With
query, results are ranked and carry a highlighted snippet; without it, most recently active first. Filters combine with AND; comma-separated values within a filter with OR. Covers conversations created since the 1st of the month 12 months ago (UTC), activity-date filters included. Results lag new messages by a few seconds. A page can hold fewer than limit items, even none, while hasMore is true; keep paging. Read messages via export with conversationId. Up to 5 searches per call in searches; results keep their order, each with its own pagination or error. To page one, call again with just that search and its cursor.chatbase_search_tickets
ChatGPTSearch tickets Searches ticket messages with a free-text query and returns matching tickets ranked by relevance. Results are capped and not paginated.
chatbase_update_agent
ChatGPTUpdate agent Partially updates an agent. Only provided fields are changed.
notificationsSettings has only two digests, dailyLeadsCollected and dailyConversations — there is no ticket-level notification setting. Passing null disables both. To turn one off, send just that key with active: false; its emails list is still required.chatbase_update_agent_auto_retrain
ChatGPTToggle auto-retrain Enables or disables automatic retraining. When enabled, the agent retrains every 7 days to reflect any source changes. Requirements: - The agent must have been trained at least once — returns
AGENT_NOT_TRAINED (409) otherwise. - Requires the Standard plan or higher — returns PLAN_FEATURE_NOT_AVAILABLE (403) on unsupported plans.chatbase_update_conversation
ChatGPTPause or resume a conversation Pause or resume an ongoing conversation. A paused conversation stops receiving AI replies but still records incoming messages.
chatbase_update_source
ChatGPTUpdate source Updates an existing source. Accepts text, qna, and link sources. File sources cannot be updated from here — a remote MCP server has no filesystem to read the bytes from; use the Chatbase CLI. A content change retrains the source immediately (status
updated until it is live again). Link URL is immutable — to change it, delete and recreate the source. Ticket and Notion sources are not accepted. Q&A size limit: A Q&A source must not exceed 4.5 MB.chatbase_update_ticket
ChatGPTUpdate a ticket Partially updates a ticket's status, assignee, team, or priority. Only provided fields are changed. Fields are validated together but written independently, so a 500 can leave a partial update.
chatbase_whoami
ChatGPTReports 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.
