The Miro connector.
Boards, sticky notes and members. Connect once with your own key. Every agent your team runs reads the same 5 tools under one permission model.
How access is governed
5
Read tools
Open by default. They run when called, and every call is logged with the endpoint, tool and capability.
0
Write tools
Miro exposes no write tools. Nothing it does mutates external state.
0
Destructive tools
Miro defines no destructive tools. Nothing here deletes data.
Defaults come from the capability on each tool definition, and an admin can tighten or open any tool individually. The endpoint's capability ceiling can only tighten that policy. An endpoint scoped to read never surfaces a write tool.
Every Miro tool
5 tools, named as the agent sees them.
- list_boardsread
List Miro boards the token can access. Start here — the `id` of a board is what every other Miro tool takes.
- get_boardread
Get one board with its team, owner, sharing policy and timestamps. Takes `board_id` from list_boards.
- list_board_itemsread
Read the content of a board — sticky notes, text, shapes, cards and frames. This is the tool that actually tells you what is ON a board. Filter with `type` (e.g. sticky_note) to read just one kind. Paginate with the returned `cursor`.
- get_itemread
Get one board item in full, including its geometry. Takes `board_id` from list_boards and `item_id` from list_board_items.
- list_board_membersread
List who has access to a board and at what role. Use to find out who owns or can edit a board before asking about it.
Use it from any agent
The same Miro tools reach Claude Code, Cursor, Claude Desktop or your own agent through one MCP endpoint. The endpoint is scoped to a group, the token is issued per group and revocable from the dashboard, and an allowed-tool list and capability ceiling limit what it exposes. Reads run. Gated writes refuse unless an admin opens them. Destructive tools remain unavailable over MCP.
{
"mcpServers": {
"growth": {
"type": "http",
"url": "https://app.notara.ai/mcp/g/acme/growth",
"headers": {
"Authorization": "Bearer ntr_mcp_xxxxxxxxxxxxxxxxxxxx"
}
}
}
}The URL and token are placeholders. Real endpoints are issued per group from the dashboard.
Setup
- 01
Create a Miro Access Token in your Miro account (where to find it). The key is yours: Notara stores it encrypted and never sees a bill.
- 02
Paste it into the Notara dashboard. Credentials can be scoped to the workspace or to one person.
- 03
The tools appear with their capability defaults already set. Tighten or open any of them per tool, then invite the agent to a channel or issue an MCP token.
Connect Miro once. Use it everywhere.
Use Notara directly, or bring us the workflow that needs to be redesigned and built.