Quote first
Validate the route and show the estimated rate before any billable action.
All integrations
LocalCall for Claude
Give Claude a managed phone line.
Connect the same LocalCall endpoint from Claude and authorize only the account and tools you intend to use.
Setup
Connect LocalCall to Claude
The connection uses OAuth with PKCE. Your assistant receives scoped access to one LocalCall team, never your password or telephony-provider credentials.
- 1
For Pro or Max, open Customize → Connectors, select +, then Add custom connector.
- 2
For Team or Enterprise, an Owner first adds a Custom → Web connector in Organization settings → Connectors.
- 3
Paste the LocalCall MCP endpoint and add the connector.
- 4
Select Connect, complete OAuth, and choose your personal account or a team.
Try it
Useful prompts for Claude
“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