A
licenseB
qualityD
maintenanceEnables interaction with Plane.so project management API through natural language, allowing users to manage issues, cycles, and projects.
10
MIT
Plane MCP
by ZethicTech
Related Servers
Alternatives to Plane MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to interact with Plane project management APIs, offering tools for managing projects, work items, cycles, modules, initiatives, and more through MCP.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI models to interact with a self-hosted Plane workspace through MCP tools, supporting task, project, cycle, and module management.-
- FlicenseNot gradedqualityDmaintenanceA server that bridges Claude AI with the Plane project management platform, enabling AI-powered project management tasks including project creation, task management, team collaboration, and automated workflows.5-
- FlicenseNot gradedqualityBmaintenanceEnables an LLM to act as a project manager across self-hosted Plane workspaces and projects, providing tools for work items, cycles, modules, states, labels, comments, members, and intake triage via Plane's REST API.-
- FlicenseNot gradedqualityDmaintenanceConnects Claude.ai to your Motion workspace, enabling task and project management via natural language.-
TDQS
B3.2/5.0
Scored across 78 tools
Disambiguation5/5
Every tool is tied to a specific resource and action (e.g., list_states vs. create_state, list_cycle_work_items vs. add_work_items_to_cycle). Despite the volume, the entity names make each tool's purpose immediately clear, and there is no overlap or ambiguity between tools.
Naming Consistency4/5
The dominant pattern is verb_noun (list_*, create_*, retrieve_*, update_*, delete_*), but a few tools use 'get' instead of 'retrieve' (e.g., get_server_version, get_project_members, get_workspace_members, get_me). The inconsistency is minor and does not impede understanding.
Tool Count2/5
With 78 tools, the server is much larger than typical MCP servers, making it heavy for agents to navigate. While the breadth matches the extensive domain (projects, work items, cycles, modules, epics, etc.), the count is excessive and risks overwhelming users.
Completeness4/5
The server covers CRUD for nearly all major resources (projects, work items, states, labels, cycles, modules, epics, milestones, initiatives, comments, links, relations). The only notable gap is pages, which only have create and retrieve—no update, delete, or list—representing a minor dead end.
Maintenance
ActivityStale
ResponsivenessUnresponsive