Plane MCP Server
Related Servers
Alternatives to Plane MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityFmaintenanceA Model Context Protocol server that enables LLMs to interact with Plane.so, allowing them to manage projects and issues through Plane's API for streamlined project management workflows.640MIT

Plane MCP Serverofficial
AlicenseBqualityAmaintenanceA 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.546121 npm340MIT- AlicenseBqualityDmaintenanceAn MCP server that enables LLMs to fully manage a Plane workspace, including projects, work items, states, labels, cycles, modules, comments, and members.38MIT
- AlicenseBqualityCmaintenanceA Model Context Protocol server that enables AI agents to interact with Plane project management APIs, supporting projects, work items, cycles, modules, and more via stdio, SSE, and HTTP transports.100MIT
- 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
TDQS
Scored across 76 tools
Every tool has a clearly distinct purpose targeting specific resources and actions, with no ambiguity. For example, tools like 'add-issues-to-cycle' and 'remove-issue-from-cycle' are complementary but distinct, and operations like 'create-issue' versus 'create-sub-issue' are well-defined.
Tool names follow a highly consistent verb-noun pattern with hyphens throughout (e.g., create-issue, list-issues, update-cycle). All tools adhere to this convention, making them predictable and readable without any mixing of styles.
With 76 tools, the count is excessive for most agent use cases, likely causing cognitive overload and inefficiency. While the domain is comprehensive, this many tools feels heavy and could overwhelm users or agents trying to navigate the API surface.
The tool set provides complete CRUD/lifecycle coverage for the project management domain, including issues, cycles, modules, states, labels, and more. There are no obvious gaps; every major operation (create, read, update, delete, list) is covered for all key resources.