The topdoer.ai Phone MCP server gives compatible AI clients a standard way to request calls, send texts, and retrieve call results. Its remote endpoint uses streamable HTTP. Your client authenticates to your workspace, discovers the available tools, and asks you to approve actions that communicate with another person.
Start with a clear request
Check your client's remote MCP support before adding a connector. Some clients restrict custom servers by plan, platform, or administrator policy. Use the connection settings recommended by that client and enter the server URL shown in the setup dialog. A local process configuration is different from a hosted remote connector, so follow the correct instructions for your environment.
Start with a read-only tool such as list_calls. This checks that the connection reaches the intended workspace without contacting a recipient. Next, inspect the available tool descriptions and required fields. place_call needs a destination, a clear goal, and a supported language. send_text needs a destination and a message you have reviewed. Keep each proposed action visible before approval.
Connect the client you use
The tool set is place_call, send_text, get_call_result, and list_calls. OAuth sign-in is available only when configured for the deployment and supported by the client. Otherwise use a workspace API key with the required scopes. Do not paste a key into a public chat, a code example, or a committed configuration file.
Review the result
Calls can finish after the initial tool response. Keep the returned call identifier and use get_call_result to check the outcome. Do not treat a queued or started state as a successful conversation. A result should distinguish an answer, no answer, a failure, and any information the recipient provided. Your application should preserve that distinction too.
Keep the boundaries clear
Call and text tools are marked as destructive actions because they affect people outside the conversation. Client approval settings and server-side checks work together. Keep approval enabled, store API keys using your client's supported secret mechanism, and rotate a key if it is exposed. Account entitlements, fair-use limits, consent rules, and destination restrictions remain server-side requirements.
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