Chatisto MCP server for Claude and ChatGPT | Chatisto Docs

Connect Claude, Claude Code or ChatGPT to Chatisto. Set up support on a website, answer customers from your inbox, look up customers and build chatbot flows from your AI assistant.

The Chatisto MCP server lets you run your website's customer support from an AI assistant. Connect it once, then ask in plain language:

"Add Chatisto to my website https://example.com and install the chat widget."
"Summarize today's open support conversations."
"Which customers asked about refunds this week?"
"Build a chatbot flow that greets visitors and offers Pricing and Talk to a human."

It uses the Model Context Protocol, so it works with any assistant that supports remote MCP servers with OAuth.

Server details

Setting	Value
Server URL	`https://fresh-api.chatisto.com/mcp`
Transport	Streamable HTTP
Authentication	OAuth 2.1 with PKCE. You sign in with your Chatisto account; no API keys.
Rate limit	120 requests per minute per user
Cost	No extra charge. Works on every Chatisto plan.

You need a Chatisto account. If you don't have one, create one for free first.

Connect

Claude (web, desktop and mobile)

In Claude, open Settings → Connectors.
Click Add custom connector.
Name it Chatisto and paste the server URL: https://fresh-api.chatisto.com/mcp
Click Add, then Connect. Sign in to Chatisto in the window that opens and approve access.

The connector syncs across Claude on the web, Claude Desktop and the Claude mobile apps. On Team and Enterprise plans, an organization owner may need to add the connector first.

Claude Code

claude mcp add --transport http chatisto https://fresh-api.chatisto.com/mcp

Then run /mcp inside Claude Code, select chatisto and choose Authenticate. Your browser opens to sign in to Chatisto.

Claude Code is the fastest way to add Chatisto to a website you're building: it can create the workspace and paste the widget code into your layout file for you.

Search for Chatisto in the ChatGPT apps directory and click Connect. If it isn't listed for your account yet, turn on developer mode in ChatGPT's settings and add the server URL above as a custom connector.

Other MCP clients

Any client that supports remote Streamable HTTP servers with OAuth dynamic client registration can connect using the server URL. OAuth metadata is published at https://fresh-api.chatisto.com/.well-known/oauth-protected-resource/mcp.

Set it up with one prompt

Paste this into your assistant. It connects the server if needed, creates your workspace and installs the widget:

Set up Chatisto (AI chatbot + live chat) on my website.

1. Connect the Chatisto MCP server if it isn't connected yet:
   URL: https://fresh-api.chatisto.com/mcp (remote, streamable HTTP, sign in with OAuth)
   - Claude Code: claude mcp add --transport http chatisto https://fresh-api.chatisto.com/mcp
   - Claude or ChatGPT: add it as a custom connector, then sign in to Chatisto.
2. Ask me for my website address, then call add_chatisto_to_website.
3. Install the returned chat widget code: if you can edit my site's code, add it to the shared layout right before </body>. Otherwise give me the steps for my platform (get_widget_install_code).
4. Call get_setup_status and tell me what's live and what's left.

Docs: https://chatisto.com/documentation/mcp

What it can do

Read tools only look at your data. Write tools change something, and the ones marked reaches customers are visible to your website visitors right away. Your assistant should ask you to confirm before using those.

Workspaces and setup

A workspace is one website or brand in Chatisto. Tools use the workspace that's active in the Chatisto app, unless you name another one.

Tool	Type	What it does
`list_workspaces`	Read	Lists the workspaces you can access.
`add_chatisto_to_website`	Write	Creates a workspace for a website, puts an AI chatbot live, starts learning from the website's pages and returns the widget code.
`get_widget_install_code`	Read	Widget code and steps for HTML, WordPress, Shopify, Next.js, React or Nuxt.
`get_setup_status`	Read	Whether the chatbot is live, which websites the knowledge base learns from and when they were last crawled, and whether visitors have started chatting (which confirms the widget is installed).
`refresh_knowledge_base`	Write	Re-crawls the workspace's websites now and sets the automatic re-crawl schedule (off, weekly or monthly).

Inbox

Tool	Type	What it does
`list_conversations`	Read	Recent conversations. Filter by open/closed, assigned to me or unassigned, chat or email, or search text.
`get_conversation`	Read	One conversation with up to 100 latest messages, showing whether the customer, an operator or the chatbot sent each one.
`get_inbox_stats`	Read	Conversations, customers, messages, response times and top operators for 24h, 7d, 1m, 1y or all time, compared with the previous period. Plus how many conversations are open and unassigned right now.
`search_knowledge_base`	Read	Searches the content your AI chatbot answers from. Useful to draft accurate replies.
`reply_to_conversation`	Write, reaches customers	Sends a message in an open web chat as you. If the chatbot was handling the chat, it switches to live chat.
`assign_conversation`	Write	Assigns a conversation to you or a teammate (by email).
`close_conversation`	Write, reaches customers	Closes a conversation and sends your end-of-conversation message.

