Robylon MCP Server
Read-only remote MCP server (Streamable HTTP, OAuth, no API key) that lets Claude, ChatGPT, Cursor and other AI assistants query a Robylon AI customer-support workspace (email, chat, voice, SMS, WhatsApp). Tools: get_analytics, search_conversations, get_conversation, list_workspaces.
Hosted MCP Server
npx add-mcp 'https://api.robylon.ai/mcp/'Installs into Claude Code, Codex, Cursor and more
Documentation
Robylon MCP server overview
The Robylon MCP server connects any AI assistant that supports remote MCP servers to your Robylon workspaces. Robylon has setup guides for Claude, Claude Code, ChatGPT, Codex, Gemini CLI and Cursor. It works through the Model Context Protocol (MCP). Once connected, you can ask the assistant about your support in plain language, for example “What was our bot resolution rate last month?” or “Show me the worst-rated WhatsApp chats this week”, and it answers from your live Robylon data.
The server is read-only. The assistant can read analytics and conversations, but nothing can be changed, sent or triggered through it.
Connect an AI assistant
Add the server URL https://api.robylon.ai/mcp/ to your AI tool and sign in with your own Robylon account. You need an Admin or Super-admin role in the workspaces you connect. There is no API key. See Setup for the full steps and a guide for each AI tool.
What an AI assistant can do
It can answer questions about your chat, email and WhatsApp performance, and find and read customer conversations on every channel, voice calls included. Voice analytics are not available through the server.
| Ask about | Examples |
|---|---|
| Volume and resolution | Chat and email volume, how much the AI agent resolved on its own, what was escalated, email triage, backlog. |
| Speed | AI agent handle time, queue wait, human first response and agent handle time on handed-over chats. |
| Satisfaction | CSAT for chat and email, and the conversations behind low ratings. |
| Your team | Human agent performance, availability and SLA performance. |
| What customers ask | Intents for chat and email. |
| Chat widget | Page loads, launcher clicks, chats opened and first messages. |
| Template delivery, read and failure rates, failure reasons, and the template funnel. | |
| Revenue | Shopify revenue from WhatsApp campaigns with cost and ROI, and revenue by UTM source, medium and campaign. |
| Usage and credits | Credits per day, split into flat charges and AI usage, and credits used by feature. |
| Specific conversations | Search by channel, status, tag, intent, rating, sentiment, agent or group, then read a full transcript. |
A good question pairs a number with examples: “What was our CSAT in August, and show me three 1-star conversations that explain it.”
MCP server tools
It provides four tools. The assistant picks the right one for each question.
| Tool | What it does |
|---|---|
get_analytics | Reads one card from your Analytics dashboard, calculated exactly as the dashboard calculates it. Used for any total, rate, average or trend. |
search_conversations | Finds conversations using the same search and filters as the Unified Inbox. Returns a summary of each conversation, not the transcript. |
get_conversation | Reads one conversation in full, turn by turn. Accepts the conversation ID shown in the inbox, for example 4521 or #R-4521. |
list_workspaces | Lists the workspaces the connection can read, so the assistant can pick the right one when you connected several. |
Because get_analytics reads the same figures as your dashboard, a number the assistant quotes matches what you see in Robylon for the same card and dates.
Limits
| Limit | Value |
|---|---|
| Access | Read-only. No replies, edits, tags, assignments or workflow runs. |
| Date range | Up to 92 days per request, so a calendar quarter fits. Give both a start and an end date, or neither for the last 30 days. |
| Analytics buckets | Daily, weekly or monthly, for cards that show a trend. |
| Search results | 10 conversations per page by default, up to 50. A search pages through at most 1,000 conversations before asking you to narrow it. |
| Free-text search | Covers about the last three months of messages, the same as the inbox search bar. Filters reach further back. |
| Test conversations | Left out unless you ask for them. |
| Internal notes | Left out of transcripts unless you ask for them. |
| Rate limits | 30 tool calls and 120 requests per minute for each connection, and 100 tool calls per minute for each workspace. Past a limit, the assistant is told how many seconds to wait and tries again. |
Figures for today and yesterday are still being calculated, so they can change after the assistant reads them.
MCP server and the MCP block
They are different features that work in opposite directions.
- The Robylon MCP server (this section) lets an outside AI assistant read data from Robylon.
- The MCP block and connector tools let Robylon’s own AI agents and workflows act in other apps, for example posting to Slack or updating a Zendesk ticket. See the MCP block and API tools and functions.
Customer data and access
The server only reads, so connecting an assistant cannot change anything in your workspace. It does share conversation content with the assistant you connect, including what customers wrote, so connect only assistants your company has approved for customer data.
Access is controlled per person. Each connection belongs to the person who signed in, covers only the workspaces they ticked, and needs an Admin or Super-admin role in each one. Admins can see every connection to their workspace and disconnect anyone from Settings → Robylon MCP. See Setup.