OpenAI Codex setup guide
Connect OpenAI Codex to ClawCall with remote MCP
Add ClawCall with codex mcp add, then sign in with codex mcp login clawcall. Codex can then place a call when a task needs one.
https://api.clawcall.dev/mcp- Setup surface
- CLI or IDE MCP server
- Transport
- Streamable HTTP
- Authentication
- OAuth with DCR/CIMD
Before you start
- A current OpenAI Codex CLI or IDE extension.
- A ClawCall account.
- A real US destination in +1 E.164 format for any call you choose to place.
- A clear, user-directed task with destination and decision boundaries specified before a real call.
Connect OpenAI Codex to ClawCall
Update Codex
Use a current Codex CLI or IDE extension that supports Streamable HTTP and OAuth MCP servers.
Add ClawCall
Add the remote server under the name clawcall.
codex mcp add clawcall --url https://api.clawcall.dev/mcpStart OAuth
Run the login command. Codex supports DCR/CIMD; ClawCall’s discovery metadata handles registration without a copied API key.
codex mcp login clawcallApprove the scopes
Sign in to ClawCall and review
calls:readandcalls:write. Return to Codex after the browser callback completes.Verify discovery
Run
codex mcp listand open/mcpin the TUI. Confirm clawcall is enabled and eleven tools are available.Always allow ClawCall
Set the ClawCall server and tools to Always allow in the active approval policy.
OAuth scopes and host permissions
OpenAI Codex signs in with OAuth and asks for two scopes: calls:read to read account and call state, and calls:write to place or hang up calls and change call settings. It gets revocable tokens, never your ClawCall API key.
Recommended: Always allow ClawCall tools
Use Codex’s per-server or per-tool approval controls to Always allow all eleven ClawCall tools, so it can run the complete calling workflow. Keep your OAuth credentials in the local credential store, not the repository.
Always allow only skips the repeated approval prompts. It does not widen the two OAuth scopes, override project policy, or allow bulk or automated calling.
Verify read-only, then place one controlled call
Check account state first. Only after that succeeds, place the first real call to a number you control.
Check my ClawCall plan and remaining trial allowance. Do not place a call.
Using ClawCall, call my phone at +1XXXXXXXXXX. Say this is a connector test, ask me to confirm I can hear the AI, then end the call. Show me any transcript evidence actually captured afterward.
Tools and troubleshooting
ClawCall gives OpenAI Codex 11 tools: read tools for the calling guide, your plan, settings, calls, transcripts, and recordings, and write tools that place, wait on, or hang up a call and update settings. A call’s outcome describes the phone network, so read the transcript evidence actually captured before treating the task as done. The remote MCP reference lists every tool and scope.
If no tools appear, check that the server URL ends in /mcp. If you see 401 or a sign-in prompt, reconnect and approve ClawCall again instead of pasting an API key. For anything else, see troubleshooting in the docs.
Disconnect and revoke access
- Disconnect or remove ClawCall in OpenAI Codex.
- Open ClawCall Dashboard → Settings → Connected AI assistants → Disconnect to revoke its OAuth tokens.
FAQ
- Do I need to choose ClawCall before every request?
- No. Once the connection is enabled, the agent can pick ClawCall automatically when an ordinary request needs a phone call. Naming the tool is optional and mainly useful for troubleshooting.
- What does it cost?
- The ClawCall trial includes 30 calls and 30 minutes, whichever lasts later. After that, a paid plan covers ongoing calls. The host itself may need its own plan for plugins or connectors.
- Does a successful network outcome prove the task succeeded?
- No. A network outcome describes the call path. Read the transcript evidence actually captured before claiming a reservation, cancellation, price, or other real-world task was completed.
- How do I revoke access?
- Remove or disconnect ClawCall in the host, then open ClawCall Dashboard → Settings → Connected AI assistants → Disconnect to revoke that connection’s tokens.
- How long does ClawCall keep transcripts and recordings?
- ClawCall deletes transcripts 7 days after a call ends and recordings 10 minutes after a call ends. Recording URLs are temporary and cannot be renewed after they expire.
Sources
Setup steps come from OpenAI Codex’s own documentation and ClawCall’s product documentation, checked on the dates below.
- OpenAI: Model Context Protocol in Codex
- OpenAI: The next phase of Education for Countries
- ClawCall: Hosted MCP for AI agents
- ClawCall security
Related pages
Give OpenAI Codex a phone line
Create a ClawCall account, add the endpoint, and start with the read-only check. The trial includes 30 calls and 30 minutes, whichever lasts later.