ChatGPT can use a remote phone connection when your plan and workspace support the required MCP connector. topdoer.ai Phone supplies the number, authenticated tools, and call record. You supply a specific request and approve the communication. Confirm your connector options before subscribing for a workflow that depends on a particular ChatGPT environment.
Start with a clear request
Open the connector settings available in your ChatGPT account and check whether a custom remote MCP server can be added. Your administrator may need to permit it. Enter the endpoint from the Phone setup dialog and use the supported authentication flow. Do not assume that every consumer, business, mobile, or browser configuration exposes the same controls.
After connecting, test a read-only request such as list_calls. This helps confirm that ChatGPT is reaching the intended workspace. Then write a small approved task: call one business, ask one set of questions, and report the answer. Specify what the agent may confirm on your behalf and what should wait for your decision.
Connect the client you use
Keep the connector's approval controls on for tools that communicate with other people. Do not put an API key into an ordinary ChatGPT message. Use the authentication or secret field designed for the connector. If you change accounts or workspace policy, verify the connection again with a read-only request before starting another outbound task.
Review the result
Read the proposed action before it is sent. Check the destination number, the language, the goal, and any information that will be disclosed. Afterward, ask for the actual call result rather than a prediction of how the call should have gone. A no-answer state, a callback request, and a confirmed appointment should remain different outcomes.
Keep the boundaries clear
Connector support is a client capability, not a promise that the service can bypass account or plan restrictions. Phone verification, credentials, consent, entitlement, fair-use limits, and allowed countries are checked by the workspace. If the connector cannot be enabled in your account, contact the team about another supported client or the authenticated API before paying for that intended use.
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