How to integrate Miro MCP with Claude Agent SDK

This guide walks you through connecting Miro to the Claude Agent SDK 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 Claude Agent SDK 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 the Claude Agent SDK 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 Claude Agent SDK 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:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Miro
  • Configure an AI agent that can use Miro as a tool
  • Run a live chat session where you can ask the agent to perform Miro operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

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:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Miro account
  • Some knowledge of Python
2

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

npm install @anthropic-ai/claude-agent-sdk @composio/core dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • @composio/core provides Composio integration for Anthropic
  • @anthropic-ai/claude-agent-sdk is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude
5

Import dependencies

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

dotenv.config();
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The dotenv.config() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Miro functionality
6

Create a Composio instance and Tool Router session

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });

  // Create Tool Router session for Miro
  const session = await composio.create(USER_ID, {
    toolkits: ['miro'],
  });
  const mcpUrl = session?.mcp.url;
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Miro
  • The returned url is the MCP server URL that your agent will use
7

Configure Claude Agent with MCP

const options: Options = {
  permissionMode: 'bypassPermissions',
  mcpServers: {
    composio: {
      type: 'http',
      url: mcpUrl,
      headers: { 'x-api-key': COMPOSIO_API_KEY }
    }
  },
  systemPrompt: 'You are a helpful assistant with access to Miro tools via Composio.',
  maxTurns: 10,
};
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permissionMode: 'bypassPermissions' allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Miro
  • maxTurns: 10 limits the conversation length to prevent excessive API usage
8

Create client and start chat loop

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

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}
What's happening:
  • The readline interface is created to handle user input and output
  • The query function is used to send the user's input to the agent
  • The chat loop continues until the user types 'exit' or 'quit'
9

Run the application

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}
What's happening:
  • The chat function is the entry point for the application
  • The try-catch block is used to handle any errors that occur

Complete Code

Here's the complete code to get you started with Miro and Claude Agent SDK:

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });
  const session = await composio.create(USER_ID, {
    toolkits: ['miro']
  });
  const mcp_url = session?.mcp.url;

  const options: Options = {
    permissionMode: 'bypassPermissions',
    mcpServers: {
      composio: {
        type: 'http',
        url: mcp_url,
        headers: { 'x-api-key': COMPOSIO_API_KEY }
      }
    },
    systemPrompt: 'You are a helpful assistant with access to Miro tools via Composio.',
    maxTurns: 10,
  };

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

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Miro through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.
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. Claude Agent SDK 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