Quo

Read texts and call transcripts from a Quo business phone number and send SMS.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Quo connector does

The Quo MCP server connects a Quo business phone system — the product formerly called OpenPhone — to Claude, ChatGPT and any MCP-compatible agent. Anthropic's directory lists nine tools that read text messages, call transcripts, inboxes and contacts, send SMS from your business number, and create or update contact records. Sign-in is OAuth 2.1 with three named scopes.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Quo tools (9)

  • send-message
  • create-contact
  • update-contact
  • fetch-call-transcripts
  • fetch-messages
  • list-users
  • list-inboxes
  • list-contacts
  • get-contact

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • The one irreversible action has no scope of its own. Three real application scopes exist, and none of them names messaging. Nothing at the OAuth grant separates reading a conversation from sending a text.
  • Quo's published tool table lists five of nine. The four missing names are reads and are described in Quo's prose, so nothing dangerous is hidden — but do not size the connector from that table.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request on 2026-08-22, so no parameter-level detail for the MCP tools is published here. Parameter facts on this page come from Quo's REST OpenAPI specification for the endpoints the tools are documented to perform, which is a mapping Quo describes in prose but does not publish field by field.
  • Call transcripts need a Business or Scale plan with recording enabled per number, and only cover calls made after the upgrade. On a Starter plan fetch-call-transcripts has nothing to return.
  • Reads are capped at 100 records per request. Quo documents this for both fetch-messages and fetch-call-transcripts. Breadth requires many calls, which interacts with the API rate limit below.
  • The REST API allows 10 requests per second per key, returning HTTP 429 above that. Quo does not publish a separate rate limit for the MCP server, so whether this figure governs it is unconfirmed.
  • Sending costs pre-paid credits and fails when they run out. $0.01 per US or Canada segment, and one non-GSM character — an emoji or a curly quote — cuts the segment from 160 characters to 70, multiplying the cost of the same message.
  • The recording-consent question is unresolved. Quo documents how transcripts are produced but we found nothing addressing whether disclosing recorded calls to a third-party AI assistant is covered by the consent obtained when recording. We did not test it and treat it as unknown.
  • The RFC 9728 endpoint is an interpolating catch-all. Every path under /.well-known/oauth-protected-resource/ returns HTTP 200 with the requested path echoed into the resource field, including a path we invented. The descriptor is nonetheless genuine: the 401's www-authenticate header names the /mcp descriptor specifically, which is the only thing that arbitrates. Do not read a 200 from that prefix as confirmation that a path exists.

Frequently asked questions

Is Quo the same thing as OpenPhone?

Yes. Quo is OpenPhone renamed, and the company's own documentation says so on nearly every page, writing Quo, formerly OpenPhone throughout its resource center. The API infrastructure still carries the old name: the OpenAPI specification linked from Quo's developer docs is served from a bucket path reading openphone-public-api-v1-prod. Same product, same phone numbers, new brand.

How many tools does the Quo MCP server have?

Anthropic's directory lists nine and Quo's documentation table names five. The four Quo omits are all reads: list-users, list-inboxes, list-contacts and get-contact. Quo's own prose describes every one of those capabilities elsewhere on the same page, so the table under-lists rather than the directory over-listing. Treat nine as the number.

Can the Quo connector text my customers?

Yes, and that is its one outbound path. The send-message tool sends SMS from your Quo number to real handsets, which nothing in the product undoes. Quo's REST send endpoint accepts a to array of up to ten recipients, so a single approved call can fan out to ten people at once rather than one.

What OAuth permissions does the Quo MCP server request?

Three named scopes: read:conversations, write:contacts and read:account. They are genuine application scopes rather than identity claims, which is better than most connectors manage. But no scope mentions messaging, so the grant that lets an agent read your conversations is not separable from the grant that lets it send a text.

Does using Quo through Claude cost money?

Reading is free and sending is not. Quo states that reading messages, transcripts and contacts uses no credits, while texts sent through an AI assistant count as API messages billed from your pre-paid balance at one cent per US or Canada segment. Quo warns that API messages fail outright when that balance runs out.

Do I need a paid Quo plan for call transcripts?

Yes, Business or Scale. Quo documents call transcripts and summaries as available only on Business and Scale plans, and only for numbers where call recording is enabled. Quo also states that transcripts generate only for calls made after upgrading, so earlier calls cannot be retroactively transcribed and will return nothing.

Can the Quo connector delete a contact or a message?

No. None of the nine tools carries a delete, remove or archive verb, and no tool reaches conversation state. Quo's REST API does document deleting a contact, deleting a webhook and marking a conversation done, and none of those has a counterpart in the MCP listing. The connector's writes are limited to creating and updating contacts.

What personal data can the Quo connector read?

The verbatim contents of your business phone line. Call transcripts return speaker-separated text with each segment tagged by the participant's phone number, not a summary or a link. Contacts carry names, emails and phone numbers, and list-users returns every workspace colleague's email address and role.

Sources

More Communication connectors

  • AgentMail

    Give an AI agent its own email inbox: create inboxes, read threads and send mail to anyone.

  • Circleback

    Search meeting notes, transcripts, action items, calendar and connected email.

  • Fellow.ai

    Pull meeting transcripts, summaries, action items and participants from Fellow.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Quo to work.

Connect Quo once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio