Model Context Protocol
Connect Chaterimo to Claude and other AI agents
The Chaterimo MCP connector gives AI agents direct access to your e-commerce support workspace: chatbot performance, conversations, product catalog, tickets, leads, and sales rules.
Recommended setup
Use the universal read-only OAuth endpoint for Claude-style analysis workflows and directory submission.
https://www.chaterimo.com/mcp-readonlyUse the full-access OAuth endpoint only when you intentionally want write actions such as updating chatbot settings.
What agents can do
- Review chatbot performance and support trends.
- Audit recent customer conversations and recurring issues.
- Search the trained product catalog and knowledge base.
- List tickets, leads, and sales rules inside the same workspace.
Example prompts
- "How did my chatbot perform in the last 7 days?"
- "Show me recent conversations about shipping delays."
- "Search my catalog for wireless headphones under 150 EUR."
- "List open tickets and leads captured this week."
How to connect
- Copy the read-only OAuth MCP URL shown on this page.
- In Claude, open Settings, then Connectors, then Add custom connector.
- Paste the connector URL and save.
- Complete the Chaterimo OAuth sign-in and choose the organisation Claude should access.
Legacy token-in-URL endpoints are still available from the API keys dashboard for internal testing and older clients, but Anthropic-facing setups should use OAuth.
Connection requirements
- Requires a Chaterimo account.
- Requires at least one connected chatbot or store.
- Data access always stays scoped to the authenticated organisation.
- OAuth is used for remote MCP authentication.
- Read-only URLs are preferred for agent analysis workflows.
OAuth endpoints
| Mode | URL |
|---|---|
| Read-only | https://www.chaterimo.com/mcp-readonly |
| Full access | https://www.chaterimo.com/mcp |
Shared MCP rate limits
MCP limits are enforced per organisation and shared across all connector sessions and API keys in that organisation.
| Tier | Per minute | Per day |
|---|---|---|
| Free / churned | 5 | 5 |
| Trial | 10 | 100 |
| Paid | 30 | 1000 |
Privacy and security
- Connector access is scoped to your organisation only.
- MCP tool-call logs store structural metadata instead of raw payload content.
- Transport uses HTTPS.
- Read-only connectors avoid exposing write tools to the agent.
- OAuth access tokens are bound to the specific MCP resource URL.
