A
licenseB
qualityF
maintenanceA 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.
6
40
MIT
Plane MCP Server
Officialby makeplane
Related Servers
Alternatives to Plane MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceA 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
- AlicenseBqualityCmaintenanceA 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.7619 npm1MIT
- AlicenseBqualityDmaintenanceAn MCP server that enables LLMs to fully manage a Plane workspace, including projects, work items, states, labels, cycles, modules, comments, and members.38MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for the Plane project management API, enabling issue retrieval, listing, commenting, state changes, and creation.1MIT
- 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
B3/5.0
Scored across 46 tools
Disambiguation4/5
Most tools have distinct purposes targeting specific resources and actions, with clear boundaries between operations like create, get, list, update, and delete. However, some potential confusion exists between 'add_cycle_issues' and 'transfer_cycle_issues' or between various 'get' tools that might overlap in retrieving issue-related data, though descriptions help clarify their specific contexts.
Naming Consistency5/5
Tool names follow a highly consistent verb_noun pattern throughout, such as create_cycle, get_issue, update_label, and delete_module. All tools use snake_case uniformly, with verbs like add, create, delete, get, list, transfer, and update applied predictably across different resources, making the naming scheme very coherent and readable.
Tool Count2/5
With 46 tools, the count is excessive for a project management server, likely overwhelming for agents and leading to complexity in tool selection. While the domain is broad, a more focused set of 15-25 tools would be more manageable, as many operations could be consolidated or generalized rather than having separate tools for each minor variation.
Completeness5/5
The tool set provides comprehensive CRUD and lifecycle coverage for the project management domain, including projects, issues, cycles, modules, labels, states, worklogs, and comments. It supports all essential operations from creation to deletion, with additional utilities like transfer and listing, leaving no obvious gaps for core workflows.
Maintenance
ActivityActive
ResponsivenessUnresponsive