🚀 Two ways to run it

☁️ Hosted — no install, no API key

Add https://mcp.rymi.live/mcp as a custom connector and sign in. In Claude: Settings → Connectors → Add custom connector. Paste the URL exactly — no trailing slash, since OAuth identifies the server by that string.

Signing in grants the connector everything you can do in Rymi, acting as you. Revoke any time from Settings.

Clients without OAuth (and CI) can pass a secret key against the same host instead:

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

💻 Local — via npx

Run the server on your own machine — it speaks stdio by default and talks to the Rymi REST API directly. The key is read from the RYMI_API_KEY environment variable.

{
  "mcpServers": {
    "rymi": {
      "command": "npx",
      "args": ["-y", "@rymi/mcp"],
      "env": {
        "RYMI_API_KEY": "rymi_your_secret_key"
      }
    }
  }
}

Options: RYMI_MCP_READONLY=1 hides every mutating tool (including create_call, batch_call, publish_agent).

This package speaks stdio only. --transport http was removed in 2.0.0 — use the hosted endpoint above, which the local server could never match on auth (it has no OAuth, and no per-key tool gating).

🧰 Tools

⚠️ Gated tools

create_call and batch_call place real, billable outbound calls; publish_agent flips an agent live to end users.

What restrains them depends on which server you're talking to.

• Hosted mcp.rymi.live — tools are filtered by your tenant role, on both OAuth and API keys. An owner/admin sees everything; a member gets agent-scoped tools only, with account-scoped writes (billing, keys, numbers, DNC) never registered. RYMI_MCP_READONLY does not apply there.
• Local @rymi/mcp — no role filtering. Full write surface unless you start it with RYMI_MCP_READONLY=1, which hides every mutating tool at once. That flag is set by whoever starts the server, so it guards a local run you configure, not a key you hand out.

Either way, role filtering bounds the tool surface, not the credential: a key or token stays valid against the REST API directly. Treat MCP access as equivalent to handing over your own account access.

Carrier connect/disconnect and publishable-key creation/revocation are intentionally not exposed over MCP (they enter credentials and change standing configuration) — do those from the dashboard.

⚙️ Configuring an agent

create_agent and update_agent accept the full agent configuration surface. Always call list_llm_options first to get valid model and voice IDs.

📖 Documentation

Full reference and guides: docs.rymi.live/api/mcp

📄 License

MIT © Rymi