How to integrate Missive MCP with Mastra AI

This guide walks you through connecting Missive to Mastra AI using the Composio tool router. By the end, you'll have a working Missive agent that can list all team members for marketing, create a draft email for client follow-up, send a chat message in project conversation through natural language commands. This guide will help you understand how to give your Mastra AI agent real control over a Missive account through Composio's Missive MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Get started for free Get a demo

Missive

Api Key

Missive is a collaborative email and chat app for teams to manage conversations and tasks together. It helps streamline team inboxes, shared labels, and internal discussion in one place.

40 Tools

Managed auth

Connect Missive without auth hassles

We manage OAuth, API keys, token refresh, and scopes — you just build.

Try for free

Introduction

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

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

Also integrate Missive with

OpenAI Agents SDK Claude Agent SDK Claude Code Claude Cowork Codex OpenClaw Hermes CLI Google ADK LangChain Vercel AI SDK LlamaIndex CrewAI

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 Missive tools
Connect Mastra's MCP client to the Composio generated MCP URL
Fetch Missive 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 Missive 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 Missive MCP server, and what's possible with it?

The Missive MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Missive account. It provides structured and secure access to your team's shared inboxes and chat threads, so your agent can perform actions like drafting emails, sending messages, generating reports, and managing team communication on your behalf.

Automated message drafting and scheduling: Let your agent create and save email, SMS, WhatsApp, or live chat drafts for later editing or scheduled sending.
Instant message sending in conversations: Have your agent send new messages directly to any Missive conversation, keeping your team in the loop in real time.
Team and user management: Effortlessly list all teams and their members, or pull a full directory of users in your Missive organization for easy coordination and task assignment.
Analytics report generation: Direct your agent to create detailed analytics reports across time ranges and filters, helping your team track productivity and engagement.
Webhook automation setup: Enable your agent to create or delete webhook subscriptions, so you can automate notifications and integrations with other tools as needed.

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:

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

Step-by-step Guide

Step by step09 STEPS

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

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 Missive through MCP.

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

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

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

Create a Tool Router session for Missive

typescript

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

  const composioMCPUrl = session.mcp.url;
  console.log("Missive MCP URL:", composioMCPUrl);

What's happening:

create spins up a short-lived MCP HTTP endpoint for this user
The toolkits array contains "missive" for Missive access
session.mcp.url is the MCP URL that Mastra's MCPClient will connect to

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 Missive toolkit

Create the Mastra agent

typescript

