Cursor can use remote MCP tools when its client configuration supports the connection. topdoer.ai Phone adds authenticated call and text actions to that tool set. A developer can describe an ordinary errand, review the proposed action, and keep its result close to the work. The connection should remain bounded by the person's instructions and approval.
Start with a clear request
Open Cursor's MCP settings and use its supported remote server configuration. Confirm that your version and workspace policy allow streamable HTTP connections. Add the endpoint from the setup panel and supply authentication through a supported private setting. Avoid placing a real API key in a shared mcp.json file or any other file that may be committed.
Separate an external communication from background development work. The agent should show the number it will contact, the message or goal, and the language before asking for approval. If it proposes to ask a provider for a quote, tell it which facts are certain and which questions are still open. Do not let a vague coding task become an open-ended phone campaign.
Connect the client you use
If Cursor's connector behavior changes after an update, inspect its current settings and test the read-only tools again. Remove unused keys and rotate exposed ones. The setup dialog provides a starting point, while the developer documentation explains the tool contract. Keep approval enabled for place_call and send_text even when other editor tools can run automatically.
Review the result
Check the workspace with list_calls before trying an outbound request. Once a call is approved, preserve its identifier and retrieve the result. Keep no answer, failure, and completed conversations distinct. Read dates, names, amounts, and commitments carefully. When the task needs another decision, the agent should return to you rather than invent permission to continue.
Keep the boundaries clear
MCP tool approval in the client is one control. The service also requires the correct account scope and applies phone verification, billing entitlement, consent rules, fair-use caps, and destination coverage. If you run the same client across several workspaces, verify which account the connector uses. Do not share a credential merely because two projects use the same editor.
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