How to integrate Miro MCP with Mastra AI

Trusted by
AWS
Glean
Zoom
Airtable
GET STARTED FOR FREEGET A DEMO

30 min · no commitment · see it on your stack

Miro logo
Mastra AI logo
divider

Introduction

This guide walks you through connecting Miro to Mastra AI using the Composio tool router. By the end, you'll have a working Miro agent that can create a new board for marketing brainstorm, list all boards owned by your team, show members of the q2 planning board through natural language commands.

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

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

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

The Miro MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Miro account. It provides structured and secure access to your whiteboards, so your agent can create new boards, manage board content, organize workflows, and collaborate visually—all on your behalf.

  • Automated board creation and setup: Instantly instruct your agent to create new Miro boards with specific names and descriptions for projects, brainstorming, or workshops.
  • Visual content management: Ask your agent to add, retrieve, or delete items such as shapes, sticky notes, app cards, or document items from any board, keeping your workspace tidy and up to date.
  • Efficient team and member management: Have your agent fetch and list all members of a board so you can easily track collaborators and manage access.
  • Seamless board organization and retrieval: Let your agent search and retrieve boards by team, owner, or keyword to keep your workspace organized and easy to navigate.
  • Connector and tag insights: Direct your agent to get details on connectors and tags used within boards, helping you map relationships and categorize content visually.

Supported Tools & Triggers

Tools
Attach Tag To ItemTool to attach an existing tag to a specific item on a Miro board.
Create App Card ItemTool to add an app card item to a board.
Create BoardTool to create a new board.
Create Card ItemTool to create a card item on a Miro board.
Create ConnectorTool to create a connector (edge/arrow) that links two existing board items.
Create Document ItemTool to create a document item on a Miro board by providing a URL to the document.
Create Document Item Using File From DeviceTool to create a document item on a Miro board using a URL to the document.
Create Embed ItemTool to create an embed item on a Miro board by providing a URL to embed content (YouTube videos, websites, etc.
Create Frame ItemTool to add a frame item to a Miro board.
Create GroupTool to create a group on a Miro board by grouping multiple items together.
Create Image Item Using Local FileTool to create an image item on a Miro board by uploading a local image file.
Create Items in BulkTool to create multiple items on a Miro board in a single request.
Create Mind Map Node (Experimental)Tool to create a mind map node on a Miro board.
Create Shape ItemTool to create a shape item on a Miro board.
Create Sticky Note ItemTool to create a sticky note item on a Miro board.
Create TagTool to create a new tag on a Miro board.
Create Text ItemTool to create a text item on a Miro board.
Delete App Card ItemTool to delete an app card item from a board.
Delete Card ItemTool to delete a card item from a board.
Delete ConnectorTool to delete a specific connector from a board.
Delete Document ItemTool to delete a document item from a board.
Delete Embed ItemTool to delete an embed item from a board.
Delete Frame ItemTool to delete a frame item from a Miro board.
Delete GroupTool to delete a group from a board.
Delete Image ItemTool to delete an image item from a board.
Delete ItemTool to delete a specific item from a board.
Delete Mind Map Node (Experimental)Tool to delete a mind map node from a board.
Delete Shape ItemTool to delete a shape item from a board.
Delete Sticky Note ItemTool to delete a sticky note item from a board.
Delete TagTool to delete a specific tag from a board.
Delete Text ItemTool to delete a text item from a board.
Get All GroupsTool to retrieve all groups on a Miro board with cursor-based pagination.
Get App Card Item 2Tool to retrieve a specific app card item by its ID from a Miro board.
Get Board ItemsTool to list items on a Miro board (shapes, stickies, cards, etc.
Get Board MembersTool to retrieve a list of members for a board.
Get Boards V2Tool to retrieve accessible boards with optional filters.
Get Card ItemTool to retrieve a specific card item from a Miro board.
Get ConnectorTool to retrieve a specific connector by its ID.
Get ConnectorsTool to retrieve a list of connectors on a board.
Get Document ItemTool to retrieve a specific document item from a Miro board by its ID.
Get Embed ItemTool to retrieve a specific embed item from a board by its ID.
Get Frame ItemTool to retrieve a specific frame item from a Miro board.
Get Group By IDTool to retrieve a specific group by its ID.
Get Image ItemTool to retrieve a specific image item from a board.
Get Item TagsTool to retrieve tags attached to a specific item on a Miro board.
Get Mind Map NodeTool to retrieve a specific mind map node from a board.
Get Mind Map Nodes (Experimental)Tool to retrieve mind map nodes from a Miro board.
Get oEmbed DataTool to retrieve oEmbed data for a Miro board.
Get Shape ItemTool to retrieve a specific shape item from a Miro board by its ID.
Get Specific BoardTool to retrieve detailed information about a specific board by its ID.
Get Specific Board MemberTool to retrieve details of a specific board member.
Get Specific ItemTool to retrieve a specific item from a Miro board by its ID.
Get Sticky Note ItemTool to retrieve a specific sticky note item from a board by its ID.
Get TagTool to retrieve details of a specific tag on a board.
Get Text ItemTool to retrieve a specific text item from a Miro board by its ID.
List Board TagsTool to list all tags on a Miro board.
Get Organization ContextRetrieves the organization associated with the current access token.
Share BoardTool to share a board by inviting users via email.
Update App Card Item 2Tool to update an app card item on a Miro board.
Update BoardTool to update properties of a specific board.
Update Board MemberTool to update the role of a specific board member.
Update Card ItemTool to update a card item on a Miro board.
Update ConnectorTool to update an existing connector on a Miro board.
Update Document ItemTool to update a document item on a Miro board.
Update Embed ItemTool to update an embed item on a board.
Update Frame ItemTool to update a frame item on a Miro board.
Update GroupTool to update a group on a Miro board with new items.
Update Image ItemTool to update an existing image item on a board.
Update Item Position or ParentTool to update an item's position or parent frame on a Miro board.
Update Shape ItemTool to update an existing shape item on a Miro board.
Update Sticky Note ItemTool to update a sticky note item on a Miro board.
Update TagTool to update a tag on a board.
Update Text ItemTool to update a text item on a Miro board.

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

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

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

  const composioMCPUrl = session.mcp.url;
  console.log("Miro MCP URL:", composioMCPUrl);
What's happening:
  • create spins up a short-lived MCP HTTP endpoint for this user
  • The toolkits array contains "miro" for Miro 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 Miro toolkit

Create the Mastra agent

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

  const composioMCPUrl = session.mcp.url;

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

  const composioTools = await mcpClient.getTools();

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

How to build Miro MCP Agent with another framework

ChatGPT logo

ChatGPT

Use Miro MCP with ChatGPT

Antigravity logo

Antigravity

Use Miro MCP with Antigravity

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Miro MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Miro MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Miro MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Miro MCP with Claude Cowork

Codex logo

Codex

Use Miro MCP with Codex

Cursor logo

Cursor

Use Miro MCP with Cursor

OpenClaw logo

OpenClaw

Use Miro MCP with OpenClaw

Hermes logo

Hermes

Use Miro MCP with Hermes

CLI logo

CLI

Use Miro MCP with CLI

Google ADK logo

Google ADK

Use Miro MCP with Google ADK

LangChain logo

LangChain

Use Miro MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Miro MCP with Vercel AI SDK

LlamaIndex logo

LlamaIndex

Use Miro MCP with LlamaIndex

CrewAI logo

CrewAI

Use Miro MCP with CrewAI

OpenCode logo

OpenCode

Use Miro MCP with OpenCode

VS Code logo

VS Code

Use Miro MCP with VS Code

FAQ

What are the differences in Tool Router MCP and Miro MCP?

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

Can I use Tool Router MCP with Mastra AI?

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 Miro tools.

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

Yes, absolutely. You can configure which Miro 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.

How safe is my data with Composio Tool Router?

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 Miro data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Get started for freeGet a demo↗