Customers

Tool	Type	What it does
`search_customers`	Read	Finds customers by name, email or ID.
`get_customer`	Read	Contact details, information collected by forms and the chatbot, and recent conversations.

Chatbot scenarios

A scenario is the flow your chatbot follows: messages, questions, button menus, AI answers and handoffs to a human. See Scenarios.

Tool	Type	What it does
`list_scenarios`	Read	Lists scenarios and shows which one is live.
`get_scenario`	Read	All steps of a scenario in order, plus warnings: buttons that lead nowhere, steps that can't be reached and AI steps visitors can't leave.
`create_scenario`	Write	Creates a new scenario. It stays offline until you activate it.
`rename_scenario`	Write	Renames a scenario.
`delete_scenario`	Write, destructive	Deletes a scenario that isn't live, with all its steps.
`add_scenario_step`	Write	Adds a step: `text`, `question`, `buttons`, `handoff`, `ai_agent` or `condition`.
`update_scenario_step`	Write	Edits a step's message, buttons, next step, question format, image, translations, branches or AI tools.
`delete_scenario_step`	Write, destructive	Deletes a step (and optionally the steps under it).
`set_scenario_start_step`	Write	Chooses the step the chat starts with.
`activate_scenario`	Write, reaches customers	Makes a scenario the live (default) chatbot on your website chat, replacing the current one.
`set_scenario_page_rules`	Write, reaches customers	Starts a scenario instead of the live one on matching pages, e.g. `/pricing*`.
`set_scenario_languages`	Write	Sets the scenario's primary language and the languages its steps are translated into.

What steps can do through the MCP server:

Buttons lead to a step, or open a link with url (signup, pricing, a booking page).
Questions take a question_format (text, email, phone, number or url) and are asked again until the answer matches. save_to_property saves the answer to a contact property, such as business_type. invalid_message sets what the bot says before asking again.
AI steps can have buttons shown under every answer, such as "Back to menu", and ai_tools.handoff lets the AI hand the chat to a human.
Condition steps route by branches (rules on operator availability, business hours, contact properties, earlier answers, page URL, channel or language) with an else_step_id fallback. They send nothing.
Images: text, question, buttons and handoff steps can show image_url (https) with image_alt, image_caption and image_link_url.
Translations: after set_scenario_languages, give each step translations (message, button labels, invalid message, image texts per language). get_scenario warns about missing ones.
Any step can wait delay_seconds before it's sent.

Edits to the live scenario reach visitors immediately. To be safe, build a new scenario, check get_scenario for warnings, then activate it. Setting the default scenario for the email channel isn't supported yet; do it in Scenario → Email.

Permissions

The assistant acts as you. It can only see the workspaces your Chatisto account belongs to, and replies are sent under your name.
Changing chatbot scenarios (creating, editing, activating) requires the owner role in that workspace. Operators can read and answer conversations but not change the chatbot.
Replying to email conversations isn't supported yet. You can read them, assign them and close them.
Nothing can be bulk-deleted. The only destructive tools are delete_scenario_step and delete_scenario, and the live scenario can't be deleted.

Data and privacy

What the assistant can access: your workspaces' conversations, customer profiles, knowledge base content and chatbot scenarios. Only what the tools above return.
Where it goes: tool results are sent to the AI assistant you connected (e.g. Anthropic for Claude, OpenAI for ChatGPT) and handled under that provider's terms. Chatisto only receives the tool calls the assistant makes, not your conversation with the assistant.
Sign-in: OAuth, so the assistant never sees your Chatisto password. Access tokens are valid for 1 day and refresh tokens for 90 days.
Disconnect: remove the Chatisto connector in your assistant's settings (in Claude Code: claude mcp remove chatisto). To revoke all issued tokens on Chatisto's side, email support@chatisto.com.

See our Privacy Policy and Terms of Service.

Troubleshooting

"Sign in to Chatisto to use this tool." Your session expired or wasn't completed. Reconnect the connector (in Claude Code: /mcp → chatisto → Authenticate).
"Only owners of the … workspace can change chatbot scenarios." Ask a workspace owner to make the change or to give you the owner role.
"Conversation not found in your workspaces." The conversation belongs to a workspace you're not a member of, or the ID is from another workspace. Ask the assistant to run list_workspaces and pick the right one.
The assistant uses the wrong website. Say which one, e.g. "use the Acme Store workspace". Tools default to the workspace last active in the Chatisto app.
Too many requests. The limit is 120 requests per minute. Wait a minute and try again.

Support

Questions or problems with the MCP server: support@chatisto.com.