2,500+ MCP servers ready to use
Vinkius

Miro MCP Server for AutoGen 14 tools — connect in under 2 minutes

Built by Vinkius GDPR 14 Tools Framework

Microsoft AutoGen enables multi-agent conversations where agents negotiate, delegate, and execute tasks collaboratively. Add Miro as an MCP tool provider through the Vinkius and every agent in the group can access live data and take action.

Vinkius supports streamable HTTP and SSE.

python
import asyncio
from autogen_agentchat.agents import AssistantAgent
from autogen_ext.tools.mcp import McpWorkbench

async def main():
    # Your Vinkius token — get it at cloud.vinkius.com
    async with McpWorkbench(
        server_params={"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"},
        transport="streamable_http",
    ) as workbench:
        tools = await workbench.list_tools()
        agent = AssistantAgent(
            name="miro_agent",
            tools=tools,
            system_message=(
                "You help users with Miro. "
                "14 tools available."
            ),
        )
        print(f"Agent ready with {len(tools)} tools")

asyncio.run(main())
Miro
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Miro MCP Server

Connect your Miro account to any AI agent and take full control of your visual collaboration through natural conversation.

AutoGen enables multi-agent conversations where agents negotiate, delegate, and collaboratively use Miro tools. Connect 14 tools through the Vinkius and assign role-based access — a data analyst queries while a reviewer validates, with optional human-in-the-loop approval for sensitive operations.

What you can do

  • Board Management — List, create, update and inspect boards with their descriptions, owners and permissions
  • Item Operations — Browse all widgets on a board (sticky notes, cards, shapes, texts, connectors, images) with their content and positions
  • Content Creation — Create sticky notes and cards programmatically with custom content and canvas positions
  • Member Management — List board members and add new users with specific roles (owner, admin, editor, commenter, viewer)
  • Comments — Read and add comments on boards for async collaboration feedback

The Miro MCP Server exposes 14 tools through the Vinkius. Connect it to AutoGen in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Miro to AutoGen via MCP

Follow these steps to integrate the Miro MCP Server with AutoGen.

01

Install AutoGen

Run pip install "autogen-ext[mcp]"

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Integrate into workflow

Use the agent in your AutoGen multi-agent orchestration

04

Explore tools

The workbench discovers 14 tools from Miro automatically

Why Use AutoGen with the Miro MCP Server

AutoGen provides unique advantages when paired with Miro through the Model Context Protocol.

01

Multi-agent conversations: multiple AutoGen agents discuss, delegate, and collaboratively use Miro tools to solve complex tasks

02

Role-based architecture lets you assign Miro tool access to specific agents — a data analyst queries while a reviewer validates

03

Human-in-the-loop support: agents can pause for human approval before executing sensitive Miro tool calls

04

Code execution sandbox: AutoGen agents can write and run code that processes Miro tool responses in an isolated environment

Miro + AutoGen Use Cases

Practical scenarios where AutoGen combined with the Miro MCP Server delivers measurable value.

01

Collaborative analysis: one agent queries Miro while another validates results and a third generates the final report

02

Automated review pipelines: a researcher agent fetches data from Miro, a critic agent evaluates quality, and a writer produces the output

03

Interactive planning: agents negotiate task allocation using Miro data to make informed decisions about resource distribution

04

Code generation with live data: an AutoGen coder agent writes scripts that process Miro responses in a sandboxed execution environment

Miro MCP Tools for AutoGen (14)

These 14 tools become available when you connect Miro to AutoGen via MCP:

01

add_board_member

Requires the board ID and user ID. Optionally set the role (owner, admin, editor, commenter, viewer). The user must already have a Miro account. Add a member to a Miro board

02

create_board

Requires the board name and optionally a description. Returns the created board with its ID, view link and edit link. Create a new Miro board

03

create_card

Requires the board ID and card title. Optionally set a description and x,y position. Cards are structured content widgets with title and description fields. Create a card widget on a Miro board

04

create_comment

Requires the board ID and comment content. Optionally reply to an existing comment by providing its ID as parent_id. Add a comment to a Miro board

05

create_sticky_note

Requires the board ID and the sticky note content (text). Optionally set the x,y position on the canvas. Returns the created sticky note with its ID and position. Create a sticky note on a Miro board

06

delete_board_item

Provide the board ID and item ID. WARNING: this action is irreversible. Delete an item from a Miro board

07

get_board

Provide the board ID (found in the board URL or from list_boards). Get details for a specific Miro board

08

get_board_item

Provide the board ID and item ID. Get details for a specific item on a Miro board

09

get_user_context

Returns user ID, name, email, avatar and account type. Use this to verify your access token is working correctly and to see which user identity the API calls will appear as. Get the authenticated Miro user context

10

list_board_items

) placed on a Miro board. Each item includes its type, ID, content, position, rotation, size and style. Optionally filter by item type (sticky_note, card, shape, text, connector, image, embed, frame, document, mind_map) and set a limit. List items (widgets) on a Miro board

11

list_board_members

Each member shows their user ID, name, email, role (owner, admin, editor, commenter, viewer) and permission level. Optionally set a limit. List members of a Miro board

12

list_boards

Each board includes its ID, name, description, creation date, owner and permissions. Optionally set a limit on the number of results. Use this to discover boards before accessing their content. List Miro boards accessible by the user

13

list_comments

Each comment includes its ID, content text, author info, creation date and parent comment ID (for replies). Optionally set a limit. List comments on a Miro board

14

update_board

Provide the board ID and the new name and/or description. Only provided fields will be updated. Update a Miro board name or description

Example Prompts for Miro in AutoGen

Ready-to-use prompts you can give your AutoGen agent to start working with Miro immediately.

01

"Show me all the sticky notes on my Sprint Planning board."

02

"Create a new board called 'Q2 OKRs' with a description 'Quarterly objectives and key results'."

03

"Add a sticky note to my board saying 'Meeting notes: Discussed API versioning strategy' at position x:100, y:200."

Troubleshooting Miro MCP Server with AutoGen

Common issues when connecting Miro to AutoGen through the Vinkius, and how to resolve them.

01

McpWorkbench not found

Install: pip install "autogen-ext[mcp]"

Miro + AutoGen FAQ

Common questions about integrating Miro MCP Server with AutoGen.

01

How does AutoGen connect to MCP servers?

Create an MCP tool adapter and assign it to one or more agents in the group chat. AutoGen agents can then call Miro tools during their conversation turns.
02

Can different agents have different MCP tool access?

Yes. AutoGen's role-based architecture lets you assign specific MCP tools to specific agents, so a querying agent has different capabilities than a reviewing agent.
03

Does AutoGen support human approval for tool calls?

Yes. Configure human-in-the-loop mode so agents pause and request approval before executing sensitive MCP tool calls.

Connect Miro to AutoGen

Get your token, paste the configuration, and start using 14 tools in under 2 minutes. No API key management needed.