Miro MCP server

Miro × VS Code

Use the Miro MCP server
in VS Code

Read and create diagrams, notes, and frames on your Miro boards. This guide connects Miro to VS Code (GitHub Copilot's agent mode) through a governed gateway — one URL that also works in every other MCP client you use, with your rules and a full log attached.

Live-probed · Security-scanned · OAuth sign-in

Setup: Miro in VS Code

VS Code adds MCP servers via MCP server configuration. The gateway route takes about two minutes:

  1. Connect Miro to your free gate gateway from the verified directory.
  2. On your gate overview, click 'Add to VS Code' — VS Code prompts to add the gateway as an HTTP MCP server.
  3. Confirm and approve the sign-in.
  4. Copilot's agent mode can now use Miro — logged and governed through your gateway.

What to ask once it’s connected

Summarize the retro board from yesterday.
Create a diagram of this architecture on a new board.
Add these ideas as sticky notes to the brainstorm.
What did we map in the user-journey board?

Why route it through a gateway

One URL, every client

The same Miro connection works in Claude, Claude Code, ChatGPT, Cursor too — no per-client re-wiring.

Rules before regret

Allow, ask, or block every tool Miro exposes — reads can flow freely while writes require your approval.

Every call logged

A plain-language activity log of everything VS Code did with Miro — searchable, exportable, auditable.

Scanned and probed

Miro passed a live handshake probe and a security scan before listing — and drift detection watches it after you connect.

Also available: Miro in Claude · Miro in Claude Code · Miro in ChatGPT · Miro in Cursor