Developers
Connect Ringhum to Claude and other AI tools (MCP)
Add Ringhum as a connector in Claude, ChatGPT, Cursor, VS Code and other AI apps that support the Model Context Protocol, choose read-only or read-and-change access, and disconnect an app.
5 min read Updated 24 September 2026
On this page
Ringhum has an MCP server. MCP (Model Context Protocol) is a standard way for AI apps to use outside tools. Once you connect Ringhum to an AI app such as Claude or ChatGPT, you can ask it questions about your workspace in plain language. For example: "Summarise yesterday's missed calls", "Which callers asked for a callback this week?" or "Add our new opening hours to the FAQs". The AI app works through the same rules and permissions as the Ringhum API.
What you need
- Server URL:
https://ringhum.com/mcp. It is also shown in the MCP server card on the Developers page, with a Copy button. - An AI app that supports remote MCP servers, such as Claude, ChatGPT, Claude Code, Cursor, Windsurf or VS Code.
- Owner or Admin role in the workspace. Only owners and admins can connect an app or create an API key.
There are two ways to connect. Signing in is the easiest and suits chat apps like Claude and ChatGPT. An API key suits developer tools that take a URL and a header.
Read-only or read-and-change access
You choose how much the AI app may do.
| Access | What the app can do |
|---|---|
| Look things up (read only) | Read calls and transcripts, appointments, contacts, the inbox, messages, orders, reservations, assistants and the knowledge base. |
| Look things up and make changes | Everything above, and also create and update assistants, add knowledge, book and cancel appointments, update contacts, send messages and place calls. |
With read-only access, the tools that change things are not offered to the app at all.
Important: With change access, the AI app can send real messages and place real calls to your customers. Ringhum marks these tools as reaching outside your workspace, and deletions as destructive, so most AI apps ask you before running them. Read what the app is about to do before you approve it.
Connect Claude by signing in
- In Claude (on the web, desktop or mobile), open Settings → Connectors and choose Add custom connector.
- Paste
https://ringhum.com/mcpas the URL and save. - Click Connect. A Ringhum page opens. Sign in if you are asked to.
- On the Connect page, choose the Workspace the app may use.
- Under What it may do, choose Look things up or Look things up and make changes.
- Click Allow. You are sent back to Claude.
The app never sees your password. The exact menu names in Claude can change over time; look for connectors or integrations in its settings.
ChatGPT: add the URL as a custom connector (MCP server) in Settings → Apps & Connectors, then click Connect and follow steps 3 to 6.
Claude Code: run the command below, then run /mcp and choose Authenticate.
claude mcp add --transport http ringhum https://ringhum.com/mcp
After you allow access, the connection renews itself as long as you keep using it. If the app is not used for 90 days, you will need to connect it again.
Connect with an API key
Use this for tools that let you set a request header, or when you do not want to sign in.
- On Developers, create an API key. Tick only read for a read-only connection, or read and write to allow changes. See API keys and scopes.
- Add the server to your app with the key in the
Authorizationheader.
Claude Code:
claude mcp add --transport http ringhum https://ringhum.com/mcp \
--header "Authorization: Bearer ck_live_…"
Cursor (~/.cursor/mcp.json), Windsurf and Claude Desktop:
{
"mcpServers": {
"ringhum": {
"url": "https://ringhum.com/mcp",
"headers": { "Authorization": "Bearer ck_live_…" }
}
}
}
VS Code (.vscode/mcp.json):
{
"servers": {
"ringhum": {
"type": "http",
"url": "https://ringhum.com/mcp",
"headers": { "Authorization": "Bearer ck_live_…" }
}
}
}
An app that can only run local servers can connect through npx mcp-remote https://ringhum.com/mcp --header "Authorization: Bearer ck_live_…".
What the tools cover
Every operation in the Ringhum API is available as a tool: your account and usage, assistants, phone numbers, calls and transcripts, contacts, appointments and availability, orders and products, room reservations, the inbox, text and WhatsApp messages, campaigns, webhooks, the company profile, services, FAQs and knowledge base, unanswered questions, payment links, review requests, revenue and spam protection. Call recordings are the one exception: they are not available as a tool.
Each tool runs the matching API request, so the same plan limits, validation and rate limits apply. Tool calls count toward the API's limit of 120 requests a minute. The full list of tools is in the MCP section of the API reference at /docs.
See and disconnect connected apps
Apps you connected by signing in are listed on Developers under Connected AI apps, with who connected them, their Access (Read only or Read and change) and when they were last used.
To remove an app, click Disconnect and confirm. It loses access at once and has to be approved again. To change an app's access, disconnect it and connect it again with the other choice.
For a connection made with an API key, revoke the key under API keys.
Troubleshooting
"Only owners and admins of a workspace can connect apps." Ask the workspace owner to connect the app, or to make you an Admin. See Invite your team.
"The sign-in request expired. Start connecting again from your AI app." The approval page was open too long. Start again from the AI app.
The app says it is not authorised, or asks you to sign in again. The app was disconnected, the key was revoked, or you are no longer a member of the workspace. Connect it again.
The app cannot make changes. It was connected with read-only access, or its API key lacks the write scope.
The app is looking at the wrong workspace. Ask it to call who_am_i to check. Each connection uses one workspace. Disconnect it and connect again to pick another.
Related articles
API keys and scopes
Create and revoke API keys on the Developers page, choose read or write access, and learn the basics of the Ringhum REST API - base URL, authentication, pagination, errors and rate limits.
Webhooks
Receive signed HTTPS notifications when calls end, messages are taken, appointments, orders and reservations change, or a campaign finishes, and verify that each one really came from Ringhum.
Security, privacy and your data
How to protect your login with two-factor authentication, see and end your sessions, control who can hear recordings, set how long transcripts and audio are kept, and export or delete your data.
Invite your team and set roles
How to invite people to your workspace, what each role can do, how seats work on each plan, and how to run several workspaces from one login.
Still stuck?
Email [email protected] or send us a message. Team and Scale plans get priority support.