Skip to main content
Glama
goto-software

plane-mcp-server

by goto-software
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to plane-mcp-server

No user-submitted related servers found.

    Related Servers

    • Plane MCP

      Rockysingh116
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that enables LLMs to fully manage a Plane workspace, including projects, work items, states, labels, cycles, modules, comments, and members.
      38
      MIT

    • plane-ce-mcp

      Bl4nk44
      A
      license
      B
      quality
      A
      maintenance
      Unofficial MCP server for self-hosted Plane Community Edition, enabling project management tasks like managing work items, cycles, modules, and initiatives via natural language.
      100
      2
      MIT

    • claude-plane

      FishyF1sh
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server and automation watcher for Plane project management, enabling Claude to interact with Plane via 40+ tools and auto-trigger on labeled issues.
      -

    • plane-mcp

      cmet7
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for the Plane project management platform that enables users to manage workspaces, projects, and work items. It supports full CRUD operations for issues while providing access to cycles, modules, labels, and workflow states.
      MIT
    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.6/5.0

    Scored across 109 tools

    Disambiguation2/5

    Several tools have overlapping boundaries: list_work_items already accepts module_ids/cycle_ids and can search across the workspace, duplicating list_module_work_items, list_cycle_work_items, and search_work_items. The additional split between get_* and retrieve_* methods, plus work_item_links vs work_item_relations, creates further ambiguity at this scale.

    Naming Consistency4/5

    Most resources follow a consistent list_/create_/retrieve_/update_/delete_ CRUD pattern. Minor deviations exist: get_me, get_project_*, and get_workspace_* use get_ instead of retrieve_, and a few container actions are inconsistent in singular/plural phrasing.

    Tool Count1/5

    At 109 tools, this is an extreme-sized MCP surface, far beyond the 3-15 tool sweet spot and well past the 25+ 'too many' threshold. Even if each endpoint maps to a real API operation, the tool count creates excessive selection overhead for agents.

    Completeness3/5

    Core resources like projects, work items, cycles, modules, epics, milestones, states, labels, and types have solid CRUD/lifecycle coverage. However, pages only have create/retrieve with no list/update/delete, and work item relations lack retrieve/update operations, leaving noticeable gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources