Skip to main content
Glama
mgh3326

miro-mcp

by mgh3326
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to miro-mcp

No user-submitted related servers found.

    Related Servers

    • Miro MCP Server

      thescriptedsouls
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides comprehensive access to the Miro REST API v2 for advanced board management, content creation, and team collaboration. It supports over 40 tools for managing board items like sticky notes and shapes, alongside bulk operations and organizational features.
      30 npm
      2
      Apache 2.0

    • NetzSchule Miro MCP Server

      my-best-code
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Miro whiteboards via MCP and REST API, including board manipulation, sticky notes, shapes, and bulk operations.
      9 npm
      1
      Apache 2.0

    • Miro MCP Server

      LuotoCompany
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to programmatically interact with a Miro board through the Miro API, supporting operations like creating items, updating positions, and managing connectors.
      16
      ISC

    • mcp-miro

      mikeysrecipes
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects to the MIRO Whiteboard Application, allowing board manipulation, sticky creation, and bulk operations.
      33 npm
      Apache 2.0

    • Miro MCP Server

      henqc
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables MCP-compatible LLMs to interact with Miro whiteboards to manage boards, create and manipulate shapes, and organize content through grouping tools.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.8/5.0

    Scored across 77 tools

    Disambiguation4/5

    Most tools have a distinct resource/action target, and descriptions clarify overlaps such as generic get_item versus type-specific get_doc/get_group. However, the many per-type create/update tools plus generic bulk and generic get/list tools create some selection ambiguity for agents.

    Naming Consistency4/5

    The set overwhelmingly follows a snake_case verb_noun convention (create_board, update_sticky_note, bulk_delete_items). Minor deviations like whoami and ungroup are readable but not fully consistent with the pattern.

    Tool Count1/5

    77 tools is an extreme mismatch for a coherent agent-facing toolset; the surface is inflated by per-item-type CRUD variants and bulk/generic alternatives. This creates substantial selection burden even if individual tools are useful.

    Completeness4/5

    The surface covers boards, members, tags, groups, connectors, docs, many item types, exports, and auth, with broad CRUD coverage. Minor gaps remain, such as no update operation for mind map nodes and some resource access relying on generic item tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources