Configure the server
Use VS Code's MCP settings and a password-style input for the API key. The exact location can depend on whether you choose user or workspace configuration.
{
"servers": {
"topdoer-ai": {
"type": "http",
"url": "https://mcp.topdoer.ai/mcp",
"headers": { "Authorization": "Bearer ${input:topdoer-key}" }
}
},
"inputs": [
{ "type": "promptString", "id": "topdoer-key", "description": "topdoer.ai API key", "password": true }
]
}
Review the configuration in your current VS Code release and keep secrets out of committed files. Start the server connection and inspect the tool list before asking for a call.
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.