How to integrate Quo MCP with CrewAI

This guide walks you through connecting Quo to CrewAI using the Composio tool router. By the end, you'll have a working Quo agent that can get call details and voicemails, get messages, manage contacts, create tasks, and manage webhooks through natural language commands. This guide will help you understand how to give your CrewAI agent real control over a Quo account through Composio's Quo MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

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

This guide walks you through connecting Quo to CrewAI using the Composio tool router. By the end, you'll have a working Quo agent that can get call details and voicemails, get messages, manage contacts, create tasks, and manage webhooks through natural language commands.

This guide will help you understand how to give your CrewAI agent real control over a Quo account through Composio's Quo MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Quo with

TL;DR

Here's what you'll learn:
  • Get a Composio API key and configure your Quo connection
  • Set up CrewAI with an MCP enabled agent
  • Create a Tool Router session or standalone MCP server for Quo
  • Build a conversational loop where your agent can execute Quo operations

What is CrewAI?

CrewAI is a powerful framework for building multi-agent AI systems. It provides primitives for defining agents with specific roles, creating tasks, and orchestrating workflows through crews.

Key features include:

  • Agent Roles: Define specialized agents with specific goals and backstories
  • Task Management: Create tasks with clear descriptions and expected outputs
  • Crew Orchestration: Combine agents and tasks into collaborative workflows
  • MCP Integration: Connect to external tools through Model Context Protocol

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.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

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 step08 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Python 3.9 or higher
  • A Composio account and API key
  • A Quo connection authorized in Composio
  • An OpenAI API key for the CrewAI LLM
  • Basic familiarity with Python
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

bash
pip install composio crewai crewai-tools[mcp] python-dotenv
What's happening:
  • composio connects your agent to Quo via MCP
  • crewai provides Agent, Task, Crew, and LLM primitives
  • crewai-tools[mcp] includes MCP helpers
  • python-dotenv loads environment variables from .env
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID scopes the session to your account
  • OPENAI_API_KEY lets CrewAI use your chosen OpenAI model
5

Import dependencies

python
import os
from composio import Composio
from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
import dotenv

dotenv.load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set")
What's happening:
  • CrewAI classes define agents and tasks, and run the workflow
  • MCPServerHTTP connects the agent to an MCP endpoint
  • Composio will give you a short lived Quo MCP URL
6

Create a Composio Tool Router session for Quo

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)
session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["quo"])

url = session.mcp.url
What's happening:
  • You create a Quo only session through Composio
  • Composio returns an MCP HTTP URL that exposes Quo tools
7

Initialize the MCP Server

python
server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users search the internet effectively",
        backstory="You are a helpful assistant with access to search tools.",
        tools=tools,
        verbose=False,
        max_iter=10,
    )
What's Happening:
  • Server Configuration: The code sets up connection parameters including the MCP server URL, streamable HTTP transport, and Composio API key authentication.
  • MCP Adapter Bridge: MCPServerAdapter acts as a context manager that converts Composio MCP tools into a CrewAI-compatible format.
  • Agent Setup: Creates a CrewAI Agent with a defined role (Search Assistant), goal (help with internet searches), and access to the MCP tools.
  • Configuration Options: The agent includes settings like verbose=False for clean output and max_iter=10 to prevent infinite loops.
  • Dynamic Tool Usage: Once created, the agent automatically accesses all Composio Search tools and decides when to use them based on user queries.
8

Create a CLI Chatloop and define the Crew

python
print("Chat started! Type 'exit' or 'quit' to end.\n")

conversation_context = ""

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ["exit", "quit", "bye"]:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_context += f"\nUser: {user_input}\n"
    print("\nAgent is thinking...\n")

    task = Task(
        description=(
            f"Conversation history:\n{conversation_context}\n\n"
            f"Current request: {user_input}"
        ),
        expected_output="A helpful response addressing the user's request",
        agent=agent,
    )

    crew = Crew(agents=[agent], tasks=[task], verbose=False)
    result = crew.kickoff()
    response = str(result)

    conversation_context += f"Agent: {response}\n"
    print(f"Agent: {response}\n")
What's Happening:
  • Interactive CLI Setup: The code creates an infinite loop that continuously prompts for user input and maintains the entire conversation history in a string variable.
  • Input Validation: Empty inputs are ignored to prevent processing blank messages and keep the conversation clean.
  • Context Building: Each user message is appended to the conversation context, which preserves the full dialogue history for better agent responses.
  • Dynamic Task Creation: For every user input, a new Task is created that includes both the full conversation history and the current request as context.
  • Crew Execution: A Crew is instantiated with the agent and task, then kicked off to process the request and generate a response.
  • Response Management: The agent's response is converted to a string, added to the conversation context, and displayed to the user, maintaining conversational continuity.

Complete Code

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

python
from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter
from composio import Composio
from dotenv import load_dotenv
import os

load_dotenv()

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

# Initialize Composio and create a session
composio = Composio(api_key=COMPOSIO_API_KEY)
session = composio.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["quo"],
)
url = session.mcp.url

# Configure LLM
llm = LLM(
    model="gpt-5",
    api_key=os.getenv("OPENAI_API_KEY"),
)

server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users with internet searches",
        backstory="You are an expert assistant with access to Composio Search tools.",
        tools=tools,
        llm=llm,
        verbose=False,
        max_iter=10,
    )

    print("Chat started! Type 'exit' or 'quit' to end.\n")

    conversation_context = ""

    while True:
        user_input = input("You: ").strip()

        if user_input.lower() in ["exit", "quit", "bye"]:
            print("\nGoodbye!")
            break

        if not user_input:
            continue

        conversation_context += f"\nUser: {user_input}\n"
        print("\nAgent is thinking...\n")

        task = Task(
            description=(
                f"Conversation history:\n{conversation_context}\n\n"
                f"Current request: {user_input}"
            ),
            expected_output="A helpful response addressing the user's request",
            agent=agent,
        )

        crew = Crew(agents=[agent], tasks=[task], verbose=False)
        result = crew.kickoff()
        response = str(result)

        conversation_context += f"Agent: {response}\n"
        print(f"Agent: {response}\n")

Conclusion

You now have a CrewAI agent connected to Quo through Composio's Tool Router. The agent can perform Quo operations through natural language commands.

Next steps:

  • Add role-specific instructions to customize agent behavior
  • Plug in more toolkits for multi-app workflows
  • Chain tasks for complex multi-step operations
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. CrewAI 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