Check the connector options
Open Claude Desktop's connector settings and check whether your plan and client version support a custom remote MCP connection. Use https://mcp.topdoer.ai/mcp as the server URL.
If the client requires OAuth, the topdoer.ai deployment needs a real issuer and sign-in flow configured first. Do not assume that a Bearer-only endpoint will work in an OAuth-only connector. If custom headers are supported, use a securely stored organization API key.
When a native connector is not available, review an approved local bridge with your administrator. Do not install an unreviewed proxy simply to pass a secret through a public service.
Approve the intended action
Start with a number you control. State the exact destination and task, then approve the call or message when the client asks. Call and text tools are destructive operations. A successful connection does not waive approval, phone verification, credits, recipient eligibility, or fair-use limits.
Verify the result
Use the result tool after the provider finishes. Distinguish a queued request from a completed conversation and distinguish a conversation from the real-world outcome you wanted. If the call did not complete or the result is missing, report that accurately.
Troubleshooting
Check the endpoint, authentication method, organization key status, provider configuration, and workspace readiness. A client that requires OAuth needs a configured issuer. Do not disable authentication, remove approval, or keep retrying a rejected outbound request with new identifiers.
Read the MCP tools reference for inputs and the API-key guide for key handling.