Miro MCP: connect Miro to Claude and ChatGPT

Ask Claude or ChatGPT what last week’s workshop decided, which themes the sticky notes fall into or what is on the roadmap board for next quarter. The answer comes straight from Miro, without zooming around a board that somebody else built.

We build the connector for your company on Miro’s own REST API. Each person signs in with their own Miro account, so the AI reaches the boards that person reaches, and it only reads.

Built for your company · Works in Claude, ChatGPT and Copilot

In practice

What your team can do with Miro in Claude and ChatGPT

Workshop facilitators

From sticky notes to a summary

Every note on the board read, grouped by theme and written up as decisions, open questions and next steps while people still remember the session.
Product

What did we say about this?

The notes from discovery sessions, retrospectives and customer journey boards searched for a feature or a problem, with the board each one came from.
Project leads

The plan without opening the board

What sits in each frame of a planning board, who owns which card and what is marked as blocked, as a status you can paste into an update.
Management

Catch up on a session you missed

A strategy or planning board turned into a one-page read: what was discussed, what was agreed and what was left open.
Examples

Ask it like this

  • “Summarise the Q3 Planning Workshop board: what was decided and what is still open?”

  • “Group the sticky notes on the Customer Feedback board into themes and count each one.”

  • “What is in the Next Quarter frame on the product roadmap board?”

  • “Which boards did I change last week?”

  • “Find the retrospective notes that mention onboarding, across our team’s boards.”

  • “Write a follow-up to the participants of the Bristol kickoff from what is on the board. I will send it myself.”

The connector

What we build for Miro

Deployed OS has no ready Miro connector yet. We build it for your company when you start, on Miro’s own API, with the same rules as every other connector: each person’s own login, access decided by group, every call logged.

Boards
The boards each person reaches, with name, description, owner and when they were last changed.
Sticky notes and text
What each note and text box says, with its colour and tags, so notes can be grouped and counted.
Frames and structure
Which frame each item sits in, so a big board can be read section by section the way it was laid out.
Cards and shapes
Cards with their titles, descriptions, owners and dates, and the text inside shapes and diagrams.
Board members
Who has access to a board and in what role.
Security

Who sees what

Read-only
The connector reads. It does not add, move or delete anything on a board. We only build write actions if you ask for them.
Each person’s own Miro account
Everyone signs in to Miro as themselves and approves reading boards only. The AI reaches the boards that person can open in your Miro team, so a private board stays private.
Your company decides who gets it
Admins choose which groups get Miro in Deployed OS. A group without access never sees the connector.
Every call logged
Who asked, what was read and when. Deployed OS keeps the log, and it can be exported.
Setup

Set up the Miro connector in three steps

01
We go through with you which questions matter most, such as how your workshop and planning boards are laid out, and build the connector on Miro’s REST API.
02
Your Miro admin approves the connection for your team, and you choose which groups get Miro in Deployed OS.
03
Each person connects with their own Miro account. From then on they just ask.
Compared

Miro’s own MCP server or Deployed OS?

Miro has its own MCP Server, which Miro hosts. You sign in with your Miro account, it works within the team you choose and the boards you may open, and on Enterprise plans an admin switches it on first. If Miro is the only system you want in your AI tool, it is a good place to start.

Deployed OS is for when Miro is one system among several. Our connector reads by default and sits next to your project tool, files and chat in one company connection, so a workshop summary can be checked against the plan it was meant to change. Admins decide which groups get each system, every call is logged in one place, the same rules apply in Claude and ChatGPT, and the tools are built around how your boards are laid out.

Their documentation: Miro’s MCP Server

Questions

Miro MCP: common questions

Yes. Miro offers its own hosted MCP Server, which follows the team you sign in to and your board permissions. Deployed OS adds Miro to one company connection with your other systems, read-only by default, with access per group, one log and tools built for your company.

No. The connector reads boards and what is on them. It does not add, move or delete anything, and we only build write actions if you ask for them.

Yes. Everyone signs in with their own Miro account, and Miro only returns the boards that person can open. The AI cannot reach more than the person could in Miro.

Yes. The connector reads a board frame by frame, so a board with hundreds of notes is summarised section by section instead of as one long list.

Deployed is an EU company and fully GDPR compliant, and you choose where your data is stored, down to the city. Miro data is fetched when someone asks for it.

It depends on the size of your team. Get in touch and we will walk you through it.

More connectorsAll connectors
Let’s talk

See it on your own tools.

Tell us which systems your company runs on. We’ll show you what your team can ask, and what IT gets to control.