What your AI apps can do with Miro
- Read board content
- Create diagrams and documents on boards
Miro MCP tools
30 tools, taken from the publisher's documentation on 29 October 2026. The server decides what it offers and can add or rename tools at any time; after you connect, Toolstile shows the current list.
| Tool | What it does |
|---|---|
board_search_boards | List or search boards you can access in your team |
canvas_read_as_svg | Read a board area or selected items as SVG |
canvas_search | Find and navigate board content |
board_show | Show an interactive preview of board items |
comment_list_comments | List comments on a board or item |
table_list_rows | Read table rows with column metadata |
image_get_data | Read an image item or get its download URL |
image_get_url | Read an image item or get its download URL |
prototype_read | Read prototype screens from a board |
user_who_am_i | Identify the signed-in user |
get_brand_context | Read the organization's brand theme and guidelines |
board_create | Create a new board |
board_create_format | Create a table, timeline, kanban, doc, diagram, slides or embed |
canvas_create_from_svg | Build board items from an SVG document |
canvas_update_from_svg | Apply changes to existing items on a board |
table_sync_rows | Add or update table rows |
comment_create | Post a comment or reply |
comment_reply | Post a comment or reply |
comment_resolve | Resolve or reopen a comment thread |
image_create | Place an image on a board |
prototype_create | Build a prototype from HTML screens |
board_update_metadata | Change a board's title, description or icon |
board_move | Move a board to a space, folder or another team |
board_move_to_team | Move a board to a space, folder or another team |
board_share | Give a user or group a role on a board or space |
space_share | Give a user or group a role on a board or space |
board_role_update | Change an existing member's role |
space_role_update | Change an existing member's role |
user_search_organization_users | Find people in the organization (returns names and emails) |
section_delete | Remove a section from a space |
Suggested access for each AI app
The documentation this list comes from doesn't mark Miro's tools as read-only or destructive. Read each tool's description and decide per app before allowing it.
Coding agent in Claude Code or Cursor. Allow the read tools so the agent can look things up without stopping, and require approval for tools that change shared data.
Chat or research app in Claude Desktop. Allow reading and searching. Allow writes only where you want the app to act for you.
Unattended agent, such as a scheduled Codex job. No one is watching the session, so keep it narrow: allow what the job needs, require approval for changes and block the rest.
Blocked tools are removed from the tool list an app sees, so it won't try them. Because rules apply per app, the same Miro connection can be broad in one app and read-only in another, and the credential stays in Toolstile instead of each app's config file.
How it works with Toolstile
- Connect once. Add Miro to a workspace (browser sign-in). Toolstile keeps the credential, so no agent config holds it.
- Choose access per app. Give Claude Code every Miro tool, give Cursor only the read tools, or keep Miro away from an app entirely.
- Share approved accounts. Teammates use the connection without copying tokens, and you can remove access in one place.
- Review activity. See which app called which tool and when, so you can tighten access with evidence.
Add the Miro MCP server to an AI app
Through Toolstile, every AI app uses one gateway entry, whichever servers you connect. In Claude Code:
claude mcp add --transport http toolstile 'https://toolstile.com/mcp'Then connect Miro in your workspace and choose which of its tools that app may use. Client setup covers Codex, Cursor and Claude Desktop.
To connect directly instead, add the Miro endpoint to each app separately. In Claude Code:
claude mcp add --transport http miro 'https://mcp.miro.com/'In Cursor's mcp.json:
{
"mcpServers": {
"miro": {
"url": "https://mcp.miro.com/"
}
}
}Some servers accept only clients they have approved, or need a token header. Check the Miro MCP documentation for what your client needs.
Before you connect
A Miro account. Sign-in uses your Miro permissions.
Server details
| Detail | Value |
|---|---|
| Publisher | Miro |
| Endpoint | https://mcp.miro.com/ |
| Authentication | Browser sign-in |
| Categories | Productivity |
| Tool list | 30 tools, observed 29 October 2026 (docs) |