Overview
Rilla MCP is a Model Context Protocol server. Connect it to Claude, Claude Code, Cursor or ChatGPT, log in with your Rilla account, and ask questions about your reps, teams and conversations in plain language: “Which reps on the West team had the lowest talk ratio last week?” or “Summarize my calls with the Lee family.” The assistant answers from live Rilla data.
Server URL
https://customer.rillavoice.com/mcpConnect a client
Step-by-step setup for Claude, Claude Code, Cursor and ChatGPT.
Sign-in and access
Who can connect, and what each person can see.
Troubleshooting
Login loops, permission errors and missing data.
How it works
Add https://customer.rillavoice.com/mcp to your AI tool as a remote MCP server or custom connector. There is no API key or header to configure.
The tool opens Rilla’s login page in your browser. Sign in the way you sign in to the Rilla web app, including single sign-on.
The assistant chooses which Rilla tools to call, reads the results and answers. Every tool only reads data; nothing in Rilla is created, changed or deleted.
MCP or the Data Export API?
Use Rilla MCP to ask questions and explore: one person, their own login, answers in a chat. Use the Data Export API to load data into a warehouse, spreadsheet or BI tool on a schedule: an API key, every field, every page.
Sign-in and access
Every MCP session is a logged-in Rilla user. Your AI tool sends you through Rilla’s login page at login.rilla.com and keeps the resulting session; Rilla never sees your AI tool’s account, and the tool never sees your password.
Who can connect
Admins and Team Managers can connect, the same people who can open Settings → Developer in the Rilla web app. Other roles can log in but every request returns 403 Forbidden.
What you can see
Rilla MCP shows you the same data the Rilla web app shows you, based on your role’s permissions:
| Your access in Rilla | What the assistant can read |
|---|---|
| Your organization’s conversations | Every rep, team and conversation in your organization |
| Your team’s conversations | Your teams and their subteams, their reps and their conversations, and your own |
| Only your own conversations | Your own conversations and numbers |
If your role can also see top performers’ conversations, those are included. Connecting never widens what you can see, and you don’t need an API key.
Staying connected
Your AI tool renews its access in the background, so you don’t have to log in again each time it expires. Logging out of the Rilla web app does not disconnect it.
Disconnecting
To stop an AI tool reading your Rilla data, remove Rilla from it:
| Client | How to disconnect |
|---|---|
| Claude and Claude Desktop | Disconnect or remove the Rilla connector under Customize → Connectors. On Team and Enterprise plans, members disconnect their own login; only an owner can remove the connector, in Organization settings → Connectors. |
| Claude Code | Run claude mcp remove rilla. |
| Cursor | Delete the rilla entry from your mcp.json. |
| ChatGPT | Remove the Rilla plugin. |
An Admin can end someone’s access by changing their role to one that can’t connect, or by removing them from Rilla. It takes effect within an hour.
Limits
- Read-only. No tool creates, edits or deletes anything in Rilla.
- Paged results. Long lists and transcripts come back a page at a time, sized so one result fits comfortably in the assistant’s context. The assistant asks for more pages when it needs them.
- Your data, your scope. Results never include reps, teams or conversations outside your access.
Troubleshooting
| Symptom | What to do |
|---|---|
The tool keeps asking you to log in, or shows 401 Unauthorized | Your session expired or was revoked. Log in again: in Claude Code, run /mcp and select rilla; in other clients, disconnect Rilla and connect it again. If that doesn’t help, remove Rilla from your client and add it again with the server URL. |
| Your client can’t add the server, or Rilla’s login page shows an error | Rilla MCP works with the clients in Connect a client. Other MCP clients can’t log in to Rilla yet, even if they support remote servers. |
403 Forbidden on every request | Your role can’t use Rilla MCP. Ask an Admin in your organization; Admins and Team Managers can connect. |
| A tool replies “You don’t have access to …” | Your role can’t read that data in Rilla. Team lists and team numbers need access to your team’s or organization’s conversations. Ask an Admin to check your role’s permissions. |
| A rep, team or conversation is missing | It is outside what your role can see in the Rilla web app, or outside the date range you asked about. |
| The tool can’t find the server | Check the URL is exactly https://customer.rillavoice.com/mcp, with /mcp at the end. |
For setup steps per client, see Connect a client.