Simp Connect in Muse

How Meta's Muse connects to Simp Connect: sign-in with a Client ID Metadata Document, scopes, the eight tools with their read and write labels, errors, rate limits, the approval flow, read-only access and AI disclosure.

Muse is Meta's personal AI agent. It reaches Simp as a remote MCP connector at https://voice.simpmobile.com/mcp, and Simp treats it as a first-class AI app, like ChatGPT, Claude and Perplexity: it is named Muse everywhere a user sees it, it gets the standard rate limits, and Simp answers it in plain sentences rather than with a card. Muse is available in the US and Canada for now.

Connecting#

Muse registers itself with a Client ID Metadata Document (CIMD): its client_id is an https URL, and the JSON served there is its registration. There is no client secret and nothing to register with Simp. Muse's document is https://platform.muse.ai/oauth/client-metadata.json.

  1. Step 1Muse reads Simp's discovery documents (see Authentication) and starts an OAuth 2.0 authorization code flow with PKCE (S256) and the resource parameter set to https://voice.simpmobile.com/mcp.
  2. Step 2Simp fetches the metadata document, checks it (the client_id must equal the URL, token_endpoint_auth_method none, https redirect URIs) and shows Simp's sign-in, headed "Connect Muse to your Simp": Open Simp on a phone, a QR code on a computer.
  3. Step 3The user approves in the Simp app, where the request reads "Muse wants to connect to your Simp" and lists what Muse is asking for. Muse exchanges the code at the token endpoint as a public client.

Then try: "Ask Simp to call Bella Napoli and book a table for two on Friday at 7."

Simp names a metadata-document client only by URLs it knows exactly. A document on any other URL, including another muse.ai one, still connects, is named by its host and gets the stricter limits until Simp adds that exact URL. Details: Client ID Metadata Documents.

Scopes#

Muse asks for all four scopes, and the eight tools need no other: tasks:write, tasks:read, input:respond, account:read.

ScopeTools
tasks:writecreate_task, cancel_task
tasks:readget_task, list_tasks
input:respondrespond_to_decision
account:readget_user_info, support_ask, support_cases

Access tokens last 60 minutes; refresh tokens last 30 days and rotate on every use.

Tools and their labels#

Every tool carries Simp's label in _meta["simp/access"] and in the tool reference. The label says what the tool may do; readOnlyHint agrees with it.

ToolLabelWhat it does
get_taskreadOne task's status, outcome and next step
list_tasksreadThe user's recent tasks
get_user_inforeadThe user's simps, Simp numbers and first name
support_casesreadThe user's open and recent help requests
cancel_taskwriteCancels a task, ending a live call
support_askwriteSends the user's question to Simp support
create_tasksensitive writeSets up a real phone call
respond_to_decisionsensitive writePasses the user's answer into a live call

Full arguments, examples and schemas are on Tools.

The default simp and number#

Every task uses the user's default simp and default Simp number. Muse never asks which simp or number to use and never offers a choice: it goes ahead. Only when the user names a simp, or asks for one of their own numbers ("from my US number"), does Muse pass persona or from_number, exactly as get_user_info lists them.

The approval flow#

A new connection asks every time: create_task answers status: "awaiting_approval" and the user approves or declines the call in the Simp app. An approval stays open for one hour from the request, scheduled or not; after that the task closes and nobody is contacted (Approval: one hour). The user can give the connection lighter rules in the Simp app; see Permissions.

While a task runs, poll get_task. Simp answers Muse in plain sentences: the status, the outcome in one sentence, what happens next.

Read-only access#

A connection can be Read only, a setting on the connection rather than a scope. The approval in the Simp app does not offer that choice today, so a connection made there has full access. A read-only connection:

  • tools/list returns only the four read tools: get_task, list_tasks, get_user_info, support_cases.
  • Every other tool, support_ask included, and tasks/update and tasks/cancel answer read_only_access. Tell the user they can disconnect Simp in the Simp app (Profile, then AI apps, then the app, then Disconnect) and connect it again with full access.

Errors#

Errors any tool can return are on Errors. The ones a Muse integration should expect:

CodeMeaningWhat to do
read_only_accessThe user chose read onlySay so; offer the reconnect above
app_not_availableSimp has not opened Muse to this account yetSay Muse isn't available for Simp yet
app_pausedSimp has paused Muse for nowThe connection and settings are kept; try later
app_daily_cap_reachedToday's limit for new tasks from Muse is reachedTry again after 00:00 UTC
ai_apps_daily_cap_reachedToday's limit for new tasks from all AI apps is reachedTry again after 00:00 UTC
ai_apps_cap_unavailableSimp cannot check today's limit right nowTry again in a few minutes

A missing or expired token is an HTTP 401 with a WWW-Authenticate challenge; a token without a tool's scope is a 403 naming the scope.

Rate limits#

Muse is on the standard tier: 600 tool calls and 200 new tasks a minute across all Muse users, and 60 tool calls and 20 new tasks a minute for each user. A hit is a rate_limited tool error carrying retry_after_seconds: back off for that long. Each connection also has its own daily task cap, 50 on the default mode. Simp also caps new tasks per AI app and across all AI apps each day. Details: Rate limits and Daily caps.

AI disclosure#

The simp always says it is an AI when asked, on every call. Simp follows the rules of each country it operates in (the UK, the US and Canada).