Miro MCP App

An independent, hosted Model Context Protocol server for Miro with an interactive MCP App workspace. It exposes the 31 tools in Miro's public MCP documentation while using only public Miro APIs.

Highlights

• Streamable HTTP MCP endpoint at /mcp

• OAuth 2.1, dynamic client registration, PKCE, and Miro OAuth brokering

• Board search, reading, layouts, diagrams, images, and experimental code widgets

• App-managed document, table, and prototype fallbacks

• Interactive board search, mini-canvas, inspector, and Miro deep links

• Explicit compatibility metadata for every result

See docs/parity.md for native, emulated, and unavailable capabilities.

Related MCP server: miro-mcp-server

Requirements

• Node.js 20 or newer

• pnpm 10

• A Miro developer app with expiring tokens

• Public HTTPS hosting for the OAuth callback

Configure the Miro app with:

• Scopes: boards:read, boards:write, identity:read

• Redirect URI: https://YOUR_HOST/oauth/miro/callback

• Expiring access tokens enabled

Configuration

Copy .env.example and set:

MIRO_ACCESS_TOKEN mode is intentionally not user-isolated. Do not use it on a shared deployment.

Run

pnpm build
pnpm start

Connect a client to:

https://YOUR_HOST/mcp

The client discovers authorization through RFC 9728 and dynamically registers itself. The user is then redirected through Miro consent.

For local development with a Miro test token:

MIRO_ACCESS_TOKEN=... MIRO_TEAM_ID=... pnpm dev

HTTP endpoints

MCP App

The 31 Miro tools return data without opening UI cards. One additional render_miro_board tool attaches ui://miro/workspace and opens a single full-size Miro Live Embed obtained from Miro's official oEmbed endpoint. Changes made by subsequent tools appear live inside Miro's own canvas:

• No reconstructed board items

• No app sidebars, inspector, or polling

• Native Miro zooming, navigation, and live updates

The View receives only Miro's validated live-embed URL; it never receives Miro or MCP access tokens.

Verification

pnpm check
pnpm verify

The verification harness checks all 31 parity tools plus the dedicated render tool, prompts, the MCP App resource, DSL discovery, and upload URL issuance without making Miro API calls.

Deployment note

OAuth clients, grants, app-managed artifacts, and uploads currently use process-local stores. This is suitable for local development and a single non-restarting evaluation instance. Before production or horizontal scaling, replace OAuthStore, ArtifactStore, and UploadStore with durable encrypted PostgreSQL/object-storage adapters.