AI assistants
MCP server
With the MCP server you use your bots in ChatGPT, Claude and other AI assistants that support the Model Context Protocol. For example, ask in ChatGPT: "Ask the Kindercentrum bot what the opening hours in Ghent are." The assistant asks your bot the question and returns the answer with the sources.
You don't need a key. When connecting, you log in with your Chat on Page account and choose which bots the assistant gets access to.
https://chatonpage.com/mcpConnect
- In your AI assistant, add a new connector or MCP server with the URL above.
- The assistant opens a Chat on Page window. Log in with your regular account (the same one as for the portal).
- Choose the account and the bots, or all bots, and click Grant access.
- You return to the assistant. It can now retrieve your bots and ask them questions.
The menus differ per assistant and sometimes change. Below are the steps as they currently look.
ChatGPT
- Open Settings → Apps & Connectors. For custom connectors, developer mode must be turned on (under Advanced). In a business workspace an administrator may need to allow this first.
- Choose Create or Add connector. Name: Chat on Page. URL:
https://chatonpage.com/mcp. Authentication: OAuth. - Confirm and log in to Chat on Page. Then turn on the connector in a conversation.
Claude
- On claude.ai or in the app, open Settings → Connectors and choose Add custom connector.
- Name: Chat on Page. URL:
https://chatonpage.com/mcp. You don't need to enter a client ID or secret. - Click Connect, log in and choose the bots.
In Claude Code:
claude mcp add --transport http chatonpage https://chatonpage.com/mcp
Then run /mcp in Claude Code to log in.
Other clients
Any MCP client with Streamable HTTP and OAuth works, such as Cursor, VS Code or Windsurf. Usually a configuration like this one is enough. The client will then ask you to log in.
{
"mcpServers": {
"chatonpage": { "url": "https://chatonpage.com/mcp" }
}
}
Login and consent
When connecting, Chat on Page shows which application is requesting access. There you choose:
- The account, if you belong to more than one account.
- The bots: one or more bots, or all bots in the account (including bots you add later).
- Leads: whether the assistant may also read leads, complaints and bug reports from those bots. Disabled by default.
Without access to leads, the assistant can only ask questions to those bots, just like a visitor in the chat on your website. It cannot make any changes and cannot see other conversations. If you reconnect, you can make a different choice.
Tools
The server provides three tools, plus three more with lead access. The assistant decides when to use them.
list_bots
Returns the bots of this connection: id, name, website, languages, greeting, start buttons and locations. Requires no input.
ask_bot
Asks a bot a question.
| Input | Type | Meaning |
|---|---|---|
message | text | The question, or the user's answer to a question from the bot. |
bot_id optional | number | The bot from list_bots. Can be omitted if the connection has only one bot. |
conversation_id optional | text | From a previous answer, to continue the same conversation. |
locale optional | text | Language of a new conversation. Defaults to the bot's language. |
The response contains conversation_id, content (Markdown), sources, choices, office_options and escalated, as in the REST API. With choices the bot asks the user to choose. The assistant shows the choices and sends the chosen text back with the same conversation_id.
get_conversation
Returns all messages of a conversation started via this connection. Input: conversation_id and optionally bot_id.
Forward leads
With access to leads, the assistant can follow up on new leads and pass them to other tools you’ve connected, such as your CRM. For example, ask: "Add new Chat on Page leads to HubSpot and mark them as contacted." For automatic integration without an assistant, use webhooks.
list_events
Events from the bots, oldest first: lead.created, lead.updated and report.created, with the same content as with webhooks. Input: after (the next_after from the previous call, to get only new events), types, bot_id and limit.
list_leads
Leads, newest first, with name, email address, phone number, question, summary and follow-up. Input: status, bot_id, since, before and limit.
update_lead
Updates a lead’s follow-up to contacted or closed. This is only possible if the person who connected has permission to follow up on leads in the account (not with the Reader role).
Manage and disconnect
In the portal under Connections → MCP connections, you can see which applications are connected, by whom and when they were last used. There, you can adjust the bots and access to leads, or break a connection. A disconnected application immediately loses access.
Conversations via MCP are listed under Conversations and count towards the answers in your subscription. Each connection has a limit of 60 questions per minute.
Technical
- Transport: Streamable HTTP at
https://chatonpage.com/mcp. - Authorisation: OAuth 2.1 with PKCE (S256) and dynamic client registration (
https://chatonpage.com/oauth/register). - Metadata:
https://chatonpage.com/.well-known/oauth-protected-resourceandhttps://chatonpage.com/.well-known/oauth-authorization-server. Scope:mcp:use. - Access tokens are valid for 8 hours. The client renews them automatically with a refresh token, which is valid for 60 days.