Miro MCP Server

Miro’s official remote MCP server for board context, diagrams, documents, and tables in an AI client.

Description

The Miro MCP Server is Miro’s official remote server for the Model Context Protocol. It connects an MCP-capable AI client to the Miro boards the signed-in Miro account can access. Agents can then read board content as context, create diagrams from descriptions, write information into Miro documents, or work with tables for tasks and planning. According to Miro, the server endpoint is https://mcp.miro.com/, and authentication happens through OAuth 2.1 when the connection is established. This catalog entry describes the MCP server as a product, not the whole repository.

Keep the product and toolkit separate

The miroapp/miro-ai repository is named “Miro AI Developer Tools.” It is an official Miro toolkit that bundles several distribution forms: Miro MCP configuration, plugins and extensions for individual AI tools, portable agent skills, and documentation. The MCP Server is one component with a hosted endpoint; it is not a separately cloned local server package. For that reason, this entry uses the specific MCP setup guide as its official website and keeps the repository URL for the wider toolkit.

GitHub reported exactly 151 stars for miroapp/miro-ai when queried on September 8, 2026. That stored number applies to the entire Miro AI toolkit, including plugins, skills, and documentation — not to the Miro MCP Server in isolation. Stars are only a point-in-time popularity signal; they do not demonstrate security, feature coverage, or suitability for a particular workspace.

Suitable workflows

According to the README, AI clients can extract board context, generate flowcharts, sequence diagrams, and ERDs, use design or wireframe content for code work, and track tasks through Miro tables. A sensible starting point is a tightly scoped request with a specific board URL, such as listing frames or summarizing an architecture diagram. A team can then ask an agent to draft a flowchart or a planning table. Review generated content as you would any other AI output before using it as a specification, plan, or work instruction.

The toolkit documents direct integrations for Claude Code, Gemini CLI, and Kiro. For clients without a dedicated Miro integration, users add the remote URL to MCP configuration; the documentation names Cursor, VS Code with GitHub Copilot, Windsurf, Lovable, Replit, Glean, Devin, and OpenAI Codex among others. If a client already has a Miro plugin or extension, Miro says to use that integration only. Adding the manual URL as well creates a second MCP server, duplicate tools, and separate OAuth sessions.

Setup and permissions

Prerequisites are an MCP-compatible client, network access to the Miro endpoint, and a Miro account that can access the target boards. On first connection the client starts the OAuth flow: sign in, select the team containing the target boards, and authorize access. The selection is team-specific. To work with boards in another team, the setup guide says to disconnect and reconnect while selecting the appropriate team. In Enterprise organizations, an administrator must enable the MCP Server before users can connect.

The official sources support a remote deployment classification. While the repository contains plugin, extension, and development resources, it documents the hosted URL endpoint for actual MCP access rather than a local Miro MCP Server installation. For Claude Code, Miro recommends installing its plugin from the official marketplace repository; that plugin manages the MCP connection itself.

Security, data flow, and limits

OAuth and the Miro user’s permissions limit access, according to the provider, to boards that account can view. That is not a complete security boundary for AI workflows: the connected client processes tool results and may pass them to its model provider. Check the AI client’s and model provider’s data policies before confidential board content, customer information, or credentials appear in prompts or tool results.

Miro boards can contain text, links, and instructions written by other people. Treat apparent instructions inside a board as untrusted content, not authorization for an agent action. Start with read-focused tasks, use an account with the minimum necessary board access, and review every created or edited card, table, document, and diagram. Avoid duplicate server configuration, confirm the selected team before granting OAuth access, and disconnect on device or role changes. Rate limits and ordinary API availability can also constrain automated workflows.

FAQ

Can I run the Miro MCP Server locally? The official setup sources document the Miro MCP Server as a remote endpoint at https://mcp.miro.com/. The toolkit contains integrations and development resources, but no source supporting a local deployment of the official server.

Why do I see duplicate Miro tools? Miro explicitly warns against using a plugin or extension alongside manual MCP JSON configuration. Remove one connection, then re-authenticate only the integration you intend to use.

