Quo MCP Server

Official MCP server for Quo (formerly OpenPhone), connects AI assistants to your business phone for SMS, calls, contacts, and transcripts.

Communication by Quo (formerly OpenPhone) OAuth2 active

Connect (Remote Server) Docs

Overview

Quo is a cloud-based business phone system (the rebrand of OpenPhone) for startups and SMBs. Its official MCP server lets AI assistants like Claude and ChatGPT interact directly with your Quo workspace, reading conversation history, pulling call transcripts, sending SMS, and managing contacts through natural language. Quo is listed as the first business phone system in Anthropic's Claude Connectors Directory.

The server is provider-hosted at https://mcp.quo.com/sse and uses OAuth-based authentication, so there is no code to clone or self-host. Once connected, the AI assistant can act on your behalf within the permissions of your Quo account: querying message history across inboxes, summarizing call activity, sending texts to individuals or broadcasting to groups, and creating or updating contact records.

Notable capabilities include analyzing customer conversation trends and objections across hundreds of calls, sending coordinated bulk updates with conversation context, and retrieving time-stamped call transcripts (where transcription is enabled on the Quo number). Messaging actions require user approval before execution, and the integration respects the role-level permissions on your Quo account.

Tools

Tool	Description
`list_messages`	Retrieve message history across inboxes, filterable by contact or date.
`send_message`	Send an SMS from a connected Quo number to an individual or group. Requires user approval.
`list_calls`	Access call history for a Quo number or contact.
`get_call_transcript`	Retrieve the transcript for a specific call (where transcription was enabled).
`search_contacts`	Search the Quo contact list by name, company, or phone number.
`get_contact`	Look up a single contact's details.
`create_contact`	Add a new contact record to Quo.
`update_contact`	Update an existing contact's fields.

Setup Guide

Prerequisites

Active Quo account (Business plan or higher recommended for call summaries/transcripts)
Claude Pro/Team or ChatGPT Plus/Pro subscription
Pre-paid credits in Quo if you want the assistant to send SMS
Transcription enabled on the Quo number to retrieve call transcripts

Claude setup (recommended)

The fastest path is the official Claude Connectors Directory entry:

Open https://claude.ai/directory/connectors/quo
Click Connect and complete the OAuth flow with your Quo login
No JSON configuration required

To add it manually in Claude Desktop:

Settings → Connectors / Integrations → Add custom integration
Name: Quo
URL: https://mcp.quo.com/sse
Authenticate when prompted

ChatGPT setup

ChatGPT Settings → Connectors (requires Plus/Pro)
Enable Developer mode
Create a new connector named Quo pointing at https://mcp.quo.com/sse
Complete OAuth authentication

Generic MCP client config

For MCP clients that accept a remote SSE server URL:

{
  "mcpServers": {
    "quo": {
      "url": "https://mcp.quo.com/sse"
    }
  }
}

Note: this integration is not covered under Quo's Business Associate Agreement, so it should not be used for PHI or other regulated data without review.

Use Cases

Pull and summarize the last 30 days of customer texts to surface recurring objections or feature requests before a sales QBR.
Send a coordinated update text to a segment of customers (e.g., everyone you spoke to about a delayed shipment) without leaving your AI assistant.
Retrieve and skim time-stamped transcripts of recent sales calls to draft follow-up emails grounded in what was actually said.
Bulk-clean the Quo contact book by enriching records with company and role information detected from recent conversations.
Triage a busy shared inbox: ask the assistant to list unread threads and propose drafted replies per contact.

Example Prompts

"Summarize all messages with Acme Corp from the last two weeks and tell me the top concerns."
"Send a text from my main Quo number to the five customers I spoke with yesterday letting them know shipping is delayed."
"Pull the transcript of my call with Jane Doe this morning and draft a follow-up email."
"Find the contact for +14155550123 and update their company to Acme."
"Which customers raised pricing objections in calls this month?"

Pros

Official, provider-hosted server with one-click setup through the Claude Connectors Directory.
Covers the full surface a phone-based workflow needs: messages, calls, transcripts, and contacts.
OAuth authentication, no API keys to manage in client config, and respects existing Quo role permissions.
First business phone system listed in Anthropic's connector directory, indicating active maintenance.

Limitations

Not covered under Quo's Business Associate Agreement, so it is not suitable for PHI/HIPAA-regulated workflows.
Call transcripts are only available on plans where transcription is enabled, and outbound SMS requires pre-paid credits.
No self-hosted/open-source option; you must trust the hosted endpoint and use the supported clients (Claude or ChatGPT Plus/Pro).

Alternatives

Twilio MCP server (community implementations) for raw programmable SMS/voice without the business phone UX.
Dialpad and RingCentral integrations via Zapier MCP for similar business phone coverage when not on Quo.
Community OpenPhone/Quo API wrappers such as EfrainTorres/armavita-quo-mcp on GitHub for self-hosted stdio workflows.