How do I get a Miro Access Token?

Go to [**Miro Developer Portal**](https://developers.miro.com/), create an app, and generate a Personal Access Token (PAT) or set up OAuth 2.0. PATs are simpler for personal use — go to your app settings and create a token under 'Personal Access Tokens'. Copy it immediately as it won't be shown again.

Can I create sticky notes programmatically?

Yes! Use `create_sticky_note` with the board ID and content text. Optionally set x,y coordinates on the canvas for precise positioning. The sticky note will appear on the board immediately and all collaborators will see it in real-time.

Can I manage board members via the API?

Yes! Use `list_board_members` to see who has access and their roles, and `add_board_member` to grant access to new users with a specific role (owner, admin, editor, commenter, viewer). The user must already have a Miro account.

Can I filter board items by type?

Yes! Use `list_board_items` with the type parameter to filter by: sticky_note, card, shape, text, connector, image, embed, frame, document, or mind_map. This is useful for finding specific widget types without loading all board content.

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

Name: Miro
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 14 Tools Framework

Connect your CrewAI agents to Miro through Vinkius, pass the Edge URL in the `mcps` parameter and every Miro tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Miro Specialist",
    goal="Help users interact with Miro effectively",
    backstory=(
        "You are an expert at leveraging Miro tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Miro "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 14 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

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.

When paired with CrewAI, Miro becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Miro tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

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 CrewAI 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 CrewAI via MCP

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

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 14 tools from Miro

Why Use CrewAI with the Miro MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Miro through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Miro + CrewAI Use Cases

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

Automated multi-step research: a reconnaissance agent queries Miro for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Miro, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Miro tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Miro against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Miro MCP Tools for CrewAI (14)

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

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

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

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

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

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

delete_board_item

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

get_board

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

get_board_item

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

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

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

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

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

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

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 CrewAI

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

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

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

"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 CrewAI

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

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Miro + CrewAI FAQ

Common questions about integrating Miro MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.