Quote first
Validate the route and show the estimated rate before any billable action.
All integrations
LocalCall for Codex
Add LocalCall to Codex.
Register the remote MCP endpoint and complete LocalCall OAuth from the Codex app, CLI, or IDE extension.
Setup
Connect LocalCall to Codex
The connection uses OAuth with PKCE. Your assistant receives scoped access to one LocalCall team, never your password or telephony-provider credentials.
- 1
Run the two verified Codex CLI commands below.
- 2
Complete LocalCall OAuth in the browser and choose your personal account or a team.
- 3
Restart Codex if needed, then open /mcp to confirm LocalCall is connected.
- 4
Use the read-only verification prompt before approving any call action.
Try it
Useful prompts for Codex
“Show the LocalCall accounts available to me. Do not place a call.”
Call lifecycle
Quote, approve, call, verify.
Confirm scope
Name the recipient, objective, consent basis, team, and playbook.
Start once
A stable replay key keeps client retries from creating duplicate calls.
Return evidence
Read completion status, structured result, duration, and final charge.
Tools
What the connector can do
- Check international number format and LocalCall route support
- Quote a supported direct, translated, or managed call
- Read approved teams, playbooks, and available wallet balance
- Start one confirmed, consented managed call
- Read call status, outcome, duration, and final charge
- End an active managed call after confirmation
Safety
What the connector cannot do
- One recipient per tool call; no lists or batch outreach
- A documented recipient-consent basis is required
- Destination, route, sanctions, premium-range, and balance checks run before dialing
- Billable and destructive tools are marked for explicit approval
- Stable replay keys prevent duplicate calls when a client retries
- Managed assistant calls identify themselves and are not recorded through these integrations