How to integrate Mezmo MCP with Mastra AI

This guide walks you through connecting Mezmo to Mastra AI using the Composio tool router. By the end, you'll have a working Mezmo agent that can send application error logs to mezmo, delete outdated pipeline alert for a component, ingest security event logs from last hour through natural language commands. This guide will help you understand how to give your Mastra AI agent real control over a Mezmo account through Composio's Mezmo 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

Mezmo

Api Key

Mezmo is a unified platform for log management and telemetry data processing. It helps you collect, analyze, and manage log data for better operational visibility.

36 Tools

Managed auth

Connect Mezmo 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 Mezmo account through Composio's Mezmo MCP server.

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

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

The Mezmo MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, and more directly to your Mezmo account. It provides structured and secure access to your log management and telemetry pipelines, so your agent can ingest logs, manage pipeline alerts, streamline monitoring, and automate log-driven workflows on your behalf.

Automated log ingestion: Seamlessly send structured log events from any host or service to Mezmo for real-time analysis and monitoring.
Pipeline alert deletion: Direct your agent to remove specific alerts tied to components in your pipelines, helping manage noise and maintain alert hygiene.
Streamlined alert management: Enable your agent to clean up outdated or redundant alerts, keeping your pipeline monitoring focused and actionable.
Real-time telemetry processing: Let your agent push telemetry data instantly for advanced analytics, troubleshooting, and observability workflows.

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 Mezmo 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 Mezmo

typescript

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

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

What's happening:

create spins up a short-lived MCP HTTP endpoint for this user
The toolkits array contains "mezmo" for Mezmo 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 Mezmo toolkit

Create the Mastra agent

typescript

const agent = new Agent({
    name: "mezmo-mastra-agent",
    instructions: "You are an AI agent with Mezmo 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: {
        mezmo: 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 Mezmo 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 Mezmo 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: ["mezmo"],
  });

  const composioMCPUrl = session.mcp.url;

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

  const composioTools = await mcpClient.getTools();

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

Create Category

Tool to create a new category for views, boards, or screens in Mezmo.

Create Ingestion Exclusion Rule

Tool to create an exclusion rule for log ingestion to control costs.

Create API Key

Tool to create a new API key (ingestion or service key) in Mezmo.

Create Member Invitation

Tool to invite a new member to the Mezmo organization with a specified role.

Create Preset Alert

Tool to create a new preset alert in Mezmo with specified name and notification channels.

Create View

Tool to create a new Mezmo view with filtering and alert configuration.

Delete Category

Tool to delete a category by its type and ID.

Delete Ingestion Exclusion

Tool to remove an ingestion exclusion rule by its ID.

Delete API Key

Tool to delete an API key by its unique identifier.

Delete Organization Member

Tool to remove a member from the organization by their email address.

Delete Pipeline Alert

Tool to delete an alert for a specific component within a pipeline.

Delete Preset Alert

Tool to delete a preset alert by its ID.

Delete View

Tool to delete a view by its ID.

Get Preset Alert

Tool to retrieve details of a specific preset alert by its ID.

Get Category

Tool to retrieve a category configuration by its type and ID.

Get Index Rate Alert Configuration

Tool to retrieve current index rate alert settings for the Mezmo account.

Get Ingestion Exclusion Rule

Tool to retrieve an ingestion exclusion rule by its ID.

Get Ingestion Status

Tool to get the current ingestion status for the Mezmo account.

Get API Key

Tool to retrieve an API key configuration by its ID.

Get Member

Tool to retrieve member information by their ID.

Get Stream Configuration

Tool to retrieve the current event streaming configuration for the Mezmo account.

Get View Details

Tool to retrieve details of a specific view by its ID.

Ingest Logs to Mezmo

Ingest log lines into Mezmo Log Analysis.

List Preset Alerts

Tool to list all preset alerts configured for the Mezmo account.

List API Keys

Tool to list all API keys and ingestion keys configured for the account.

List Members

Tool to list all team members in the Mezmo account configuration.

List Telemetry Pipelines

Tool to list all telemetry pipelines configured for the account.

List Views

Tool to list all views configured for the account.

Resume Log Ingestion

Tool to resume log ingestion for the account after it has been stopped.

Update Category

Tool to update a category name by its type and ID.

Update Index Rate Alert Configuration

Tool to configure index rate alerting settings including thresholds and notification channels.

Update Ingestion Exclusion Rule

Tool to update an existing exclusion rule by its ID.

Update API Key

Tool to update an API key name by its ID.

Update Member Role and Groups

Tool to update a member's role and group assignments by their email address.

Update Preset Alert

Tool to update an existing preset alert by ID.

Update Mezmo View

Tool to update an existing Mezmo view by its ID.

FRAMEWORKS

How to build Mezmo MCP Agent with another framework

OpenAI Agents SDK

Use Mezmo MCP with OpenAI Agents SDK

Claude Agent SDK

Use Mezmo MCP with Claude Agent SDK

Claude Code

Use Mezmo MCP with Claude Code

Claude Cowork

Use Mezmo MCP with Claude Cowork

Codex

Use Mezmo MCP with Codex

OpenClaw

Use Mezmo MCP with OpenClaw

Hermes

Use Mezmo MCP with Hermes

CLI

Use Mezmo MCP with CLI

Google ADK

Use Mezmo MCP with Google ADK

LangChain

Use Mezmo MCP with LangChain

Vercel AI SDK

Use Mezmo MCP with Vercel AI SDK

LlamaIndex

Use Mezmo MCP with LlamaIndex

CrewAI

Use Mezmo MCP with CrewAI

MORE TOOLKITS

Explore Other Toolkits

Toolkit marketplace

Supabase

Oauth2Api Key

Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure.

Codeinterpreter

No Auth

Codeinterpreter is a Python-based coding environment with built-in data analysis and visualization. It lets you instantly run scripts, plot results, and prototype solutions inside supported platforms.

GitHub

Oauth2

GitHub is a code hosting platform for version control and collaborative software development. It streamlines project management, code review, and team workflows in one place.

Ably

Api Key

Ably is a real-time messaging platform for live chat and data sync in modern apps. It offers global scale and rock-solid reliability for seamless, instant experiences.

FAQ

Frequently asked questions

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

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

Start with Mezmo.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Mezmo 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 Mezmo MCP with Mastra AI

Connect Mezmo without auth hassles

Introduction

Also integrate Mezmo with

TL;DR

What is Mastra AI?

What is the Mezmo 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 Mezmo

Configure Mastra MCP client and fetch tools

Create the Mastra agent

Set up interactive chat interface

Complete Code

Conclusion

Supported Tools

How to build Mezmo 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

Supabase

Codeinterpreter

GitHub

Ably

Frequently asked questions

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

Can I use Tool Router MCP with Mastra AI?+

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

How safe is my data with Composio Tool Router?+

Start with Mezmo.It takes 30 seconds.

Teams ship real agents on Composio