How to integrate Quo MCP with Claude Code

Manage your Quo directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns. You can do this in two different ways: Via Composio Connect - Direct and easiest approach Via Composio SDK - Programmatic approach with more control

Quo logoQuo
Api Key

Quo is a business phone platform for calls, SMS, contacts, and team conversations. It helps teams manage customer communication from one shared, searchable workspace.

36 Tools

Introduction

Manage your Quo directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Composio Connect - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Also integrate Quo with

Why use Composio?

  • Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
  • Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Handling Large tool responses out of LLM context to minimize context rot.
  • Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

Connecting Quo to Claude Code using Composio

1. Add the Composio MCP to Claude

Terminal

2. Start Claude Code

bash
claude

3. Open your MCP list

bash
/mcp

4. Select Composio and click on Authenticate

Select Composio and click Authenticate

5. This will redirect you to the Composio OAuth page. Complete the flow by authorizing Composio and you're all set.

Composio OAuth authorization page
Composio authorization complete
Ask Claude to connect to your account and authenticate via the link

What is the Quo MCP server, and what's possible with it?

The Quo MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Quo account. It provides structured and secure access to your business calls, messages, contacts, conversations, tasks, users, and webhooks, so your agent can review calls, send text messages, manage contacts, organize conversations and tasks, and monitor webhook activity on your behalf.

  • Call and voicemail review: Have your agent review call participants, routing, status, timing, recordings, voicemail transcripts, and recording details.
  • Messaging and conversation management: Direct your agent to find and read messages, send texts from your Quo numbers, and mark conversations as read, open, or done.
  • Contact organization: Let the agent create, find, update, or delete contacts while working with standard details, custom fields, and external source information.
  • Task coordination: Instruct your agent to create and edit tasks, connect them to calls or conversations, assign teammates, set due dates, and complete or reopen work.
  • Webhook monitoring: Have your agent create, update, review, or remove webhook subscriptions and inspect their delivery activity and outcomes.

Connecting Quo via Composio SDK

Composio SDK is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here Quo) for even more tool search precision. It's secure and reliable.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step10 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A Quo account
  • Basic knowledge of Python or TypeScript
2

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

3

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)
5

Install Composio library

npm install @composio/core dotenv

Install the Composio TypeScript library to create MCP sessions.

  • @composio/core provides the core Composio functionality
  • dotenv loads environment variables from your .env file
6

Generate Composio MCP URL

import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['quo'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http quo-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Create a script to generate a Composio MCP URL for Quo. This URL will be used to connect Claude Code to Quo.

What's happening

  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for Quo
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it
7

Run the script and copy the MCP URL

node --loader ts-node/esm generate_mcp_url.ts
# or if using tsx
tsx generate_mcp_url.ts

Run your TypeScript script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output
8

Add Quo MCP to Claude Code

bash
claude mcp add --transport http quo-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (quo-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

9

Verify the installation

bash
claude mcp list

Check that your Quo MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your quo-composio entry in the list
  • This confirms that Claude Code can now access Quo tools

If everything is wired up, you should see your quo-composio entry listed:

Claude Code MCP list showing the toolkit MCP server
10

Authenticate Quo

The first time you try to use Quo tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with Quo
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the Quo authorization flow
  • Return to the terminal and start using Quo through Claude Code

Once authenticated, you can ask Claude Code to perform Quo operations in natural language. For example:

  • "List unread Quo conversations from today"
  • "Send follow-up SMS to missed callers"
  • "Create tasks from recent customer calls"

Complete Code

Here's the complete code to get you started with Quo and Claude Code:

import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['quo'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http quo-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Conclusion

You've successfully integrated Quo with Claude Code using Composio's MCP server. Now you can interact with Quo directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for Quo operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various Quo operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

TOOLS

Supported Tools

Every Quo action and event your agent gets out of the box.

Create Contact

Create a Quo contact with standard fields, optional custom fields, and external source metadata.

Create Task

Create a task linked to exactly one phone number, conversation, or activity.

Create Webhook

Create one unified webhook subscription for selected Quo events and return its signing secret, which must be stored securely.

Delete Contact

Permanently delete one Quo contact by ID.

Delete Task

Permanently delete one Quo task by ID.

Delete Webhook

Permanently delete one unified Quo webhook and revoke its signing secret.

Get Call

Get one call and its routing, participants, status, and timing details by ID.

Get Call Voicemail

Get voicemail processing status, transcript, duration, and recording URL for a Quo call.

Get Contact

Get one contact with default and custom fields by Quo contact ID.

Get Message

Get one message by Quo message ID, including its content, related IDs, participants, delivery status, and timestamps.

Get Phone Number

Get one Quo phone number and its assignments and restrictions by ID.

Get Task

Get one task and its current links, assignee, due date, and completion state.

Get User

Get one workspace user by Quo user ID.

Get Webhook

Get one unified Quo webhook by its numeric ID.

Get Webhook Delivery

Get the payload and attempt details for one Quo webhook delivery event.

List Call Recordings

List recording segments for a Quo call in chronological order.

List Calls

List calls between a Quo number and one external participant with optional user and creation-time filters.

List Contact Custom Fields

List the workspace's contact custom-field definitions for constructing valid contact values.

List Contacts

List contacts, optionally filtered by external IDs or source, with stable-v1 phone and custom fields.

List Conversations

List inbox conversations with optional phone-number, user, creation-time, update-time, and inactive-state filters.

List Messages

List messages exchanged by a Quo phone number and one or more participants, optionally filtered by sender or creation time.

List Phone Numbers

List Quo phone numbers and their assigned users, calling restrictions, and messaging restrictions.

List Tasks

List workspace tasks with cursor-controlled pagination.

List Users

List workspace users and return one cursor-controlled page.

List Webhook Deliveries

List one page of delivery events for a unified Quo webhook, optionally filtered by status, event type, or dispatch time.

List Webhooks

List unified Quo webhooks across call, message, contact, task, and integration event families.

Send Message

Send an irreversible text message from a Quo number to one or more recipients.

Send Message and Mark Conversation Done

Send an irreversible text message from a Quo number and move the resulting inbox conversation to Done.

Set Conversation Status

Set a Quo conversation to read, done, or open.

Set Task Assignee

Assign or unassign a Quo user on a task.

Set Task Completion

Complete or reopen a Quo task.

Set Task Conversation Link

Link or unlink a Quo task and conversation.

Set Task Due Date

Set or remove a Quo task's due date.

Update Contact

Patch selected standard, custom, or source fields on an existing Quo contact.

Update Task

Replace both the title and description of an existing Quo task.

Update Webhook

Partially update a unified Quo webhook.

FAQ

Frequently asked questions

With a standalone Quo MCP server, the agents and LLMs can only access a fixed set of Quo tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Quo and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Code fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Quo tools.

Yes, absolutely. You can configure which Quo scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Quo data and credentials are handled as safely as possible.

Start with Quo.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Quo tool your agent needs.Free to start.

Start building