Send and read OpenPhone messages, calls, contacts and phone numbers. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"openphone": {
"url": "https://openphone.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"openphone": {
"type": "http",
"url": "https://openphone.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your OpenPhone API key.
Create one in OpenPhone → Settings → API. Your token is used only to call the API on your behalf and to derive a private account id; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your OpenPhone API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the OpenPhone connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
openphone_list_phone_numbers | read | List phone numbers List the OpenPhone numbers in the workspace (id, number, name, formatted number, assigned users, restrictions). Usually the first call — most other tools need a phoneNumberId. OpenPhone REST: GET /phone-numbers. |
openphone_list_users | read | List users List workspace users (id, email, name, role). Use to find a userId for scoping other calls. OpenPhone REST: GET /users. |
openphone_list_contacts | read | List contacts List contacts in the workspace, optionally filtered by external ids or sources. Returns each contact's default fields (name, company, emails, phone numbers) and custom fields. OpenPhone REST: GET /contacts. |
openphone_get_contact | read | Get a contact Get a single contact by its id, including default fields (name, company, role, emails, phone numbers) and custom fields. OpenPhone REST: GET /contacts/{id}. |
openphone_get_contact_custom_fields | read | Get contact custom fields List the workspace's contact custom-field definitions (name, key, type). Use the returned keys when creating contacts with custom fields. OpenPhone REST: GET /contact-custom-fields. |
openphone_list_conversations | read | List conversations List conversations (threads), most-recent activity first, optionally filtered by phone number(s), user, and created/updated date ranges. Each conversation has participants, assignee, and last-activity metadata. OpenPhone REST: GET /conversations. |
openphone_list_messages | read | List messages List messages in a conversation between one of your OpenPhone numbers and one or more participants. Returns text, direction, status and timestamps. OpenPhone REST: GET /messages. |
openphone_get_message | read | Get a message Get a single message by its id (starts with 'AC'). OpenPhone REST: GET /messages/{id}. |
openphone_send_message | write | Send a text message Send an SMS/text message from one of your OpenPhone numbers to up to 10 recipients. WRITE ACTION — this actually sends a real text message (which may incur carrier cost and requires approved A2P 10DLC registration). OpenPhone REST: POST /messages. |
openphone_list_calls | read | List calls List calls between one of your OpenPhone numbers and a participant, newest first, optionally filtered by user and created date range. Returns direction, status, duration and timestamps. OpenPhone REST: GET /calls. |
openphone_get_call | read | Get a call Get a single call by its id (starts with 'AC') — direction, status, duration, participants and timestamps. OpenPhone REST: GET /calls/{id}. |
openphone_get_call_summary | read | Get a call summary Get the AI-generated summary and next steps for a call by its id. Availability depends on your plan and whether the call was summarized. OpenPhone REST: GET /call-summaries/{callId}. |
openphone_get_call_transcript | read | Get a call transcript Get the transcription for a call by its id — dialogue segments with speaker, text and timestamps, plus overall status and duration. OpenPhone REST: GET /call-transcripts/{id}. |
openphone_get_call_recordings | read | Get call recordings Get the recordings for a call by its id — each with a URL, duration, start time and status. OpenPhone REST: GET /call-recordings/{callId}. |
openphone_list_webhooks | read | List webhooks List all webhooks configured in the workspace (id, url, events, status). Read-only inventory — this tool does not create or delete webhooks. OpenPhone REST: GET /webhooks. |
openphone_create_contact | write | Create a contact Create a new contact in the workspace. WRITE ACTION — this adds a persistent contact record. Emails and phoneNumbers are passed as simple string arrays and stored under default field labels. OpenPhone REST: POST /contacts. |
openphone_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
openphone_request_feature | Request a missing feature Tell usefulapi that the user needs something the OpenPhone tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
openphone_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED OpenPhone tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
openphone_cancel_subscription | Cancel the Pro subscription Cancel the caller's OpenPhone Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run openphone_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Pro | $9/mo · $90/yr | Unlimited |
Pro covers this OpenPhone server only. Subscribe with openphone_upgrade (it returns a Stripe Checkout link). Cancel any time with openphone_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running openphone_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by OpenPhone. The server calls the OpenPhone API with your own OpenPhone access, so it sees only the data that your account can see.
The login page asks for your OpenPhone API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your OpenPhone API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the OpenPhone API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in OpenPhone.
Yes, if you approve it. 2 of the 16 OpenPhone tools can create or change data. The other 14 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this OpenPhone server only. Run openphone_usage_status to see how many calls you used.
Ask the AI to run openphone_upgrade: it returns a Stripe Checkout link. To cancel, run openphone_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with openphone_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.