Miro

Miro MCP Server

Run your Miro workshops, retros, and planning sessions from the command line. Read boards, create stickies, organize frames, and generate diagrams through Claude, Cursor, or any MCP client.

Community project — Not officially affiliated with Miro. See official options below.

110 tools | Single binary | All platforms | All major AI tools

[CI] [lint] [CodeScene Average Code Health] [License: MIT] [Go Reference] [codecov] [MCP context]

Documentation

Quick Start

1. Install

Homebrew (macOS/Linux):

brew tap olgasafonova/tap && brew install miro-mcp-server

One-liner (macOS/Linux):

curl -fsSL https://raw.githubusercontent.com/olgasafonova/miro-mcp-server/main/install.sh | sh

Docker:

docker pull ghcr.io/olgasafonova/miro-mcp-server:latest

Manual download: See SETUP.md for all platforms

2. Get a Miro Token

1. Go to miro.com/app/settings/user-profile/apps
2. Create an app with boards:read and boards:write permissions
3. Install to your team and copy the token

3. Configure Your AI Tool

Claude Code:

claude mcp add miro -e MIRO_ACCESS_TOKEN=your-token -- miro-mcp-server

Claude Desktop / Cursor / VS Code: See SETUP.md

Cursor Marketplace:

/add-plugin miro

Not working? Tell us what made it hard — even one sentence helps.

What You Can Do

Voice Examples

• "Add a yellow sticky saying 'Review PRs'"
• "Create a flowchart: Start → Decision → End"
• "What boards do I have?"
• "Share the Design board with [email protected]"
• "Create a mindmap with 'Project Ideas' as root"

Companion Skill: miro-workflow

[Validated by SkillCheck Pro]

For Claude clients that support skills (Claude Code, Claude Desktop), this repo includes a miro-workflow skill that describes how to assemble a few common board layouts from the atomic create-item tools.

Five layouts are covered:

Each one specifies frame sizes, gap math, sticky placement, color conventions (the Miro API takes hex for frame fills and named values for stickies; two different vocabularies), and the tool-call order to follow. For single-tool calls ("add one sticky") or read-only inspection, the atomic tools are usually enough on their own.

The skill is new and likely needs adjustment as more layouts get exercised against real boards. Files live under skills/miro-workflow/. Claude Code auto-discovers skills from ~/Projects/claude-code-config/skills/; for other hosts, follow your client's skill installation docs.

The badge above is awarded by SkillCheck Pro; this skill currently scores 92/100 with zero Critical issues and zero Warnings. Skills in this repo earn the badge at ≥90/100 with zero Critical and zero Warnings; below that bar, the badge is dropped until the skill passes again.

Companion CLI: miro-cli

For shell-first usage, this server has a sibling: miro-cli. Same author, same Miro API coverage, different runtime. One verb per endpoint, JSON in and out, plus a local SQLite mirror for offline search. Reach for it when you're scripting Miro in CI, bulk-migrating stickies between boards, or querying boards offline without burning API quota.

The MCP server and the CLI overlap deliberately. Use the MCP server when an agent runtime is in the loop (Claude Code, Claude Desktop, Cursor). Use the CLI when bash, Makefiles, or CI are. Use both if you want.

Install:

brew install olgasafonova/tap/miro-cli# orgo install github.com/olgasafonova/miro-cli/cmd/miro-cli@latest

Companion MCP Apps server: miro-mcp-apps

If you want Miro data to render as interactive UI in the chat (cards, tables, color clusters, SVG graphs) instead of streamed JSON, there's a TypeScript sibling: miro-mcp-apps. Eleven tools built on the MCP Apps extension (SEP-1865), reusing the same MIRO_ACCESS_TOKEN. The two servers run side-by-side: this one for the 110-tool CRUD surface, that one for visual at-a-glance views.

The MCP Apps pattern is TypeScript-only today (Go SDK has no ext-apps helpers), which is why this companion lives in a separate repo instead of bolting onto the Go server.

Token Efficiency

The full tool surface (110 tools) costs roughly 20.8K tokens of preload; the essentials profile trims that to ~2.8K. For sessions where that footprint matters, set MIRO_TOOLS_PROFILE=essentials in your client config; the server then registers a curated 14-tool subset (boards, list/find/search, sticky/text/frame/connector creation, list/get/update/delete items) plus one discovery meta-tool. Agents reach the rest via miro_tool_search on demand.

Savings: ~17,760 tokens (86.2% reduction) when you opt into essentials. Description tokens are exact (JSON-marshaled); schema cost is estimated at 200 bytes per tool. Reproduce locally with go run ./cmd/token-count/.

miro_tool_search(query?, category?, limit?) is registered in both profiles. It searches tool names, titles, descriptions, and categories with weighted keyword scoring (name 3×, title 2×, category 2.5×, description 1×), returns up to 50 matches, and never recommends itself. Use it when you don't know which tool to reach for, or to scope to a category before browsing. Empty query plus a category returns the category's tools alphabetically.

See CONFIG.md for the full env-var reference.

All 110 Tools

Diagram Generation

Create flowcharts and sequence diagrams from Mermaid syntax:

Flowchart:

flowchart TB    A[Start] --> B{Decision}    B -->|Yes| C[Success]    B -->|No| D[Retry]    D --> B

Sequence Diagram:

sequenceDiagram    Alice->>Bob: Hello Bob!    Bob-->>Alice: Hi Alice!

