Quo
by Quo
Read texts and call transcripts from a Quo business phone number and send SMS from an AI agent. Quo is OpenPhone renamed. Anthropic lists 9 tools; Quo documents 5. OAuth with three real 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.
Connect Quo via MCP
https://mcp.quo.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Quo Tools & Capabilities (9)
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-transcriptshas nothing to return. - Reads are capped at 100 records per request. Quo documents this for both
fetch-messagesandfetch-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 theresourcefield, including a path we invented. The descriptor is nonetheless genuine: the 401'swww-authenticateheader names the/mcpdescriptor 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
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.
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.
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.
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.
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.
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.
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.
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
- Quo MCP for custom AI agents, including the five-tool table (retrieved 2026-08-22) · retrieved 2026-08-22
- Quo MCP overview, Claude and ChatGPT (retrieved 2026-08-22) · retrieved 2026-08-22
- Quo Claude connector setup, sample prompts, filters and FAQ (retrieved 2026-08-22) · retrieved 2026-08-22
- Quo pre-paid credits and usage-based billing (retrieved 2026-08-22) · retrieved 2026-08-22
- Quo call transcripts and summaries, plan requirements (retrieved 2026-08-22) · retrieved 2026-08-22
- Quo API pricing overview, segment billing (retrieved 2026-08-22) · retrieved 2026-08-22
- Quo API rate limits (retrieved 2026-08-22) · retrieved 2026-08-22
- Quo public OpenAPI specification, send-message, users and call-transcript schemas (retrieved 2026-08-22) · retrieved 2026-08-22
- Quo documentation indexes — · (retrieved 2026-08-22) · retrieved 2026-08-22
- Live OAuth posture check, RFC 9728 metadata at
https://mcp.quo.com/.well-known/oauth-protected-resource/mcp, and authorization server metadata athttps://mcp.quo.com/.well-known/oauth-authorization-server(2026-08-22) · retrieved 2026-08-22 - Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
- Quo support — · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Communication
- Developer
- Quo
- Tools
- 9
- Domain
- mcp.quo.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.