DEVELOPER DOCS

MCP overview

Connect an assistant to approved phone and messaging tools.

One connection for a defined set of tools

The hosted MCP endpoint is https://mcp.topdoer.ai/mcp. The application handler is /api/mcp. It uses streamable HTTP and exposes a small tool set: place a call, send a text, retrieve a call result, and list calls.

A working remote endpoint requires the host and deployment routing to be configured. A URL in this guide does not mean the current preview has a production hostname attached.

Authentication

Use an organization API key through Bearer authentication when your client supports a secure custom-header connection. OAuth is available only when a real issuer and client flow have been configured. The application does not advertise a working sign-in flow merely by returning an invented metadata document.

Human approval comes first

Call and text tools are marked as destructive. The client must ask for approval of the recipient and the intended content before requesting the action. The server also requires an explicit approval flag and enforces workspace prerequisites and limits.

Read results carefully

A call can be queued, in progress, completed, failed, or otherwise unresolved. Use the result tool to retrieve the actual recorded outcome. Do not tell a user a reservation changed or a quote was obtained merely because the call request was accepted.

Choose the client guide

Client authentication options vary. Use the setup the client actually supports instead of removing authentication to make a connector appear to work.

Never miss a call again.

Put your calls, texts, and next steps in one workspace.