How to integrate Miro MCP with Google ADK

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Miro logo
Google ADK logo
divider

Introduction

This guide walks you through connecting Miro to Google ADK 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 Google ADK 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 a Miro account set up and connected to Composio
  • Install the Google ADK and Composio packages
  • Create a Composio Tool Router session for Miro
  • Build an agent that connects to Miro through MCP
  • Interact with Miro using natural language

What is Google ADK?

Google ADK (Agents Development Kit) is Google's framework for building AI agents powered by Gemini models. It provides tools for creating agents that can use external services through the Model Context Protocol.

Key features include:

  • Gemini Integration: Native support for Google's Gemini models
  • MCP Toolset: Built-in support for Model Context Protocol tools
  • Streamable HTTP: Connect to external services through streamable HTTP
  • CLI and Web UI: Run agents via command line or web interface

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:
  • A Google API key for Gemini models
  • A Composio account and API key
  • Python 3.9 or later installed
  • Basic familiarity with Python

Getting API Keys for Google and Composio

Google API Key
  • Go to Google AI Studio and create an API key.
  • Copy the key and keep it safe. You will put this in GOOGLE_API_KEY.
Composio API Key and User ID
  • Log in to the Composio dashboard.
  • Go to Settings → API Keys and copy your Composio API key. Use this for COMPOSIO_API_KEY.
  • Decide on a stable user identifier to scope sessions, often your email or a user ID. Use this for COMPOSIO_USER_ID.

Install dependencies

bash
pip install google-adk composio python-dotenv

Inside your virtual environment, install the required packages.

What's happening:

  • google-adk is Google's Agents Development Kit
  • composio connects your agent to Miro via MCP
  • python-dotenv loads environment variables

Set up ADK project

bash
adk create my_agent

Set up a new Google ADK project.

What's happening:

  • This creates an agent folder with a root agent file and .env file

Set environment variables

bash
GOOGLE_API_KEY=your-google-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id-or-email

Save all your credentials in the .env file.

What's happening:

  • GOOGLE_API_KEY authenticates with Google's Gemini models
  • COMPOSIO_API_KEY authenticates with Composio
  • COMPOSIO_USER_ID identifies the user for session management

Import modules and validate environment

python
import os
import warnings

from composio import Composio
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()

warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")
What's happening:
  • os reads environment variables
  • Composio is the main Composio SDK client
  • GoogleProvider declares that you are using Google ADK as the agent runtime
  • Agent is the Google ADK LLM agent class
  • McpToolset lets the ADK agent call MCP tools over HTTP

Create Composio client and Tool Router session

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["miro"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url,
print(f"Composio MCP URL: {COMPOSIO_MCP_URL}")
What's happening:
  • Authenticates to Composio with your API key
  • Declares Google ADK as the provider
  • Spins up a short-lived MCP endpoint for your user and selected toolkit
  • Stores the MCP HTTP URL for the ADK MCP integration

Set up the McpToolset and create the Agent

python
composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Miro operations."
    ),
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")
What's happening:
  • Connects the ADK agent to the Composio MCP endpoint through McpToolset
  • Uses Gemini as the model powering the agent
  • Lists exact tool names in instruction to reduce misnamed tool calls

Run the agent

bash
# Run in CLI mode
adk run my_agent

# Or run in web UI mode
adk web

Execute the agent from the project root. The web command opens a web portal where you can chat with the agent.

What's happening:

  • adk run runs the agent in CLI mode
  • adk web . opens a web UI for interactive testing

Complete Code

Here's the complete code to get you started with Miro and Google ADK:

python
import os
import warnings

from composio import Composio
from composio_google import GoogleProvider
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()
warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider())

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["miro"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url


composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Miro operations."
    ),  
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")

Conclusion

You've successfully integrated Miro with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Miro using natural language commands.

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate Miro tools
  • Environment variables keep your credentials secure and separate from code
  • Clear agent instructions reduce tool calling errors
  • The ADK web UI provides an interactive interface for testing and development

You can extend this setup by adding more toolkits to the toolkits array in your session configuration.

How to build Miro MCP Agent with another framework

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 Google ADK?

Yes, you can. Google ADK 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.