Miro MCP Server (admin guide)

Who can do it: Company and team admins on Enterprise plans

As a company admin for an Enterprise subscription, you control whether Miro MCP Server is available to your organization. This setting determines whether your teams can use AI integrations that connect with Miro.

Use Miro MCP (Model Context Protocol) to connect your Miro boards to MCP‑compatible AI tools. When enabled and authorized, AI agents can read context from specific boards and (where allowed) take actions such as summarizing content or creating diagrams via a curated set of Miro MCP tools. This guide explains prerequisites, enablement, governance, and troubleshooting.

Before you begin

• Enable for the entire organization or only for selected teams (board‑level permissions still apply).

Enable or disable MCP Server

To enable MCP Server:

1. Go to Admin settings > Apps & Integrations > MCP.
2. Choose scope.
   1. Organization: Any user in your org may authorize MCP for boards they can already access.
   2. Selected team(s): Only users in those teams may authorize MCP. Board‑level permissions still apply.
3. Toggle on. Changes take effect immediately.

To temporarily halt usage, toggle Miro MCP off in the same location (halts new tool calls).

NOTE: If you don't see the MCP toggle, contact your account manager.

How access and permissions work

When you enable MCP, you allow:

• External AI agents to read board content when authorized by users.
• AI tools to create or modify content on Miro boards.
• Secure data exchange between Miro and third-party applications.

Important security considerations:

• All access is authenticated through OAuth 2.1.
• Users can only grant access to boards they have permission to view.
• Enterprise security compliance is maintained.
• Standard API rate limits apply to all operations.
• Users in your org will be able to authenticate to the MCP Server allowing external or third-party AI agents to read and create content on a board on their behalf.

Managing MCP in your organization

As an admin, you should consider:

1. Communication: Inform your teams about Miro MCP availability and use cases.
2. Training: Provide guidance on how to effectively use MCP with different AI tools.
3. Governance: Establish guidelines for appropriate use of AI-generated content.
4. Monitoring: Periodically review MCP usage and adjust settings as needed.

For more information on managing apps in your Miro environment, see the App management documentation.

Rollout guidance

• Start small: enable for one or two pilot teams (for example, engineering and product) and validate value/control.
• Reinforce prompt hygiene: require users to include a full board URL in every MCP prompt.

Control which MCP clients can connect to Miro

As Company admin, you can allow all clients to access Miro from your organization, or manage an allowlist of clients, including your own custom MCP clients.

Follow these steps:

1. In Admin Console, go to Apps and integrations > MCP. If you have not already enabled MCP, see Enable MCP.
2. Under Access control, All clients is the default setting. To modify, click All clients, then click Specific clients.
   The Specific MCP clients panel opens.
3. Toggle on which clients you want to allow. To allow a custom MCP client, input the name of your client in the search bar (top), then click Add. For more information, see Miro MCP developer documentation.
4. Click Save.
   The panel closes, and your specified clients show in a row under Access Control.

TIP: To disallow any client, return to Apps and integrations > MCP > All clients (under Access Control) and toggle the client off. 

NOTE: If you add a custom MCP client and then later disallow it, the client is removed from the list. To re-allow, you must re-add the client. See step 3 in Control which MCP clients can connect to Miro. 

Troubleshooting

• “I can’t see Miro MCP tools in my client”
  • Confirm MCP is enabled for the org or intended team, and the user belongs to that team.
  • Re‑run the OAuth flow and select a team with MCP enabled.
  • Verify the client supports MCP and is among the clients we’re targeting/documenting.
• “Access denied when prompting”
  • Ensure the prompt includes a full board URL; agents won’t auto‑discover boards.
  • Confirm the user already has access to that board in Miro.
• “We need to pause usage now”
  • Toggle MCP off in Admin settings > Apps & Integrations > Miro MCP.
• "A user's client is blocked / returns an access error"
  • Confirm the client is toggled on under Access control, or add it as a custom client.