A supported Codex MCP client can use topdoer.ai Phone to request a call or text as part of a reviewed task. The phone tools are remote and authenticate to your workspace. This can help a coding agent complete a simple communication step, while keeping the recipient, purpose, and approval visible to the person directing the work.
Start with a clear request
Add the remote server using the MCP settings supported by your Codex client. Keep the URL separate from the private authentication value. Put API credentials in the client's supported secret or environment mechanism, not a tracked project file. If the client runs in a cloud environment, confirm that it can reach the service through its approved network policy.
Give the agent a communication brief that is independent of its code changes. For example, ask it to call a supplier about opening hours, not to negotiate an undefined purchase while editing an application. Include the destination, supported language, and a stopping point. Human approval should happen after those details are visible and before an external action begins.
Connect the client you use
A cloud agent may have an allowlist for network destinations. Permit only the endpoints required by your intended workflow and keep TLS verification enabled. Do not work around a denied destination by routing a key through an unrelated service. Read the MCP setup documentation for the current supported authentication method and client-specific configuration.
Review the result
Begin with list_calls to check the connection. For an approved call, keep the returned identifier and read get_call_result when it is available. Do not convert an accepted request into a claim that the call succeeded. If the action is interrupted, check the existing request before submitting another one. A new conversation or agent run should not erase that responsibility.
Keep the boundaries clear
The fact that a tool is available in a coding environment does not authorize unrestricted outreach. Call and text tools are marked destructive, and your application should preserve approval. The workspace separately enforces authentication, phone verification, entitlement, destination restrictions, consent rules, and fair-use caps. Use a business plan when the intended operation goes beyond the personal Phone plan.
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