plane-mcp
Related Servers
Alternatives to plane-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.-
- AlicenseCqualityDmaintenanceMCP server for Plane integration, enabling AI agents to interact with Plane APIs and services for project management tasks.100MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for the Plane project management API, enabling issue retrieval, listing, commenting, state changes, and creation.1MIT
- AlicenseBqualityDmaintenanceAn MCP server that enables LLMs to fully manage a Plane workspace, including projects, work items, states, labels, cycles, modules, comments, and members.38MIT
- 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
- 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
TDQS
Scored across 16 tools
Most tools target distinct resources and actions (list_members, list_labels, list_states, create_task, etc.), but change_status overlaps with update_task (both can modify status) and add_comment_with_image overlaps with add_comment. The descriptions clarify the differences, so ambiguity is limited.
Tool names follow a consistent verb_noun pattern (list_*, create_task, update_task, add_comment). Minor deviations include change_status (could be update_status) and add_comment_with_image (longer but still verb_noun). No camelCase or mixed conventions.
16 tools is slightly above the typical 3-15 range but reasonable for a project management server covering tasks, attachments, comments, labels, states, and members. Each tool serves a distinct purpose within the scope.
The surface covers core task operations (create, read, update, status change) and attachments/comments, but lacks task deletion and label/member management. The server appears read-focused for config entities, yet missing delete for tasks is a notable gap.