Skip to main content
Glama
JonatanCosta

plane-local-mcp

by JonatanCosta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to plane-local-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • plane-mcp

      bhflm
      A
      license
      Not graded
      quality
      B
      maintenance
      Local MCP server for a self-hosted Plane instance that exposes tickets, cycles, modules, labels, and states as MCP tools with both read and mutation capabilities.
      7 npm
      MIT

    • 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 MCP Server by makeplane

      Plane MCP Serverofficial

      makeplane
      A
      license
      B
      quality
      A
      maintenance
      A Model Context Protocol server that enables AI interfaces to seamlessly interact with Plane's project management system, allowing management of projects, issues, states, and other work items through a standardized API.
      46
      121 npm
      325
      MIT

    • Plane MCP Server

      disrex-group
      A
      license
      B
      quality
      C
      maintenance
      A Model Context Protocol (MCP) server that enables LLMs to interact with Plane.so, allowing them to manage projects and issues through Plane's API. Using this server, LLMs like Claude can directly interact with your project management workflows while maintaining user control and security.
      76
      4 npm
      1
      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

    B3.3/5.0

    Scored across 14 tools

    Disambiguation4/5

    Each tool targets a distinct resource or action, but the pair retrieve_issue and get_issue_by_identifier both retrieve a single issue, differing only by lookup key. This minor overlap is clarified by descriptions, so most tools are unambiguous.

    Naming Consistency4/5

    Names follow a verb_noun pattern with snake_case throughout, but verbs are inconsistent (list, get, retrieve, update, add, remove). This is readable but not as uniform as using the same verb for the same operation.

    Tool Count5/5

    With 14 tools, the server covers issues, cycles, states, labels, modules, and projects without feeling bloated. This is well-scoped for a project management integration.

    Completeness3/5

    The surface has strong read and update coverage for issues and cycles, but notably lacks a create_issue tool or any deletion capability. Agents cannot create new issues, so the lifecycle is incomplete.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources