Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Miro to Claude Code

Make Claude build out frames, sticky notes, and flows in Miro. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Miro to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Miro, you add a Miro MCP server: a small hosted service that exposes Miro's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Miro account. No API keys pasted into config files.

claude mcp add --transport http miro https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Miro once connected?

Full read-write Miro access lets Claude build out a board for you: create frames and sticky notes, add shapes and text, draw connectors between items, tag and group elements, and rearrange a cluttered canvas. The structuring that used to mean dragging items by hand happens where the board already lives.

  • Create a frame and populate it with titled sticky notes from a brainstorm
  • Add shapes, text boxes, and connectors to draw out a process flow
  • Convert a list into a grid of color-coded sticky notes
  • Tag and group related items so a messy board reads clearly
  • Duplicate a template frame and fill it in for a new workshop
  • Update or move existing widgets to reorganize a board layout

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Miro access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Miro API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Miro changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Miro connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Miro connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Miro account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Miro's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Miro?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Miro account it signs in with. Revoking access is one click in Miro.

More on the Miro connector

Miro connector for claude.aiNotion + Claude CodeAsana + Claude CodeFigma + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us