📘

Feedback form.

🔑 Authentication & Team Access

The most common issues with the Miro MCP server relate to how users are authenticated across multiple teams.

Why am I seeing a "Different Team" authorization error?

If you receive the following error message:

"This board belongs to a different team than your current authorization. To access this board, please re-authorize while viewing it."

❗️

The "Last One Wins" Rule: This 1:1 rule applies across all MCP Clients. If you authenticate into a new team or even a different MCP Client, the previous connection is immediately dropped.

• The Cause: Miro MCP maintains a 1:1 connection. Each individual user can only be "connected" or "authed" into one team at a time. This is true even if you auth with multiple MCP Clients. For example, if you auth into 3 clients, only the latest client connection will work!
• The Behavior: Once a user re-authenticates into another team, the connection from the previous team is lost. If the AI tries to access a board from a team that is no longer authenticated, it will trigger this error.
• The Fix: Simply re-authenticate while viewing a board in the desired team to reset the connection to that specific environment.

How to Solve "Board Access denied" error in VSCode

1. Go to bottom left corner, click on profile icon -> MCP (mcp.miro.com) -> Sign out (As shown below).

2. Follow the steps to re-add the Miro MCP Server to VSCode. Easiest way is by clicking install from the GitHub MCP Registry.
3. Re-run your prompt and you should see that the error is gone.

💻 Client Not Registered Error

If you see a "Client Not Registered" error with VSCode (or other MCP Clients) during auth, specifically this error:

How to Solve Client Not Registered Error Request

You will need to re-request a new Client ID from the MCP Server.

VSCode Client Not Registered Solution

For VSCode, you can run the following command

1. Go to command pallet by going to Code -> View -> Command Pallete (as shown below)

2. Use the following command: Authentication: Remove Dynamic Authentication Providers

3. That's it! Re-auth, and the issue should be fixed.

Cursor Client Not Registered Solution

For Cursor, you can run the following commands

1. Go to command pallet by going to Cursor -> View -> Command Pallete (as shown below)

2. Use the following command: Cursor: Clear all MCP Tokens

2. Re auth into Cursor by going into MCP Settings -> Connect.
3. You should see the Miro App Request from Cursor and click on Allow Access.

4. You will now go through the OAuth flow to select a team to install the MCP Server on within your Miro Organization.
5. That's it! You should see the tools are available in the Cursor MCP Settings.

🏢 Enterprise & Admin Setup

Is MCP available across all teams in an Enterprise account?

No. MCP must be enabled on a team-by-team basis.

• Admin Action: Enterprise admins can turn the feature on/off at the Org-level, but they must explicitly select the teams where it should be active. If you're on an Enterprise account, ensure your admin has turned it on - see guide here.
• User Access: If you cannot find the MCP in your sidebar, please contact your Admin to ensure your specific team has been enabled in the settings.

---

⚡ Quick Troubleshooting Guide

---

📘

Pro Tip: Team Switching

For more details on the installation and team selection flow, visit the MCP Documentation on Team Selection.