Other MCP clients

SimpleVox runs a remote MCP server. Assistants and agents that support remote MCP servers with OAuth sign-in can connect to it, not just Claude and ChatGPT. Each person signs in with their own SimpleVox account and chooses what the connection can do.

Connection details

Setting	Value
Server URL	https://my.simplevox.app/mcp, with no slash at the end
Transport	Streamable HTTP. Requests are JSON-RPC, sent with POST to the server URL.
Authentication	OAuth 2.1 authorization code with PKCE (S256). Public client, no client secret.
Client registration	Dynamic client registration at https://my.simplevox.app/oauth/register. Redirect addresses use HTTPS, or http://127.0.0.1, http://[::1] or http://localhost for apps on your computer.
Scope and resource	mcp:use, with resource https://my.simplevox.app/mcp
Permissions	Chosen by the person on the consent screen. See MCP permissions for the capability IDs and tool visibility.
Tools	See the MCP tools reference for the available tools and their limits.
Server card	https://my.simplevox.app/mcp/server-card, listed by https://simplevox.net/.well-known/ai-catalog.json and https://my.simplevox.app/.well-known/ai-catalog.json. https://simplevox.net/.well-known/api-catalog (RFC 9727) lists the REST API and the MCP server.
Rate limit	120 requests a minute

There are no API keys to paste in. SimpleVox personal API tokens work only with the REST API, not with MCP.

Sign-in addresses

Web clients finish sign-in at an HTTPS address. Command-line and desktop clients, such as Claude Code, can finish it at an address on your own computer: http://127.0.0.1, http://[::1] or http://localhost, on whatever port the client opens. The consent screen labels these An app on this computer. App links such as myapp:// aren’t supported, and SimpleVox doesn’t read client ID metadata documents, so clients need to support dynamic client registration.

Add SimpleVox to your client

1. In your client, add a new remote MCP server. It may be called a connector, an integration or a custom server.

2. Enter the server URL https://my.simplevox.app/mcp. If you’re asked for a transport, choose Streamable HTTP or HTTP.

3. If you’re asked about authentication, choose OAuth. Leave client ID and secret empty: your client registers itself with SimpleVox.

4. Connect. Your client opens SimpleVox in a browser.

5. Sign in. If you haven’t verified your email address or set up a workspace, SimpleVox takes you through that first.

6. Check the consent screen: the workspace and email shown are yours, and the Redirect URI belongs to the client you’re connecting.

7. Choose what it can do. Tick any permissions you want under Also allow it to, and choose All numbers you can access or Only the numbers I choose. Then choose Authorize. See Choose what each connection can do.

8. Back in your client, list the tools. You should see tools such as get_my_account, search_contacts and list_history. Tools that need a permission you didn’t grant don’t appear.

Note

Menu names and setup screens vary by client and change between versions. If your client can’t complete sign-in, email support@simplevox.net with the client’s name and version.

Configure and check

Client config

Many clients list MCP servers in a JSON file. The exact format depends on the client, so check its documentation. Clients that support remote servers usually need only the URL:

{
  "mcpServers": {
    "simplevox": {
      "url": "https://my.simplevox.app/mcp"
    }
  }
}

Check discovery

Without a token, the server answers 401 and points to its metadata:

curl -si -X POST https://my.simplevox.app/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  --data '{"jsonrpc":"2.0","id":1,"method":"ping"}'

curl -s https://my.simplevox.app/.well-known/oauth-protected-resource/mcp
curl -s https://my.simplevox.app/.well-known/oauth-authorization-server

The first response includes WWW-Authenticate: Bearer resource_metadata="https://my.simplevox.app/.well-known/oauth-protected-resource/mcp", scope="mcp:use".

How sign-in works

If you’re building or debugging a client, this is the flow SimpleVox expects. It follows the MCP authorization specification.

1. The client calls https://my.simplevox.app/mcp without a token. SimpleVox responds with 401 and a WWW-Authenticate header that points to the protected resource metadata.

2. The client reads https://my.simplevox.app/.well-known/oauth-protected-resource/mcp. It names the resource, the authorization server https://my.simplevox.app and the mcp:use scope.

3. The client reads https://my.simplevox.app/.well-known/oauth-authorization-server for the authorization, token and registration endpoints. It advertises the authorization_code and refresh_token grants, S256 and token endpoint authentication none.

4. The client registers at /oauth/register with a client_name and up to 5 HTTPS redirect_uris. SimpleVox creates a public client and returns its client_id. Registration is limited to 10 requests a minute.

5. The client sends the person to /oauth/authorize with response_type=code, its client_id, the exact redirect_uri, a random state, scope=mcp:use, resource=https://my.simplevox.app/mcp and a PKCE S256 challenge. The person signs in, chooses permissions and numbers, and approves.

6. The client exchanges the code at /oauth/token with the same redirect_uri and resource and its code_verifier, then calls the MCP server with the access token as a bearer token.

7. Access tokens last 15 minutes. Refresh with the same resource. Refresh tokens rotate: each one works once and lasts 30 days, so store the new one every time.

For request examples and error handling, see Authentication.

What the client can do

Use the shared guides when configuring or building a client:

• Permissions: tool visibility and the capabilities each connection needs.
• Pagination: page sizes, cursors and how to report partial results.
• Tools that act: confirmation, marking conversations and retries.
• Assisted calls: choosing a device, following a call and ending it.

For the user-facing call flow and consent screen, see the AI tools overview. For account setup, missing numbers, permissions, texting or calling problems, see AI tools troubleshooting.