ReadyToTalk MCP — setup guide

Connect Claude, ChatGPT, or any MCP client, to your ReadyToTalk front office. The connector reads: your business and everything below it — calls, messages, customers, activity, billing, receptionists, call routes, phone numbers, menu audio and the dashboard. It changes nothing; setup stays in the ReadyToTalk app.

1. Endpoint

The MCP server speaks streamable HTTP at:

https://api.readyto.talk/mcp

2. Sign in

Claude (the connectors directory, or Settings → Connectors → add https://api.readyto.talk/mcp): the server answers a 401 that names its sign-in, Claude sends you to Cracked Robot's sign-in page, and you come back signed in as the ReadyToTalk account that has your email. Use the email your ReadyToTalk account is signed up with.

ChatGPT (the plugin directory, or Settings → Connectors → Developer mode → add https://api.readyto.talk/mcp): the same sign-in, the same account, the same tools. A sign-in whose email has no ReadyToTalk account yet gets one made, empty, and every tool then says where to set the business up.

Other clients: pass a Personal Access Token from the ReadyToTalk app as a Bearer token:

Authorization: Bearer rtt_<your-token>

Every tool call runs as the signed-in user and is scoped to your businesses by the same permissions as the REST API.

3. The tools

Every tool is a read and is marked read-only; a tool on a business names the business by its id, as the app's address bar shows it.

• Business: the business, its activity, calls and a call's recording link, text messages, customers.
• Billing: subscription, credits, charges, payment method on file.
• Receptionists: the AI receptionists, their prompts (draft, live, versions) and documents.
• Call routes and numbers: routes, their menus and versions; phone numbers and each number's routing menu; menu audio.
• Dashboard: the dashboard and its setup tasks.

Not tools: the account and its tokens, the platform's catalogues, partner integrations, and anything that creates, changes or deletes.

4. Cursor and other stdio-only clients

A client that speaks stdio only can bridge the remote server with mcp-remote (needs Node.js). Add this to the client's MCP config:

{
  "mcpServers": {
    "readytotalk": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://api.readyto.talk/mcp",
        "--header", "Authorization: Bearer rtt_<your-token>"
      ]
    }
  }
}

Restart the client; the ReadyToTalk tools appear once connected.

5. Questions

Support for the connector, as for the app: support@sevenolives.com. Say which client you connect from and, for a tool that answers an error, the tool's name and the time. The privacy policy and terms cover the connector as they cover the app and the API.