> ## Documentation Index
> Fetch the complete documentation index at: https://support.quo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP for custom AI agents

> Connect Quo to your own agent or any MCP-compatible AI client using Quo's remote MCP server URL.

<Note>
  To use integrations, you must have the [Quo Desktop app installed](https://support.quo.com/getting-started/install-apps).
</Note>

## Overview

Quo is an [official Claude connector](https://support.quo.com/core-concepts/integrations/mcp/claude) and an [official ChatGPT connector](https://support.quo.com/core-concepts/integrations/mcp/chatgpt), with one-click setup in each app's directory. If you're building your own agent or using a different AI client, you can connect to the same Quo data through Quo's remote MCP server URL.

The integration uses the Model Context Protocol (MCP), an open standard that lets AI clients talk to your Quo account securely. Any MCP-compatible client can connect, including custom agents and assistants that support remote MCP servers.

<Note>
  Connecting through the MCP server URL is an advanced setup for clients that aren't Claude or ChatGPT. For those two, use the official connectors instead. They're the simplest path and need no manual configuration.
</Note>

***

## Server URL

Add Quo as a remote MCP server in your client using this URL:

```text theme={null}
https://mcp.quo.com/mcp
```

The server uses the Streamable HTTP transport, the current MCP standard, so any client that supports remote MCP servers can connect.

<Note>
  `https://mcp.quo.com` on its own redirects to this resource center. Use the full `https://mcp.quo.com/mcp` path when adding the server to your client.
</Note>

***

## Authenticate

Quo's MCP server uses OAuth 2.1. When you add the server URL, your client opens a Quo sign-in screen in your browser. Log in to the Quo account you want to connect and approve access. Your client handles the connection from there.

<Note>
  Make sure you're logged in to the **Quo account you want to connect before starting.**
</Note>

***

## Available tools

Once connected, the server exposes these tools to your agent. How you invoke them depends on your client, but the capabilities are the same.

| Tool                     | What it does                                                               |
| ------------------------ | -------------------------------------------------------------------------- |
| `fetch-messages`         | Pull message history from a Quo inbox, filtered by contact, date, or inbox |
| `fetch-call-transcripts` | Retrieve call history and voicemail transcripts from a Quo number          |
| `send-message`           | Send a text from your Quo number to one or more recipients                 |
| `create-contact`         | Add a new contact to your Quo account                                      |
| `update-contact`         | Update an existing contact's details                                       |

Each `fetch-messages` or `fetch-call-transcripts` request returns up to **100 records at a time**. Your agent can make multiple requests in a session, so there's no hard cap on how much data you can work with.

<Note>
  Call transcripts are only available on numbers where [call transcripts are enabled](https://support.quo.com/core-concepts/calling/summaries-and-transcripts#call-transcripts-and-summaries).
</Note>

<Warning>
  Pre-paid credits are needed to send texts with `send-message`. These count as API messages. [Learn more about pre-paid credits and usage →](https://support.quo.com/core-concepts/administration/billing/credits-and-usage)
</Warning>

***

## When to use the API instead

The MCP server is the right fit when your agent or client supports remote MCP and you want it to read and act on your Quo data through these tools.

If you're building a product or a workflow that needs full programmatic control, the [Quo API](https://www.quo.com/docs/2026-03-30/introduction) is often the better path. It covers users, contacts, calls, transcripts, messages, phone numbers, and webhooks, and is built with AI agent use cases in mind.

***

## Safety and permissions

<Columns cols={3}>
  <Column>
    <Card title="Write access" icon="badge-check">
      The server can send texts and create or update contacts. Build a confirmation step into your agent before it runs these actions.
    </Card>
  </Column>

  <Column>
    <Card title="Account-limited access" icon="lock">
      The integration only accesses what your Quo account can already see.
    </Card>
  </Column>

  <Column>
    <Card title="OAuth-based" icon="key">
      You sign in through Quo's own login, so your password is never shared with the client.
    </Card>
  </Column>
</Columns>

<Note>
  Treat your connection like a password. Don't share access publicly.
</Note>

***

## FAQs

<AccordionGroup>
  <Accordion title="Which AI clients can connect this way?">
    Any client that supports remote MCP servers. For Claude and ChatGPT, use the [official connectors](https://support.quo.com/core-concepts/integrations/mcp) instead, since setup is simpler and needs no manual configuration.
  </Accordion>

  <Accordion title="What's the difference between this and the official Claude and ChatGPT connectors?">
    The official connectors are one-click installs from each app's directory. The server URL is for everything else, custom agents and other MCP-compatible clients, and requires you to add the server and sign in manually.
  </Accordion>

  <Accordion title="Should I use the MCP server or the Quo API?">
    Use the MCP server when your agent or client supports remote MCP and you want it to work with your Quo data through the available tools. Use the [Quo API](https://www.quo.com/docs/2026-03-30/introduction) when you're building an application or need full programmatic control.
  </Accordion>

  <Accordion title="Does this cost credits?">
    Reading messages and call transcripts doesn't use credits.

    Sending texts with `send-message` uses prepaid messaging credits. [Learn about credits and usage](https://support.quo.com/core-concepts/administration/billing/credits-and-usage).
  </Accordion>

  <Accordion title="My connection keeps dropping. What can I do?">
    Reconnect and sign in to Quo again to refresh your session. Make sure your client supports the Streamable HTTP transport and is pointed at `https://mcp.quo.com/mcp`.
  </Accordion>
</AccordionGroup>

***

Need help? [Submit a support request](https://support.quo.com/help/submit-a-request) and we'll jump in.