Add the server configuration
Use Cursor's MCP settings or its supported project configuration to add the remote HTTP endpoint. Keep the actual key in secure environment storage and use the client's supported secret interpolation.
{
"mcpServers": {
"topdoer-ai": {
"url": "https://mcp.topdoer.ai/mcp",
"headers": {
"Authorization": "Bearer ${env:TOPDOER_API_KEY}"
}
}
}
}
Confirm interpolation support in your client version. Never commit a real key into a project file. Check the MCP status and review the tools before requesting an action.
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.