Connect Rymi to your AI client

Rymi runs a hosted MCP server at https://mcp.rymi.live/mcp. Add it to an AI client and the client can build voice agents, place calls and read results for you. This page has the setup for each client. For the tool list and what each role can reach, see MCP server.

Two ways to sign in, and every client uses one of them:

• OAuth. The client opens a Rymi sign-in page. No key to copy. Use this wherever the client supports it.
• Secret key. The client sends Authorization: Bearer rymi_… on every request. Create the key in Studio under Settings → API keys. Publishable keys (rymi_pk_…) are rejected.

Paste the OAuth URL exactly as written, with no trailing slash. OAuth identifies the server by that string, and …/mcp/ is a different one. The key-based configs below use https://mcp.rymi.live/, which the server also accepts.

What has been checked

The hosted endpoint, OAuth sign-in and key sign-in are Rymi's own and run in production. The per-client steps below follow each vendor's documented MCP setup. We have not re-tested every client's interface, and their menus change. If a step doesn't match your screen, the URL and sign-in method are what matter.

Grok and Dots are untested. Grok is listed because xAI documents remote MCP support. We have not run Rymi through it. We don't know the Dots client, so there are no steps for it. Any client that accepts a remote Streamable HTTP MCP URL should work with the generic config at the end.

Claude

Works in Claude on the web and in Claude Desktop.

1. Open Settings → Connectors.

2. Choose Add custom connector, name it Rymi, and paste:

   https://mcp.rymi.live/mcp

3. Connect, then sign in to Rymi when the browser opens.

Claude Code

claude mcp add --transport http rymi https://mcp.rymi.live/mcp

Run /mcp inside Claude Code, pick rymi, and choose Authenticate. With a secret key instead:

claude mcp add --transport http rymi https://mcp.rymi.live/ \
  --header "Authorization: Bearer rymi_your_secret_key"

Cursor

Add to Cursor registers the server, and Cursor opens the sign-in page.

By hand, add this to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "rymi": {
      "url": "https://mcp.rymi.live/mcp"
    }
  }
}

VS Code

Add to VS Code registers the server. By hand, add this to .vscode/mcp.json:

{
  "servers": {
    "rymi": {
      "type": "http",
      "url": "https://mcp.rymi.live/mcp"
    }
  }
}

Start the server from the MCP: List Servers command, sign in, then pick Rymi's tools in Copilot Chat.

ChatGPT

ChatGPT supports remote MCP servers as custom connectors, on some plans and behind a developer-mode switch.

1. Open Settings → Connectors and enable developer mode if it is offered.
2. Create a connector with the URL https://mcp.rymi.live/mcp and OAuth sign-in.
3. Sign in to Rymi, then enable the connector in the chat composer.

Windsurf

Windsurf names the URL field serverUrl, not url. Add this to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "rymi": {
      "serverUrl": "https://mcp.rymi.live/",
      "headers": {
        "Authorization": "Bearer rymi_your_secret_key"
      }
    }
  }
}

Refresh the MCP list in Windsurf after you save.

Grok (xAI API, untested)

xAI's Responses API takes a remote MCP server as a tool, with the key in authorization. See xAI remote MCP for the current fields.

{
  "tools": [
    {
      "type": "mcp",
      "server_url": "https://mcp.rymi.live/",
      "server_label": "rymi",
      "authorization": "Bearer rymi_your_secret_key"
    }
  ]
}

Any other client

Point any client that speaks Streamable HTTP MCP at this config:

{
  "mcpServers": {
    "rymi": {
      "type": "http",
      "url": "https://mcp.rymi.live/",
      "headers": {
        "Authorization": "Bearer rymi_your_secret_key"
      }
    }
  }
}

A client with no HTTP support can run the local server instead: npx -y @rymi/mcp with RYMI_API_KEY set. See Run it locally.

Try it

Once connected, ask:

"List my Rymi agents."

Then something that builds:

"Create a receptionist agent for BrightSmile Dental, then tell me what's missing before I publish it."

More prompts are in Example prompts.

If it doesn't connect

Symptom	Cause
401 right after sign-in	The URL has a trailing slash on an OAuth connector. Use https://mcp.rymi.live/mcp.
401 with a key	The key is publishable (rymi_pk_…), revoked, or missing the Bearer prefix.
Fewer tools than the docs list	The server shows only what your role and key scopes allow. See Mutating tools and what limits them.
Tools missing in Windsurf	The list needs a manual refresh after editing the config.