Miro MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MIRO_ACCESS_TOKEN | Yes | Your MIRO access token generated from the MIRO Developer Portal with boards:read scopes. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_boardsB | List all MIRO boards accessible to the user |
| get_boardC | Get details about a specific MIRO board |
| get_board_itemsC | Get all items (widgets) from a MIRO board |
| get_board_framesC | Get all frames from a MIRO board |
| search_board_contentC | Search for text content across all items in a MIRO board |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap: list_boards enumerates boards, get_board retrieves board metadata, get_board_frames fetches frames, get_board_items fetches widgets, and search_board_content performs text searches. The descriptions specify unique targets (boards, frames, items, content), eliminating any ambiguity.
All tool names follow a consistent verb_noun pattern with snake_case, using verbs like 'get', 'list', and 'search' paired with specific nouns (e.g., board, board_frames, board_items). There are no deviations in style or convention, making the set predictable and readable.
With 5 tools, the server is well-scoped for interacting with MIRO boards, covering essential operations like listing, retrieving details, fetching components (frames/items), and searching content. Each tool earns its place without feeling excessive or insufficient for the domain.
The toolset provides strong read/search coverage for MIRO boards, including listing, metadata retrieval, and content exploration. However, there are minor gaps in write operations (e.g., creating/updating boards or items), which agents might need to work around for full CRUD functionality, though the read-focused scope is clear.