const agent = new Agent({
    name: "missive-mastra-agent",
    instructions: "You are an AI agent with Missive 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

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: {
        missive: 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 Missive 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 Missive 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: ["missive"],
  });

  const composioMCPUrl = session.mcp.url;

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

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "missive-mastra-agent",
    instructions: "You are an AI agent with Missive 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: { missive: 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 Missive 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 Missive action and event your agent gets out of the box.

Create Analytics Report

Tool to create an analytics report.

Create Missive Contacts

Tool to create one or more contacts in a Missive contact book.

Create Draft

Tool to create a new draft in Missive.

Create Missive Post

Tool to create a post in a Missive conversation.

Create Canned Response

Tool to create one or more canned responses (templates) in Missive.

Create Shared Label

Tool to create one or more shared labels at the organization level.

Create Missive Task

Tool to create a task in Missive.

Create Team

Tool to create a new team in an organization.

Create Webhook

Tool to create a webhook subscription.

Delete Draft

Tool to delete a draft from a conversation by draft ID.

Delete Post

Tool to delete a post from a conversation by post ID.

Delete Saved Responses

Tool to delete one or more saved responses by ID.

Delete Webhook

Tool to delete a webhook subscription by webhook ID.

Get Analytics Report

Tool to fetch a completed analytics report using its ID.

Get Missive Contact

Tool to fetch a specific contact using the contact ID.

Get Missive Conversation

Tool to fetch full conversation metadata (assignees/users/labels/team/org) for a specific conversation ID.

List Conversation Messages

Tool to list messages belonging to a Missive conversation (newest first).

Get Missive Message

Tool to fetch full message details including headers, HTML body, and attachments.

Get Missive Response

Tool to fetch a specific saved response using the response ID.

Get Missive Task

Tool to get a single task by ID with full details including assignees, team, and conversation info.

List Missive Contact Books

Tool to list contact books the authenticated user has access to.

List Missive Contact Groups

Tool to list contact groups or organizations linked to a contact book.

List Missive Contacts

Tool to list contacts from a contact book.

List Conversation Comments

Tool to list comments in a Missive conversation ordered from newest to oldest.

List Conversation Drafts

Tool to list draft messages in a Missive conversation (newest first).

List Conversation Posts

Tool to list posts in a Missive conversation ordered by newest first.

List Missive Conversations

Tool to list conversations visible to the authenticated user ordered by newest activity first.

List Messages by Message-ID

Tool to fetch messages matching an email Message-ID header.

List Missive Organizations

Tool to list organizations the authenticated user is part of.

List Missive Saved Responses

Tool to list saved responses (canned responses/templates) for the authenticated user.

List Missive Shared Labels

Tool to list shared labels (organization-level labels) available to the authenticated user.

List Missive Tasks

Tool to list tasks accessible to the authenticated user.

List Missive Teams

Tool to list all teams.

List Missive Users

Tool to list all users.

Merge Missive Conversations

Tool to merge multiple conversations into one.

Update Missive Contact

Tool to update one or more contacts in Missive.

Update Saved Response

Tool to update one or more saved responses in Missive.

Update Shared Labels

Tool to update one or more shared labels in Missive.

Update Missive Task

Tool to update an existing task's attributes in Missive.

Update Missive Team

Tool to update one or more teams in Missive.

FRAMEWORKS

How to build Missive MCP Agent with another framework

OpenAI Agents SDK

Use Missive MCP with OpenAI Agents SDK

Claude Agent SDK

Use Missive MCP with Claude Agent SDK

Claude Code

Use Missive MCP with Claude Code

Claude Cowork

Use Missive MCP with Claude Cowork

Codex

Use Missive MCP with Codex

OpenClaw

Use Missive MCP with OpenClaw

Hermes

Use Missive MCP with Hermes

CLI

Use Missive MCP with CLI

Google ADK

Use Missive MCP with Google ADK

LangChain

Use Missive MCP with LangChain

Vercel AI SDK

Use Missive MCP with Vercel AI SDK

LlamaIndex

Use Missive MCP with LlamaIndex

CrewAI

Use Missive MCP with CrewAI

MORE TOOLKITS

Explore Other Toolkits

Toolkit marketplace

Gmail

Oauth2

Gmail is Google's email service with powerful spam protection, search, and G Suite integration. It keeps your inbox organized and makes communication fast and reliable.

Outlook

Oauth2S2s Oauth2

Outlook is Microsoft's email and calendaring platform for unified communications and scheduling. It helps users stay organized with powerful email, contacts, and calendar management.

Slack

Oauth2

Slack is a channel-based messaging platform for teams and organizations. It helps people collaborate in real time, share files, and connect all their tools in one place.

Gong

BasicOauth2

Gong is a platform for video meetings, call recording, and team collaboration. It helps teams capture conversations, analyze calls, and turn insights into action.

FAQ

Frequently asked questions

With a standalone Missive MCP server, the agents and LLMs can only access a fixed set of Missive tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Missive 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 Missive tools.

Yes, absolutely. You can configure which Missive 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 Missive data and credentials are handled as safely as possible.

Start with Missive.It takes 30 seconds.

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

Start building

Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREE BOOK A DEMO

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati

Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya

Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave

CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu

Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola

Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche

Co-Founder, Ingram Technologies

How to integrate Missive MCP with Mastra AI

Connect Missive without auth hassles

Introduction

Also integrate Missive with

TL;DR

What is Mastra AI?

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

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

What is Composio SDK?

How the Composio SDK works

Step-by-step Guide

Prerequisites

Getting API Keys for OpenAI and Composio

Install dependencies

Set up environment variables

Import libraries and validate environment

Create a Tool Router session for Missive

Configure Mastra MCP client and fetch tools

Create the Mastra agent

Set up interactive chat interface

Complete Code

Conclusion

Supported Tools

How to build Missive MCP Agent with another framework

OpenAI Agents SDK

Claude Agent SDK

Claude Code

Claude Cowork

Codex

OpenClaw

Hermes

CLI

Google ADK

LangChain

Vercel AI SDK

LlamaIndex

CrewAI

Explore Other Toolkits

Gmail

Outlook

Slack

Gong

Frequently asked questions

What are the differences in Tool Router MCP and Missive MCP?+

Can I use Tool Router MCP with Mastra AI?+

Can I manage the permissions and scopes for Missive while using Tool Router?+

How safe is my data with Composio Tool Router?+

Start with Missive.It takes 30 seconds.

Teams ship real agents on Composio