Miro MCP integration for AI agents.
Connect AI agents to Miro through 7 structured actions, including get board, create board, and create sticky note. Review authentication, inputs, workflows…
- ACTION CONTRACTS
- 7
- AUTHENTICATION
- OAuth 2.0
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Miro integration exposes
The Miro Agent App exposes 7 provider-backed actions for design and productivity work. Its current contract lets an authorized agent get one miro board by id, create a miro board with optional team, project, and sharing policy settings, and create a sticky note on a miro board with optional style, position, geometry, and parent frame. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses OAuth 2.0. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Miro account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Miro capabilities.
Showing 7 of 7 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_boardREADGet one Miro board by ID.
INPUTS: boardId
create_boardWRITECreate a Miro board with optional team, project, and sharing policy settings.
INPUTS: name / description / teamId / projectId / policy
create_sticky_noteWRITECreate a sticky note on a Miro board with optional style, position, geometry, and parent frame.
INPUTS: boardId / data / style / position / geometry
create_textWRITECreate a text item on a Miro board with optional style, position, geometry, and parent frame.
INPUTS: boardId / data / style / position / geometry
get_itemREADGet one item from a Miro board.
INPUTS: boardId / itemId
list_boardsREADList Miro boards visible to the connected user with optional team, project, owner, or text filters.
INPUTS: teamId / projectId / query / owner / limit
list_itemsREADList items on a Miro board with cursor pagination and an optional item-type filter.
INPUTS: boardId / limit / cursor / type
INPUT CONTRACTS
Know what the action needs before it runs.
get_board
boardIdOPTIONAL- Unique identifier of the Miro board.
create_board
nameREQUIRED- Board name.
descriptionOPTIONAL- Board description.
teamIdOPTIONAL- Team where the board will be created.
projectIdOPTIONAL- Project or space where the board will be created.
policyOPTIONAL- Provider-native Miro board policy object.
create_sticky_note
boardIdREQUIRED- Unique identifier of the Miro board.
dataREQUIRED- Miro sticky note data.
styleOPTIONAL- Provider-native Miro item style fields.
positionOPTIONAL- Position of the item on the board.
geometryOPTIONAL- Geometry of the Miro sticky note.
create_text
boardIdREQUIRED- Unique identifier of the Miro board.
dataREQUIRED- Miro item data.
styleOPTIONAL- Provider-native Miro item style fields.
positionOPTIONAL- Position of the item on the board.
geometryOPTIONAL- Geometry of the Miro text item. Miro calculates text height from its content and width.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Board
Get one Miro board by ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_boardControl Create Board
Create a Miro board with optional team, project, and sharing policy settings. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_boardVerify with Get Item
Get one item from a Miro board. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_itemSAFETY BOUNDARY
Operate Miro with explicit limits
- Authorize Miro with OAuth 2.0 and grant only the provider access required by the selected actions.
- 3 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- The sampled contract declares provider scopes including `boards:write` and `boards:read`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the Miro task completed successfully.
CONNECTION MODEL
OAuth 2.0
Miro uses OAuth 2.0. Connection requirements and availability are determined by the provider and the Working Machines deployment.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 4
- WRITE SIGNALS
- 3
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Miro.