Robylon MCP server overview
The Robylon MCP server connects AI assistants such as Claude, ChatGPT and Cursor to your Robylon workspaces 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.
How do I 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 can an AI assistant do with the Robylon MCP server?
It can answer questions about your support performance and find and read customer conversations, across chat, email, social and voice.
| Ask about | Examples |
|---|---|
| Volume and resolution | Chat, email and voice volume, how much the AI agent resolved on its own, what was escalated, backlog. |
| Speed | Chat response time, ticket reply time, resolution time. |
| Satisfaction | CSAT for chat and email, and the conversations behind low ratings. |
| Your team | Human agent performance, availability, chat assignment and SLA performance. |
| What customers ask | Intents for chat and email, and knowledge gaps. |
| Usage and credits | Credits used by feature, voice minutes, the WhatsApp template funnel. |
| 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.”
Which tools does the Robylon MCP server provide?
It provides three 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. |
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.
What are the limits?
| Limit | Value |
|---|---|
| Access | Read-only. No replies, edits, tags, assignments or workflow runs. |
| Date range | Up to 90 days per request. With no dates given, 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. |
Figures for today and yesterday are still being calculated, so they can change after the assistant reads them.
Is the Robylon MCP server the same as the MCP block in workflows?
No. They 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, such as posting to Slack or updating a Zendesk ticket. See the MCP block and API tools and functions.
Is my customer data safe when I connect an AI assistant?
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.