plane-mcp
Related Servers
Alternatives to plane-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceMCP server for Plane project management platform providing 56 tools for workspaces, projects, issues, comments, cycles, modules, and more.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to interact with Plane project management APIs, offering tools for managing projects, work items, cycles, modules, initiatives, and more through MCP.MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for the Plane project management API, enabling issue retrieval, listing, commenting, state changes, and creation.1MIT
- AlicenseNot gradedqualityBmaintenanceLocal 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.15 npmMIT
- AlicenseBqualityCmaintenanceEnables to manage Plane CE projects, issues, pages, modules, cycles, and more via MCP.561MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI models to interact with a self-hosted Plane workspace through MCP tools, supporting task, project, cycle, and module management.-
TDQS
Scored across 49 tools
Most tools are clearly separated by resource type (labels, states, issues, etc.), but `get_issue_using_readable_identifier` and `get_issue_details_by_readable_id` overlap heavily, both retrieving issues via readable identifiers with only slight input differences. This ambiguity could cause an agent to pick the wrong one.
The majority of tools follow a consistent verb_noun pattern (e.g., list_labels, create_issue, delete_cycle). Minor deviations like `get_issue_details_by_readable_id` and singular/plural mismatches (delete_module_issue vs add_module_issues) prevent a perfect score.
With 49 tools, the server is far above the 25+ threshold, making it unwieldy for agents to discover and select tools. Even for a broad project management domain, the count feels excessive and could benefit from consolidation.
The tool set provides full CRUD for issues, labels, states, issue types, modules, cycles, and worklogs, covering core workflows well. Some gaps exist, such as no update/delete for projects and no single-project getter, but these are minor and workable.