Add the HTTP server
Store the organization key in the environment used by Codex, then add the remote endpoint. The client reads the named variable rather than placing the key directly in the command.
codex mcp add topdoer-ai \
--url https://mcp.topdoer.ai/mcp \
--bearer-token-env-var TOPDOER_API_KEY
Review the MCP server status and the tool list in your client. Do not expose the environment value in command output or ask the assistant to print it.
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.