How to integrate Miro MCP with Mastra AI

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.

Miro logoMiro
Oauth2

Miro is a collaborative online whiteboard platform for teams to brainstorm, design, and manage projects visually. It streamlines teamwork by enabling real-time idea sharing, diagramming, and workflow planning in a single space.

73 Tools

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.

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

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
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: {
        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
TOOLS

Supported Tools

Every Miro action and event your agent gets out of the box.

Attach Tag To Item

Tool to attach an existing tag to a specific item on a Miro board.

Create App Card Item

Tool to add an app card item to a board.

Create Board

Tool to create a new board.

Create Card Item

Tool to create a card item on a Miro board.

Create Connector

Tool to create a connector (edge/arrow) that links two existing board items.

Create Document Item

Tool to create a document item on a Miro board by providing a URL to the document.

Create Document Item Using File From Device

Tool to create a document item on a Miro board using a URL to the document.

Create Embed Item

Tool to create an embed item on a Miro board by providing a URL to embed content (YouTube videos, websites, etc.

Create Frame Item

Tool to add a frame item to a Miro board.

Create Group

Tool to create a group on a Miro board by grouping multiple items together.

Create Image Item Using Local File

Tool to create an image item on a Miro board by uploading a local image file.

Create Items in Bulk

Tool 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 Item

Tool to create a shape item on a Miro board.

Create Sticky Note Item

Tool to create a sticky note item on a Miro board.

Create Tag

Tool to create a new tag on a Miro board.

Create Text Item

Tool to create a text item on a Miro board.

Delete App Card Item

Tool to delete an app card item from a board.

Delete Card Item

Tool to delete a card item from a board.

Delete Connector

Tool to delete a specific connector from a board.

Delete Document Item

Tool to delete a document item from a board.

Delete Embed Item

Tool to delete an embed item from a board.

Delete Frame Item

Tool to delete a frame item from a Miro board.

Delete Group

Tool to delete a group from a board.

Delete Image Item

Tool to delete an image item from a board.

Delete Item

Tool 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 Item

Tool to delete a shape item from a board.

Delete Sticky Note Item

Tool to delete a sticky note item from a board.

Delete Tag

Tool to delete a specific tag from a board.

Delete Text Item

Tool to delete a text item from a board.

Get All Groups

Tool to retrieve all groups on a Miro board with cursor-based pagination.

Get App Card Item 2

Tool to retrieve a specific app card item by its ID from a Miro board.

Get Board Items

Tool to list items on a Miro board (shapes, stickies, cards, etc.

Get Board Members

Tool to retrieve a list of members for a board.

Get Boards V2

Tool to retrieve accessible boards with optional filters.

Get Card Item

Tool to retrieve a specific card item from a Miro board.

Get Connector

Tool to retrieve a specific connector by its ID.

Get Connectors

Tool to retrieve a list of connectors on a board.

Get Document Item

Tool to retrieve a specific document item from a Miro board by its ID.

Get Embed Item

Tool to retrieve a specific embed item from a board by its ID.

Get Frame Item

Tool to retrieve a specific frame item from a Miro board.

Get Group By ID

Tool to retrieve a specific group by its ID.

Get Image Item

Tool to retrieve a specific image item from a board.

Get Item Tags

Tool to retrieve tags attached to a specific item on a Miro board.

Get Mind Map Node

Tool 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 Data

Tool to retrieve oEmbed data for a Miro board.

Get Shape Item

Tool to retrieve a specific shape item from a Miro board by its ID.

Get Specific Board

Tool to retrieve detailed information about a specific board by its ID.

Get Specific Board Member

Tool to retrieve details of a specific board member.

Get Specific Item

Tool to retrieve a specific item from a Miro board by its ID.

Get Sticky Note Item

Tool to retrieve a specific sticky note item from a board by its ID.

Get Tag

Tool to retrieve details of a specific tag on a board.

Get Text Item

Tool to retrieve a specific text item from a Miro board by its ID.

List Board Tags

Tool to list all tags on a Miro board.

Get Organization Context

Retrieves the organization associated with the current access token.

Share Board

Tool to share a board by inviting users via email.

Update App Card Item 2

Tool to update an app card item on a Miro board.

Update Board

Tool to update properties of a specific board.

Update Board Member

Tool to update the role of a specific board member.

Update Card Item

Tool to update a card item on a Miro board.

Update Connector

Tool to update an existing connector on a Miro board.

Update Document Item

Tool to update a document item on a Miro board.

Update Embed Item

Tool to update an embed item on a board.

Update Frame Item

Tool to update a frame item on a Miro board.

Update Group

Tool to update a group on a Miro board with new items.

Update Image Item

Tool to update an existing image item on a board.

Update Item Position or Parent

Tool to update an item's position or parent frame on a Miro board.

Update Shape Item

Tool to update an existing shape item on a Miro board.

Update Sticky Note Item

Tool to update a sticky note item on a Miro board.

Update Tag

Tool to update a tag on a board.

Update Text Item

Tool to update a text item on a Miro board.

FAQ

Frequently asked questions

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.

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.

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.

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.

Start with Miro.It takes 30 seconds.

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

Start building