# Simp Connect

> Simp Connect is the MCP + OAuth platform behind Simp, the mobile operator whose AI personas (simps) make and take real phone calls on a user's own Simp number. Connect Claude, ChatGPT or any MCP client to give a user's simp a task (a call, or asking, telling or chasing someone by a deadline), follow it, pass on the user's decisions and read the one result - with the user approving every task by default.

MCP endpoint: https://voice.simpmobile.com/mcp (MCP 2026-07-28, stateless Streamable HTTP; OAuth 2.0 with PKCE S256 and RFC 9207 issuer identification; clients identify with a Client ID Metadata Document, no registration; discovery at https://voice.simpmobile.com/.well-known/oauth-authorization-server).

Full corpus as one markdown document: https://voice.simpmobile.com/llms-full.txt
Generated tool reference (JSON): https://voice.simpmobile.com/platform/tool-reference.json

## Docs

- [Simp Connect](https://simpmobile.com/developers): Give your integration a way to reach people. Simp Connect is the MCP and OAuth platform that lets Claude, ChatGPT, Gemini, Copilot and any MCP client have a user's simps call businesses and ask, tell or chase people - with the user approving every task.
- [Quickstart: a five-minute sandbox call](https://simpmobile.com/developers/quickstart): Connect an MCP client to Simp, create a real end-to-end call to the Simp sandbox number, pass on a decision mid-call, and read the result - without ringing a stranger.
- [Connect guides](https://simpmobile.com/developers/clients): Step-by-step setup for Claude (claude.ai, Claude Code, Claude Desktop), ChatGPT developer mode, Gemini CLI and SDK, Microsoft Copilot Studio, and any other MCP client.
- [Authentication: OAuth 2.0, client metadata documents and scopes](https://simpmobile.com/developers/authentication): Simp is both the OAuth 2.0 authorisation server and the MCP resource server: discovery metadata, Client ID Metadata Documents instead of registration, authorization code with PKCE S256, RFC 9207 issuer identification, resource-bound tokens, four scopes, rotation and revocation.
- [Tool reference](https://simpmobile.com/developers/tools): The eight Simp Connect MCP tools - create_task, get_task, list_tasks, respond_to_decision, cancel_task, get_user_info, support_ask, support_cases - with arguments, annotations, valid and invalid examples, generated from the live schemas, plus the MCP tasks extension and decisions.
- [Deadlines and timing](https://simpmobile.com/developers/timing): How long approval lasts, what respond_by means for get_answer, send_update and follow_up, when Simp contacts people (the recipient window), how many times it calls, and what happens at the deadline.
- [Webhooks: signed task events](https://simpmobile.com/developers/webhooks): Receive task.approval_needed, task.status_changed, task.input_needed, task.participant_answered, task.result_ready, task.completed and task.failed as signed HTTPS POSTs: registration, ownership handshake, HMAC signature verification in Node and Python, at-least-once delivery, retries, dead-lettering and the event catalogue.
- [A2A: Simp as an Agent2Agent server](https://simpmobile.com/developers/a2a): Talk to Simp over the A2A v1.0 protocol: the signed agent card, the JSON-RPC endpoint, the three skills (ask a Simp user, tell a Simp user, have Simp act for a signed-in user), the task states, push notifications, errors and limits.
- [Permission modes: ask every time, notify only, rights-based](https://simpmobile.com/developers/permissions): How much autonomy a connected app has: the default approve-every-task mode, notify-only auto-dispatch with a cancel window, rights-based auto-dispatch that fails closed, the sharing envelope, per-connection daily caps and frozen connections.
- [Errors catalogue](https://simpmobile.com/developers/errors): Every Simp Connect tool error code with its teaching message and what the agent should do next, generated from the live catalogue.
- [Changelog](https://simpmobile.com/developers/changelog): What changed on the Simp Connect platform, newest first, including the 2026-10-05 replacement of the MCP server on the 2026-07-28 specification.
- [Troubleshooting](https://simpmobile.com/developers/troubleshooting): Fixes for the common snags: stale tool schemas and old clients, OAuth loops, clients asking for credentials, tasks that never start, stale decisions, webhook handshakes and rate limits.

## Optional

- [Authorisation server metadata](https://voice.simpmobile.com/.well-known/oauth-authorization-server): RFC 8414 discovery document.
- [Protected resource metadata](https://voice.simpmobile.com/.well-known/oauth-protected-resource/mcp): RFC 9728 document for the MCP endpoint.