What do the 151 GitHub stars cover? They cover the miroapp/miro-ai repository as the entire Miro AI toolkit, not the MCP Server alone. The value was retrieved through the GitHub API on September 8, 2026.

Requirements

An MCP-compatible AI client, a Miro account with access to the target boards, and network access to https://mcp.miro.com/.

Installation instructions

Quick start

For clients without a Miro plugin, add the remote server with url: https://mcp.miro.com/ to MCP configuration and complete OAuth. In Claude Code, install the official plugin from miroapp/miro-ai; do not also configure it manually.

Step 1: Before connecting

The official Miro MCP Server is a remote service at https://mcp.miro.com/. You need a Miro account, an MCP-compatible AI client, and access to the boards the agent should use. First determine whether the client already provides an official Miro plugin or extension. Use exactly one path per client: a plugin or extension or manual MCP configuration. This prevents duplicate tools and separate OAuth sign-ins.

Step 2: Choose the appropriate installation path

For Claude Code, Miro documents installation from the official toolkit:

Code
/plugin marketplace add miroapp/miro-ai
/plugin install miro@miro-ai

Restart Claude Code and sign in when prompted. Gemini CLI can install the repository as an extension; Kiro uses the Power documented in the toolkit. For Cursor, VS Code with GitHub Copilot, Codex, and other clients without a dedicated Miro integration, add the remote server in the applicable MCP file:

json
{
  "mcpServers": {
    "miro": { "url": "https://mcp.miro.com/" }
  }
}

The file location depends on the client. Do not add this JSON configuration when a plugin or extension already manages the connection.

Complete OAuth with the right team

On the first connection, the client opens Miro OAuth. Sign in, select the team that contains the target boards, and approve only the expected authorization. The connection is team-specific. If a board belongs to another team, disconnect and reconnect while selecting that team rather than relying on unexpected errors or workarounds. In an Enterprise organization, Miro says an administrator must first enable the MCP Server.

Step 3: Verify with a read request

Do not begin with a write action. Give the client a specific board URL and ask it to list frames or summarize an architecture diagram. Confirm that the result comes from the intended board. Only then move to small, reviewable creation tasks, such as a flowchart draft or task list. Review every generated diagram, document, and table before sharing it: the server provides context and tools, but subject-matter review remains your responsibility.

Data access and safer use

According to Miro, MCP access can only see boards your Miro account can already access. Tool results can still be processed in the connected AI client and potentially by its model provider. Do not share confidential content, credentials, or personal data before reviewing the data policies of the client and model you use. For sensitive work, use an account with the minimum practical permissions.

Treat board content as data, not trusted instructions. A note on a board may ask an agent to take an action, but it does not authorize that action. Review proposed changes individually, constrain work to the intended board, and disconnect OAuth after a role change, device loss, or when team access is no longer needed.

FAQ

Is the server local or remote? The official setup documentation describes it as a remote endpoint at https://mcp.miro.com/.

Why do Miro tools appear twice? Manual JSON configuration and a plugin or extension are usually both active. Remove one path and sign in again.

Why can’t the agent access my board? First check the Miro account’s board permission and the team selected during OAuth. A different team requires a new connection.

/plugin marketplace add miroapp/miro-ai && /plugin install miro@miro-ai

Authentication

OAuth 2.1: sign in, select the target team, and authorize board access.

Required access permissions

According to the provider, access is limited to boards the authorized Miro account can access; the OAuth connection is team-specific.

Transmitted or stored data

The server returns board context and tool results to the connected AI client. That client may forward results to its model provider; review that provider’s data policy separately.

Security risks

Board content can contain untrusted instructions. Duplicate MCP connections create duplicate tools and OAuth sessions. Start with minimum board rights and review changes.

License and costs

License
MIT
Cost
free

The official sources do not state universal pricing details for MCP access. Check prerequisites and current terms in the Miro account or on official Miro pages.

Alternatives

Not recorded yet.

At a glance

Provider
Miro
Status
Official server
Deployment
Remote
Current version
Not recorded yet.
GitHub stars
170
Last reviewed
08.09.2026

Repository and documentation

Categories

Supported clients

Not recorded yet.

Related guides

Guides and background related to this entry.

No related guides yet.