Connect guides

Step-by-step setup for Claude (claude.ai, Claude Code, Claude Desktop), ChatGPT developer mode, Gemini CLI and SDK, Microsoft Copilot Studio, Muse, and any other MCP client.

Every guide below boils down to the same three moves: paste the MCP URL, let the client identify itself, have your user sign in to Simp and tap Approve. The URL is the only thing you need.

text

https://voice.simpmobile.com/mcp

Simp speaks MCP 2026-07-28 only: stateless Streamable HTTP, no initialize, no session. It advertises OAuth discovery metadata and accepts Client ID Metadata Documents, so a current MCP client needs no client ID or secret. A client that only speaks an older protocol revision is answered -32022 with the supported version and must be updated. Claude, Claude Code and ChatGPT speak 2026-07-28 (observed on 2026-10-05); for any other client, check its release notes. If your client insists on credentials, see Other MCP clients.

Claude#

Claude on the web and in the apps (claude.ai)#

For an individual Pro or Max plan:

Go to Customize > Connectors.
Click + Add, then Add custom connector.
Enter a name (Simp) and paste the Simp MCP URL as the remote MCP server URL. Click Continue.
Review the authentication settings Claude detected. Under OAuth client, keep Use Claude's published identity (Recommended): that is Claude's Client ID Metadata Document, which Simp accepts. Register automatically is dynamic client registration, which Simp does not offer. Click Continue.
When asked how people connect, choose Sign in now (or Sign in when needed). Your browser opens Simp: sign in and tap Approve.
In a conversation, open the + menu, choose Connectors, and switch Simp on.

To change a connector, remove it (Remove, or the three dots beside it) and add it again.

On Team and Enterprise plans an Owner adds the connector first under Organization settings > Connectors (Add, hover Custom, choose Web, then the same steps); each member then finds it under Customize > Connectors and clicks Connect to sign in to their own Simp account. Tools and data stay per user - one Simp account per person.

Then try: "Use Simp to call the sandbox number and book a table for two on Friday at 7" (the number is on the Quickstart). The user is asked to approve the task in the Simp app.

Claude Code#

bash

claude mcp add --transport http simp https://voice.simpmobile.com/mcp

Then run /mcp inside Claude Code and pick Simp to authenticate - the browser opens Simp, you sign in and tap Approve. Tokens are stored by Claude Code and refreshed automatically.

Claude Desktop via a config file#

If you prefer the config file, bridge through mcp-remote (Settings > Developer > Edit Config, then restart Claude Desktop):

json

{
  "mcpServers": {
    "simp": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://voice.simpmobile.com/mcp"]
    }
  }
}

mcp-remote uses an ephemeral loopback port for the OAuth redirect; Simp accepts loopback redirect URIs on any port, as RFC 8252 requires.

ChatGPT#

ChatGPT adds custom MCP servers in developer mode, which is available to Pro, Plus, Business, Enterprise or Education accounts on the web. Copy the URL above first, then:

In ChatGPT, open Settings → Security and login and turn on Developer mode (needs Pro, Plus, Business, Enterprise or Education).
Go to Plugins, select the plus button, name it Simp, and paste the URL above. Pick OAuth and leave client ID and secret blank.
ChatGPT sends you to Simp - sign in and tap Approve.
Ask ChatGPT to make a call for you - it should ask to use Simp for this.

On a phone the ChatGPT app cannot add connectors: open chatgpt.com in your browser, sign in, and follow the same path (Settings > Security and login > Developer mode, then Plugins and the plus button). ChatGPT's MCP tools then work in the app as well.

On the default connection mode every task ChatGPT creates waits for the user's approval in the Simp app. A user who trusts the connection can switch it to Notify only under Connected apps in Simp; only they can change that - see Permission modes.

Gemini#

Gemini CLI#

bash

gemini mcp add --transport http simp https://voice.simpmobile.com/mcp

or in ~/.gemini/settings.json:

json

{
  "mcpServers": {
    "simp": {
      "httpUrl": "https://voice.simpmobile.com/mcp",
      "oauth": { "enabled": true }
    }
  }
}

The first connection returns 401, the CLI discovers Simp's OAuth metadata and opens your browser. If it does not, run /mcp auth simp inside the CLI. OAuth needs a local browser and a loopback redirect on http://localhost:<random-port>/oauth/callback - Simp accepts that; headless or SSH sessions without a browser will not work.

Gemini SDK and other Google agent frameworks#

Any MCP-capable client in the Gemini ecosystem connects the same way: Streamable HTTP transport at the URL above, OAuth discovered from https://voice.simpmobile.com/.well-known/oauth-authorization-server, PKCE S256, and a Client ID Metadata Document as the client's identity. If the framework wants you to supply an OAuth client yourself, host a metadata document and pass its URL as the client_id (see Authentication).

Microsoft Copilot Studio#

Copilot Studio supports Streamable HTTP MCP servers with OAuth 2.0 dynamic discovery. Simp's discovery documents are complete, but Simp no longer offers dynamic client registration: if Copilot Studio stops at registering a client, ask us for pre-registered credentials (see Other MCP clients).

Open your agent and go to the Tools page.
Select Add a tool, then New tool, then Model Context Protocol.
Fill in Server name (Simp), a short Server description ("Gives the user's simp tasks: calls, and asking, telling or chasing people by a deadline. The user approves every task in the Simp app.") and the Server URL above. The description is what the orchestrator uses to decide when to call the server, so keep it accurate.
For authentication choose OAuth 2.0, then Dynamic discovery, and select Create.
Create a new connection when prompted: Simp opens, sign in and tap Approve. Then add the Simp tools to the agent.

Generative orchestration must be on for MCP tools to be used. Each end user of the agent connects to their own Simp account.

Muse#

Muse is Meta's personal AI agent, and it takes services as connectors. A Muse user connects Simp from its listing:

In the Muse app or at muse.ai, go to Settings > Connectors.
Select Connect next to Simp and review what it asks for, then Continue.
Your browser opens Simp: sign in and tap Approve.

Then try: "Ask Simp to call the sandbox number and book a table for two on Friday at 7" (the number is on the Quickstart). The user is asked to approve the task in the Simp app.

To connect your own Simp account to Muse outside the listing, ask Muse to add a custom connector and give it the MCP URL above; Muse walks through the setup itself. Muse connects from Meta's cloud rather than from your device, which Simp's public URL allows. Meta does not review custom connectors. Muse is available in the US and Canada for now.

Other MCP clients#

Any client that speaks MCP 2026-07-28 over Streamable HTTP works:

Point it at https://voice.simpmobile.com/mcp.
If it supports OAuth discovery and Client ID Metadata Documents, it identifies itself - nothing to type.
Sign in to Simp and tap Approve when the browser opens.

Command-line tools without native remote support can bridge with npx mcp-remote https://voice.simpmobile.com/mcp. MCP Inspector connects directly with the URL and walks the same OAuth flow.

If your client cannot use a metadata document, Simp has no self-service registration (dynamic client registration was removed on 2026-10-05). Pre-registered credentials exist for an installation that genuinely needs them; we hand those out directly - get in touch through your usual Simp contact.

Zapier and OpenClaw#

Native Zapier and OpenClaw integrations are coming. Both will sit on the same platform documented here - OAuth, the tool contract, and webhooks for "a result is ready" triggers - so anything you build against the MCP endpoint today carries over. Until they ship, Zapier-style automation can already consume Simp webhooks through a catch-hook URL.