A compatible Claude client can connect to topdoer.ai Phone through remote MCP. Once your workspace is configured, Claude can request an approved call, send a reviewed text, or retrieve a call result. You keep control of the destination, the goal, and the information the agent may share. The connection adds a phone channel to the assistant you already use.
Start with a clear request
First identify which Claude client you are setting up. Claude Desktop and Claude Code can expose different connector or MCP settings, and organizational policies may restrict them. Use the remote streamable HTTP option supported by your client. The setup dialog provides the server URL. Check your client's current instructions before adding a configuration intended for another environment.
Try a read-only request first. Ask Claude to list calls in the connected workspace so you can verify the account without contacting another person. For a real errand, state the destination, the language, and the outcome you want. Tell Claude which alternatives it can accept and what must come back to you for another decision.
Connect the client you use
For Claude Code, a remote MCP configuration can use the endpoint shown below with authentication supplied through a supported secret setting. In Claude Desktop, use the available connector flow for your plan. OAuth sign-in requires both a configured deployment and a client that supports it. An API key remains a private credential regardless of which client stores it.
Review the result
Before approving place_call or send_text, read the exact proposal. A conversational plan is not the same as a reviewed destination and message. When the action finishes, ask for the actual result using the returned call identifier. If the recipient did not answer or asked for something outside your brief, keep that uncertainty in the summary.
Keep the boundaries clear
Claude's client controls and topdoer.ai's server checks serve different roles. Keep tool approval enabled, use the required API scopes, and do not expose your credential in a shared prompt or repository. A configured number, verified phone access, account entitlement, allowed destination, consent, and fair-use limits can all affect whether the request proceeds.
Set up the connection in three steps
- Choose your AI in the Phone setup dialog. Check that the client supports the remote connection and that your workspace permits it.
- Connect the MCP endpoint with supported authentication. Use a read-only request first, then review a specific call or message before approving it.
- Review the plan at checkout. Choosing a client does not charge you, and a connection does not activate an unconfigured number or subscription.
Read the plan before you start
The first month is $9, then $19 per month, or $190 a year with two months free. Fair use applies: 200 call minutes and 300 text segments a month, one call at a time, 30 calls a day, and up to 15 minutes per call, to US, Puerto Rico and Canada numbers. Over the cap, add a $10 top-up (about 60 minutes) or wait for the next cycle. See the full fair-use list.
Keep a record of what you approved and what actually happened. If a request fails, read the error and check its state before trying again. Review the billing terms shown by Stripe, including renewal and taxes. Your workspace Billing page opens the supported customer portal for subscription changes. You can also contact our team when a plan or client requirement needs clarification.
Frequently asked questions
Do I approve the call or text?
Yes. Review the destination, goal, and information to be shared before approving an outbound action. Keep your client's approval controls enabled.
Can I use English or Spanish?
English and Spanish are supported choices. Specify the language before the action and check the result for important names, dates, and numbers.
Where do I see the price and limits?
It costs $9 for the first month, then $19 a month or $190 a year. Fair-use limits apply, and checkout shows the final terms before you pay.
Connection reference
Use the remote endpoint shown below. Store a real credential only in your client's supported private authentication setting, and consult the MCP setup documentation for the current client contract.
Transport: streamable HTTP
Server URL: https://mcp.topdoer.ai/mcp
Authentication: workspace API key, or configured OAuth sign-in
Read tools: list_calls, get_call_result
Actions requiring approval: place_call, send_text