Miro

All of them, with a condition on Enterprise. Miro's MCP FAQ states the server is available across Miro plans, and its overview page says it works for all plans including free teams. Enterprise is the exception: the server is disabled by default there and an admin must enable it before anyone can connect. Miro's own REST-comparison page contradicts this by listing an Enterprise-only requirement, so verify against your own account.

Your admin has not enabled it. Miro's FAQ states that on Enterprise plans the MCP Server may be disabled by default, so a company admin must turn it on, and that requesting access through another tool such as a Claude connector will not work until they do. Admins enable it under Admin settings, then Apps and Integrations, then MCP, choosing either organization-wide or selected teams only.

No, and that is why you re-authenticate. Miro's FAQ states the MCP connection is 1:1, so each user is authenticated into one team at a time even across multiple clients. Authorizing a different team or a different client supersedes the previous connection. The fix is to re-authenticate while viewing a board in the team you want, which resets the connection to that environment.

You are authenticated into a different team than the board lives in. Miro's troubleshooting page calls this the last-one-wins rule: the 1:1 connection applies across all MCP clients, so authenticating into a new team or even a different client immediately drops the previous connection. Miro notes that if you authorize three clients, only the latest one will work. Re-authorize while viewing the target board.

Access is governed by your existing Miro permissions. Miro's FAQ states that authentication uses OAuth 2.1 with dynamic client registration, and that the AI agent can only see and act on boards the authenticated user can already access. Enabling MCP respects existing board-level access controls. The connector adds no new reach of its own, so it inherits whatever the authorizing user could already open.

Usually the board URL is missing from the prompt. Miro's FAQ says to check three things: that the board URL is included in your prompt, that you are authenticated into the same team where the board lives, and that you already have access to that board in Miro. Miro recommends including the full URL as a habit, which it calls prompt hygiene.

You have installed the server twice in one client. Miro's troubleshooting page explains that each installation method creates an independent connection with its own OAuth session, so a plugin plus a manual JSON config produces duplicate tools and authentication confusion. The rule is to use only one method per client: if your client has a Miro plugin, use it and remove the manual entry, then restart and re-authenticate once.

Further calls are blocked until the daily reset. Miro's usage page states that once you reach your daily allowance, further MCP tool calls are blocked until the limit resets at 00:00 UTC, and your agent receives an error telling you the daily limit is reached and prompting a plan upgrade. Every tool call counts toward the allowance whether or not it uses Miro AI Credits.

A curated subset of board objects, not the full API. Miro's FAQ states the MCP works with frames, sticky notes, shapes, text, cards, docs, tables, and images from public URLs, plus generated diagrams. Miro calls it a purposeful abstraction rather than a full mirror of the REST API, so some things behave differently or are not available yet, and the REST API may cover cases the MCP does not.