How to integrate Quo MCP with Mastra AI

This guide walks you through connecting Quo to Mastra AI 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 Mastra AI 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 Mastra AI 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 Mastra AI 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:
  • Set up your environment so Mastra, OpenAI, and Composio work together
  • Create a Tool Router session in Composio that exposes Quo tools
  • Connect Mastra's MCP client to the Composio generated MCP URL
  • Fetch Quo tool definitions and attach them as a toolset
  • Build a Mastra agent that can reason, call tools, and return structured results
  • Run an interactive CLI where you can chat with your Quo agent

What is Mastra AI?

Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP.

Key features include:

  • MCP Client: Built-in support for Model Context Protocol servers
  • Toolsets: Organize tools into logical groups
  • Step Callbacks: Monitor and debug agent execution
  • OpenAI Integration: Works with OpenAI models via @ai-sdk/openai

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

Prerequisites

Before starting, make sure you have:
  • Node.js 18 or higher
  • A Composio account with an active API key
  • An OpenAI API key
  • Basic familiarity with TypeScript
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key.
  • You need credits or a connected billing setup to use the models.
  • Store the key somewhere safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Go to Settings and copy your API key.
  • This key lets your Mastra agent talk to Composio and reach Quo through MCP.
3

Install dependencies

bash
npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv

Install the required packages.

What's happening:

  • @composio/core is the Composio SDK for creating MCP sessions
  • @mastra/core provides the Agent class
  • @mastra/mcp is Mastra's MCP client
  • @ai-sdk/openai is the model wrapper for OpenAI
  • dotenv loads environment variables from .env
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_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 your requests to Composio
  • COMPOSIO_USER_ID tells Composio which user this session belongs to
  • OPENAI_API_KEY lets the Mastra agent call OpenAI models
5

Import libraries and validate environment

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey as string,
});
What's happening:
  • dotenv/config auto loads your .env so process.env.* is available
  • openai gives you a Mastra compatible model wrapper
  • Agent is the Mastra agent that will call tools and produce answers
  • MCPClient connects Mastra to your Composio MCP server
  • Composio is used to create a Tool Router session
6

Create a Tool Router session for Quo

typescript
async function main() {
  const session = await composio.create(
    composioUserID as string,
    {
      toolkits: ["quo"],
    },
  );

  const composioMCPUrl = session.mcp.url;
  console.log("Quo MCP URL:", composioMCPUrl);
What's happening:
  • create spins up a short-lived MCP HTTP endpoint for this user
  • The toolkits array contains "quo" for Quo access
  • session.mcp.url is the MCP URL that Mastra's MCPClient will connect to
7

Configure Mastra MCP client and fetch tools

typescript
const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      nasdaq: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

console.log("Fetching MCP tools from Composio...");
const composioTools = await mcpClient.getTools();
console.log("Number of tools:", Object.keys(composioTools).length);
What's happening:
  • MCPClient takes an id for this client and a list of MCP servers
  • The headers property includes the x-api-key for authentication
  • getTools fetches the tool definitions exposed by the Quo toolkit
8

Create the Mastra agent

typescript
const agent = new Agent({
    name: "quo-mastra-agent",
    instructions: "You are an AI agent with Quo tools via Composio.",
    model: "openai/gpt-5",
  });
What's happening:
  • Agent is the core Mastra agent
  • name is just an identifier for logging and debugging
  • instructions guide the agent to use tools instead of only answering in natural language
  • model uses openai("gpt-5") to configure the underlying LLM
9

Set up interactive chat interface

typescript
let messages: AiMessageType[] = [];

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

const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout,
  prompt: "> ",
});

rl.prompt();

rl.on("line", async (userInput: string) => {
  const trimmedInput = userInput.trim();

  if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) {
    console.log("\nGoodbye!");
    rl.close();
    process.exit(0);
  }

  if (!trimmedInput) {
    rl.prompt();
    return;
  }

  messages.push({
    id: crypto.randomUUID(),
    role: "user",
    content: trimmedInput,
  });

  console.log("\nAgent is thinking...\n");

  try {
    const response = await agent.generate(messages, {
      toolsets: {
        quo: composioTools,
      },
      maxSteps: 8,
    });

    const { text } = response;

    if (text && text.trim().length > 0) {
      console.log(`Agent: ${text}\n`);
        messages.push({
          id: crypto.randomUUID(),
          role: "assistant",
          content: text,
        });
      }
    } catch (error) {
      console.error("\nError:", error);
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    console.log("\nSession ended.");
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});
What's happening:
  • messages keeps the full conversation history in Mastra's expected format
  • agent.generate runs the agent with conversation history and Quo toolsets
  • maxSteps limits how many tool calls the agent can take in a single run
  • onStepFinish is a hook that prints intermediate steps for debugging

Complete Code

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

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({ apiKey: composioAPIKey as string });

async function main() {
  const session = await composio.create(composioUserID as string, {
    toolkits: ["quo"],
  });

  const composioMCPUrl = session.mcp.url;

  const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      quo: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "quo-mastra-agent",
    instructions: "You are an AI agent with Quo tools via Composio.",
    model: "openai/gpt-5",
  });

  let messages: AiMessageType[] = [];

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: "> ",
  });

  rl.prompt();

  rl.on("line", async (input: string) => {
    const trimmed = input.trim();
    if (["exit", "quit"].includes(trimmed.toLowerCase())) {
      rl.close();
      return;
    }

    messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed });

    const { text } = await agent.generate(messages, {
      toolsets: { quo: composioTools },
      maxSteps: 8,
    });

    if (text) {
      console.log(`Agent: ${text}\n`);
      messages.push({ id: crypto.randomUUID(), role: "assistant", content: text });
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main();

Conclusion

You've built a Mastra AI agent that can interact with Quo through Composio's Tool Router. You can extend this further by:
  • Adding other toolkits like Gmail, Slack, or GitHub
  • Building a web-based chat interface around this agent
  • Using multiple MCP endpoints to enable cross-app workflows
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. Mastra AI 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