Supported: flowchart/graph, sequenceDiagram, directions (TB/LR/BT/RL), shapes ([] rectangle, {} diamond, (()) circle), labeled edges.

Why This Server?

Official vs Community

Miro opened a beta of their official MCP server in December 2025, with around 10 tools, and has grown it substantially since. Comparison refreshed 18-09-2026 by enumerating the 45 tools the hosted server actually registers at mcp.miro.com, rather than counting the documented set — the docs lag the deployment in both directions, and the surface moves fast enough that a count is perishable: 65 on 13-08-2026, 63 on 18-08, 61 on 09-09, 45 on 18-09.

The September drop is a consolidation rather than attrition. Every one of the sixteen removed tools is a content read or write path superseded by the canvas_* family — board_list_items, board_show, context_explore, context_get, all three diagram_*, all three doc_*, all four layout_* — and the server's own connection instructions now lead with Canvas Composer SVG as "Miro's unified interaction/representation protocol for the canvas". The 09-09 pass saw it coming: layout_* were still registered but already self-describing as deprecated in favour of canvas. Earlier churn: board_trash and space_delete, present on 17-08-2026, were gone the next day, leaving the surface with no hard-destructive verbs; all five code_widget_* tools present on 18-08 were gone by 09-09, while canvas_search, canvas_load_format_skill and content_item_list_roles arrived. Recent additions come from their changelogs on new MCP tools and code widget endpoints.

Where the differences come from. Spaces, sections, canvas-SVG and prototypes have no endpoints in the public REST API v2 — checked 13-08-2026 against the 114-path OpenAPI spec tracked in api-tracking/, and re-checked by probing the live API, since the spec omits endpoints Miro does ship. Those run on Miro-internal APIs. The reverse also holds: mindmaps, tags, groups, connectors and export are public REST surfaces the official server has not wrapped.

Board context used to be a design difference rather than a gap, and as of 18-09-2026 it is neither: context_get returned a server-side AI summary of a board and has been removed along with context_explore. miro_get_board_content returns the structured content itself — items by type, frame hierarchy, connectors and tags — and lets the model already in your session do the summarizing, with no second inference hop.

When to use the official server: You want zero-setup via plugin marketplace, OAuth 2.1 enterprise security, spaces and sections, comments, or SVG/prototype workflows. Board context extraction is no longer among them — those tools were removed on 18-09-2026.

When to use this server: You need full REST coverage (110 tools, or a tunable 15-tool essentials mode), offline/self-hosted operation, richer board listing metadata, bulk ops, mindmaps, tags, connectors, or export.

Both can coexist — use different MCP server names in your config.

Performance

• Caching: 2-minute TTL reduces API calls
• Rate limiting: Adapts to Miro's rate limit headers
• Circuit breaker: Isolates failing endpoints
• Parallel bulk ops: Creates items concurrently
• Token validation: Fails fast on startup with clear error
• Transient error retry: Auto-retries 502/503/504 with backoff
• OpenTelemetry: Built-in tracing and metrics via mcp-otel-go (OTel Registry)

See PERFORMANCE.md for optimization tips and benchmarks.

HTTP Mode Endpoints

When running with -http :8080:

Health check response:

{  "status": "healthy",  "server": "miro-mcp-server",  "version": "1.21.0",  "uptime": "2h30m",  "components": {    "config": {"status": "healthy"},    "miro_api": {"status": "healthy", "latency": "145ms"}  }}

Development

# Buildmake build
# Run testsmake test
# Run with coveragemake test-cover
# Lintmake lint
# Build for all platformsmake build-all
# See all targetsmake help

Docker Deployment

Quick start:

# Using Docker Composeexport MIRO_ACCESS_TOKEN=your-tokendocker compose up -d
# Or build and run manuallydocker build -t miro-mcp-server .docker run -e MIRO_ACCESS_TOKEN=xxx -p 8080:8080 miro-mcp-server

docker-compose.yml features:

• Health checks configured
• Resource limits template
• Environment variable passthrough

Debugging with MCP Inspector

Test and debug the server interactively with MCP Inspector:

# Install and run (no setup required)npx @modelcontextprotocol/inspector miro-mcp-server
# With environment variablesMIRO_ACCESS_TOKEN=your-token npx @modelcontextprotocol/inspector miro-mcp-server

Open http://localhost:6274 to:

• Browse all 110 tools with their schemas
• Test tool calls interactively
• View raw JSON-RPC messages
• Debug parameter validation

See SETUP.md for more debugging options.

Supported Platforms

Supported AI Tools

See SETUP.md for configuration guides.

Account Compatibility

Four tools need an Enterprise plan and fail with a hint saying so: the three PDF/SVG export tools (miro_create_export_job, miro_get_export_job_status, miro_get_export_job_results) and miro_get_org_audit_logs, which additionally needs the auditlogs:read scope. miro_get_board_picture works on every plan. Everything else works on any plan.

The 6 code widget tools and 5 comment tools use Miro's v2-experimental API; availability may vary by account or plan, and the endpoints may change before GA.

Like This Project?

If this server saved you time, consider giving it a ⭐ on GitHub. It helps others discover the project.

More MCP Servers

Check out my other MCP servers:

License

MIT

Built for the Miro and MCP communities.
_{Miro is a trademark of Miro Inc. This project is not affiliated with or endorsed by Miro.}