Plane Workflow MCP
Related Servers
Alternatives to Plane Workflow MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP server and automation watcher for Plane project management, enabling Claude to interact with Plane via 40+ tools and auto-trigger on labeled issues.-
- AlicenseBqualityDmaintenanceAn MCP server that enables LLMs to fully manage a Plane workspace, including projects, work items, states, labels, cycles, modules, comments, and members.38MIT
- AlicenseAqualityCmaintenanceMCP server for Plane, the open-source project management tool, exposing a focused set of task and comment management tools for a single Plane project. Includes a setup wizard to bind a local folder to a Plane project and configure Claude Code or Codex.163MIT
- AlicenseBqualityCmaintenanceLocal MCP server for interacting with a self-hosted Plane Community Edition instance. Enables listing projects, issues, states, labels, cycles, and updating issues via natural language.14MIT
- AlicenseBqualityAmaintenanceUnofficial MCP server for self-hosted Plane Community Edition, enabling project management tasks like managing work items, cycles, modules, and initiatives via natural language.1002MIT
- AlicenseCqualityDmaintenanceMCP server for Plane integration, enabling AI agents to interact with Plane APIs and services for project management tasks.100MIT
TDQS
Scored across 33 tools
The core workflow actions (create/start/complete/cancel/update work items) and the git-backfill, reporting, relation, evidence, and attachment tools are clearly distinct. Several read-only status/context tools overlap around workspace, project, profile, setup, and diagnostic information, so an agent may need to inspect descriptions carefully to choose the right getter.
Tool names consistently use snake_case with a verb-first pattern such as get_, list_, create_, apply_, validate_, and add_. The few longer names remain predictable and readable, with no significant mixing of naming conventions.
At 33 tools, the set is heavy for a single MCP server even though the domain is broad. Many setup/status/profile helpers could likely be consolidated or grouped, making discovery and selection more burdensome than necessary.
The server covers workspace/project activation, workflow profiles, standardization planning, work-item lifecycle operations, relations, evidence links, attachments, reporting, auditing, and git backfill. Minor gaps remain around deletion/detachment operations and standalone comment management, but core workflows are well covered.