Miro Automation via Rube MCP
Automate Miro whiteboard operations through Composio's Miro toolkit via Rube MCP.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Miro connection via
RUBE_MANAGE_CONNECTIONS with toolkit miro
- Always call
RUBE_SEARCH_TOOLS first to get current tool schemas
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLS responds
- Call
RUBE_MANAGE_CONNECTIONS with toolkit miro
- If connection is not ACTIVE, follow the returned auth link to complete Miro OAuth
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. List and Browse Boards
When to use: User wants to find boards or get board details
Tool sequence:
MIRO_GET_BOARDS2 - List all accessible boards [Required]
MIRO_GET_BOARD - Get detailed info for a specific board [Optional]
Key parameters:
query: Search term to filter boards by name
sort: Sort by 'default', 'last_modified', 'last_opened', 'last_created', 'alphabetically'
limit: Number of results per page (max 50)
offset: Pagination offset
board_id: Specific board ID for detailed retrieval
Pitfalls:
- Pagination uses offset-based approach, not cursor-based
- Maximum 50 boards per page; iterate with offset for full list
- Board IDs are long alphanumeric strings; always resolve by search first
2. Create Boards and Items
When to use: User wants to create a new board or add items to an existing board
Tool sequence:
MIRO_CREATE_BOARD - Create a new empty board [Optional]
MIRO_CREATE_STICKY_NOTE_ITEM - Add sticky notes to a board [Optional]
MIRO_CREATE_FRAME_ITEM2 - Add frames to organize content [Optional]
MIRO_CREATE_ITEMS_IN_BULK - Add multiple items at once [Optional]
Key parameters:
name / description: Board name and description (for CREATE_BOARD)
board_id: Target board ID (required for all item creation)
data: Content object with content field for sticky note text
style: Styling object with fillColor for sticky note color
position: Object with x and y coordinates
geometry: Object with width and height
Pitfalls:
board_id is required for ALL item operations; resolve via GET_BOARDS2 first
- Sticky note colors use hex codes (e.g., '#FF0000') in the
fillColor field
- Position coordinates use the board's coordinate system (origin at center)
- BULK create has a maximum items-per-request limit; check current schema
- Frame items require
geometry with both width and height
3. Browse and Manage Board Items
When to use: User wants to view, find, or organize items on a board
Tool sequence:
MIRO_GET_BOARD_ITEMS - List all items on a board [Required]
MIRO_GET_CONNECTORS2 - List connections between items [Optional]
Key parameters:
board_id: Target board ID (required)
type: Filter by item type ('sticky_note', 'shape', 'text', 'frame', 'image', 'card')
limit: Number of items per page
cursor: Pagination cursor from previous response
Pitfalls:
- Results are paginated; follow
cursor until absent for complete item list
- Item types must match Miro's predefined types exactly
- Large boards may have thousands of items; use type filtering to narrow results
- Connectors are separate from items; use GET_CONNECTORS2 for relationship data
4. Share and Collaborate on Boards
When to use: User wants to share a board with team members or manage access
Tool sequence:
MIRO_GET_BOARDS2 - Find the board to share [Prerequisite]
MIRO_SHARE_BOARD - Share the board with users [Required]
MIRO_GET_BOARD_MEMBERS - Verify current board members [Optional]
Key parameters:
board_id: Board to share (required)
emails: Array of email addresses to invite
role: Access level ('viewer', 'commenter', 'editor')
message: Optional invitation message
Pitfalls:
- Email addresses must be valid; invalid emails cause the entire request to fail
- Role must be one of the predefined values; case-sensitive
- Sharing with users outside the organization may require admin approval
- GET_BOARD_MEMBERS returns all members including the owner
5. Create Visual Connections
When to use: User wants to connect items on a board with lines or arrows
Tool sequence:
MIRO_GET_BOARD_ITEMS - Find items to connect [Prerequisite]
MIRO_GET_CONNECTORS2 - View existing connections [Optional]
Key parameters:
board_id: Target board ID
startItem: Object with id of the source item
endItem: Object with id of the target item
style: Connector style (line type, color, arrows)
Pitfalls:
- Both start and end items must exist on the same board
- Item IDs are required for connections; resolve via GET_BOARD_ITEMS first
- Connector styles vary; check available options in schema
- Self-referencing connections (same start and end) are not allowed
Common Patterns
ID Resolution
Board name -> Board ID:
1. Call MIRO_GET_BOARDS2 with query=board_name
2. Find board by name in results
3. Extract id field
Item lookup on board:
1. Call MIRO_GET_BOARD_ITEMS with board_id and optional type filter
2. Find item by content or position
3. Extract item id for further operations
Pagination
- Boards: Use
offset and limit (offset-based)
- Board items: Use
cursor and limit (cursor-based)
- Continue until no more results or cursor is absent
- Default page sizes vary by endpoint
Coordinate System
- Board origin (0,0) is at the center
- Positive X is right, positive Y is down
- Items positioned by their center point
- Use
position: {x: 0, y: 0} for center of board
- Frames define bounded areas; items inside inherit frame position
Known Pitfalls
Board IDs:
- Board IDs are required for virtually all operations
- Always resolve board names to IDs via GET_BOARDS2 first
- Do not hardcode board IDs; they vary by account
Item Creation:
- Each item type has different required fields
- Sticky notes need
data.content for text
- Frames need
geometry.width and geometry.height
- Position defaults to (0,0) if not specified; items may overlap
Rate Limits:
- Miro API has rate limits per token
- Bulk operations preferred over individual item creation
- Use MIRO_CREATE_ITEMS_IN_BULK for multiple items
Response Parsing:
- Response data may be nested under
data key
- Item types determine which fields are present in response
- Parse defensively; optional fields may be absent
Quick Reference
| Task |
Tool Slug |
Key Params |
| List boards |
MIRO_GET_BOARDS2 |
query, sort, limit, offset |
| Get board details |
MIRO_GET_BOARD |
board_id |
| Create board |
MIRO_CREATE_BOARD |
name, description |
| Add sticky note |
MIRO_CREATE_STICKY_NOTE_ITEM |
board_id, data, style, position |
| Add frame |
MIRO_CREATE_FRAME_ITEM2 |
board_id, data, geometry, position |
| Bulk add items |
MIRO_CREATE_ITEMS_IN_BULK |
board_id, items |
| Get board items |
MIRO_GET_BOARD_ITEMS |
board_id, type, cursor |
| Share board |
MIRO_SHARE_BOARD |
board_id, emails, role |
| Get members |
MIRO_GET_BOARD_MEMBERS |
board_id |
| Get connectors |
MIRO_GET_CONNECTORS2 |
board_id |
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
1---2name: miro-automation3description: "Automate Miro tasks via Rube MCP (Composio): boards, items, sticky notes, frames, sharing, connectors. Always search tools first for current schemas."4requires:5 mcp: [rube]6risk: unknown7source: community8metadata:9 source: https://skillmd.com/skills/mayurrathi/miro-automation10---1112# Miro Automation via Rube MCP1314Automate Miro whiteboard operations through Composio's Miro toolkit via Rube MCP.1516## Prerequisites1718- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)19- Active Miro connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `miro`20- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas2122## Setup2324**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.2526271. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds282. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `miro`293. If connection is not ACTIVE, follow the returned auth link to complete Miro OAuth304. Confirm connection status shows ACTIVE before running any workflows3132## Core Workflows3334### 1. List and Browse Boards3536**When to use**: User wants to find boards or get board details3738**Tool sequence**:391. `MIRO_GET_BOARDS2` - List all accessible boards [Required]402. `MIRO_GET_BOARD` - Get detailed info for a specific board [Optional]4142**Key parameters**:43- `query`: Search term to filter boards by name44- `sort`: Sort by 'default', 'last_modified', 'last_opened', 'last_created', 'alphabetically'45- `limit`: Number of results per page (max 50)46- `offset`: Pagination offset47- `board_id`: Specific board ID for detailed retrieval4849**Pitfalls**:50- Pagination uses offset-based approach, not cursor-based51- Maximum 50 boards per page; iterate with offset for full list52- Board IDs are long alphanumeric strings; always resolve by search first5354### 2. Create Boards and Items5556**When to use**: User wants to create a new board or add items to an existing board5758**Tool sequence**:591. `MIRO_CREATE_BOARD` - Create a new empty board [Optional]602. `MIRO_CREATE_STICKY_NOTE_ITEM` - Add sticky notes to a board [Optional]613. `MIRO_CREATE_FRAME_ITEM2` - Add frames to organize content [Optional]624. `MIRO_CREATE_ITEMS_IN_BULK` - Add multiple items at once [Optional]6364**Key parameters**:65- `name` / `description`: Board name and description (for CREATE_BOARD)66- `board_id`: Target board ID (required for all item creation)67- `data`: Content object with `content` field for sticky note text68- `style`: Styling object with `fillColor` for sticky note color69- `position`: Object with `x` and `y` coordinates70- `geometry`: Object with `width` and `height`7172**Pitfalls**:73- `board_id` is required for ALL item operations; resolve via GET_BOARDS2 first74- Sticky note colors use hex codes (e.g., '#FF0000') in the `fillColor` field75- Position coordinates use the board's coordinate system (origin at center)76- BULK create has a maximum items-per-request limit; check current schema77- Frame items require `geometry` with both width and height7879### 3. Browse and Manage Board Items8081**When to use**: User wants to view, find, or organize items on a board8283**Tool sequence**:841. `MIRO_GET_BOARD_ITEMS` - List all items on a board [Required]852. `MIRO_GET_CONNECTORS2` - List connections between items [Optional]8687**Key parameters**:88- `board_id`: Target board ID (required)89- `type`: Filter by item type ('sticky_note', 'shape', 'text', 'frame', 'image', 'card')90- `limit`: Number of items per page91- `cursor`: Pagination cursor from previous response9293**Pitfalls**:94- Results are paginated; follow `cursor` until absent for complete item list95- Item types must match Miro's predefined types exactly96- Large boards may have thousands of items; use type filtering to narrow results97- Connectors are separate from items; use GET_CONNECTORS2 for relationship data9899### 4. Share and Collaborate on Boards100101**When to use**: User wants to share a board with team members or manage access102103**Tool sequence**:1041. `MIRO_GET_BOARDS2` - Find the board to share [Prerequisite]1052. `MIRO_SHARE_BOARD` - Share the board with users [Required]1063. `MIRO_GET_BOARD_MEMBERS` - Verify current board members [Optional]107108**Key parameters**:109- `board_id`: Board to share (required)110- `emails`: Array of email addresses to invite111- `role`: Access level ('viewer', 'commenter', 'editor')112- `message`: Optional invitation message113114**Pitfalls**:115- Email addresses must be valid; invalid emails cause the entire request to fail116- Role must be one of the predefined values; case-sensitive117- Sharing with users outside the organization may require admin approval118- GET_BOARD_MEMBERS returns all members including the owner119120### 5. Create Visual Connections121122**When to use**: User wants to connect items on a board with lines or arrows123124**Tool sequence**:1251. `MIRO_GET_BOARD_ITEMS` - Find items to connect [Prerequisite]1262. `MIRO_GET_CONNECTORS2` - View existing connections [Optional]127128**Key parameters**:129- `board_id`: Target board ID130- `startItem`: Object with `id` of the source item131- `endItem`: Object with `id` of the target item132- `style`: Connector style (line type, color, arrows)133134**Pitfalls**:135- Both start and end items must exist on the same board136- Item IDs are required for connections; resolve via GET_BOARD_ITEMS first137- Connector styles vary; check available options in schema138- Self-referencing connections (same start and end) are not allowed139140## Common Patterns141142### ID Resolution143144**Board name -> Board ID**:145```1461. Call MIRO_GET_BOARDS2 with query=board_name1472. Find board by name in results1483. Extract id field149```150151**Item lookup on board**:152```1531. Call MIRO_GET_BOARD_ITEMS with board_id and optional type filter1542. Find item by content or position1553. Extract item id for further operations156```157158### Pagination159160- Boards: Use `offset` and `limit` (offset-based)161- Board items: Use `cursor` and `limit` (cursor-based)162- Continue until no more results or cursor is absent163- Default page sizes vary by endpoint164165### Coordinate System166167- Board origin (0,0) is at the center168- Positive X is right, positive Y is down169- Items positioned by their center point170- Use `position: {x: 0, y: 0}` for center of board171- Frames define bounded areas; items inside inherit frame position172173## Known Pitfalls174175**Board IDs**:176- Board IDs are required for virtually all operations177- Always resolve board names to IDs via GET_BOARDS2 first178- Do not hardcode board IDs; they vary by account179180**Item Creation**:181- Each item type has different required fields182- Sticky notes need `data.content` for text183- Frames need `geometry.width` and `geometry.height`184- Position defaults to (0,0) if not specified; items may overlap185186**Rate Limits**:187- Miro API has rate limits per token188- Bulk operations preferred over individual item creation189- Use MIRO_CREATE_ITEMS_IN_BULK for multiple items190191**Response Parsing**:192- Response data may be nested under `data` key193- Item types determine which fields are present in response194- Parse defensively; optional fields may be absent195196## Quick Reference197198| Task | Tool Slug | Key Params |199|------|-----------|------------|200| List boards | MIRO_GET_BOARDS2 | query, sort, limit, offset |201| Get board details | MIRO_GET_BOARD | board_id |202| Create board | MIRO_CREATE_BOARD | name, description |203| Add sticky note | MIRO_CREATE_STICKY_NOTE_ITEM | board_id, data, style, position |204| Add frame | MIRO_CREATE_FRAME_ITEM2 | board_id, data, geometry, position |205| Bulk add items | MIRO_CREATE_ITEMS_IN_BULK | board_id, items |206| Get board items | MIRO_GET_BOARD_ITEMS | board_id, type, cursor |207| Share board | MIRO_SHARE_BOARD | board_id, emails, role |208| Get members | MIRO_GET_BOARD_MEMBERS | board_id |209| Get connectors | MIRO_GET_CONNECTORS2 | board_id |210211## When to Use212This skill is applicable to execute the workflow or actions described in the overview.