MiroBridgeMCP
Related Servers
Alternatives to MiroBridgeMCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables MCP clients to read design structure, take screenshots, create nodes, and edit UI directly on Figma canvas via a bridge between MCP and Figma Desktop.10MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to programmatically interact with a Miro board through the Miro API, supporting operations like creating items, updating positions, and managing connectors.16ISC
- AlicenseNot gradedqualityBmaintenanceEnables remote AI agents to control a local, authenticated desktop browser over MCP through an outbound WebSocket bridge and Chrome extension, supporting tab management, navigation, page reading, clicking, typing, scrolling, screenshots, and JavaScript evaluation.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables MCP-compatible AI clients to read and modify the user's currently open Figma file by executing JavaScript in Figma's sandbox, all through a local bridge with status monitoring, node jumping, and automatic rollback on errors.3MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible agents and HTTP clients to discover, claim, and control Chrome tabs through an authenticated local bridge, including snapshots, actions, approvals, task ownership, screenshots, frames, diagnostics, and cleanup.Apache 2.0
- AlicenseAqualityDmaintenanceEnables interaction with Miro boards via MCP tools, supporting listing items, creating stickies, frames, shapes, connectors, and manipulating mind maps.13MIT
TDQS
Scored across 14 tools
Most tools have a clear distinct purpose (read vs. create vs. delete vs. mutate vs. viewport), and descriptions add helpful cues like 'z-order' for reorder_items vs. 'auto-layout' for arrange_items. Two mild overlaps remain: get_selection and get_focus both return user-selected items, and reorder_items/arrange_items could be confused at a glance despite the clarifying text.
Nearly all tools follow a snake_case verb_object pattern (get_items, create_items, update_items, delete_items, group_items, set_focus, get_board_info). Minor deviations: 'capture' is a bare verb with no object, and 'zoom_to' uses a verb+preposition form that breaks the pattern slightly.
14 tools sit comfortably in the well-scoped range, and each one maps to a distinct board operation: reading (items, focus, selection, board info), mutation (create/update/delete/group/reorder/arrange), plus capture and zoom_to for visual feedback. Nothing looks redundant or missing for the stated Miro workflow purpose.
The surface covers the full lifecycle — create (including bulk, tables, images, connectors), read (compact and via board info/focus/selection), update, delete, plus grouping, z-order, auto-layout, viewport and screenshot verification — so agents won't hit dead ends. The main gap is native Miro tables being unreadable except via the capture workaround, and no direct single-item fetch beyond filtering get_items by id.