plane-mcp-server
Related Servers
Alternatives to plane-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server for the Plane project management API, enabling issue retrieval, listing, commenting, state changes, and creation.1MIT
- 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 gradedqualityBmaintenanceMCP server for a Plane CE instance enabling management of pages (via direct database and live converter) and work items through Plane's REST API, with multi-workspace support.-
- AlicenseNot gradedqualityDmaintenanceAn MCP server for the Plane project management platform that enables users to manage workspaces, projects, and work items. It supports full CRUD operations for issues while providing access to cycles, modules, labels, and workflow states.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI models to interact with a self-hosted Plane workspace through MCP tools, supporting task, project, cycle, and module management.-
- 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.16 npmMIT
TDQS
Scored across 56 tools
Each tool targets a specific resource and action (e.g., plane-cycle-create vs plane-cycle-list). Clear prefixes and distinct verbs (upload, create, list, update, delete) make it easy for an agent to differentiate. Only minor overlap exists (e.g., page content tools) but descriptions clarify differences.
All tools follow the pattern plane-<resource>-<action> in lowercase snake_case. Actions are consistently verbs (create, list, update, delete, add, remove) with rare noun usage (detail, status) that still fits the pattern. No mixing of conventions (e.g., camelCase) exists.
With 56 tools, the server is on the high end of typical MCP servers. While the tools cover many aspects of the Plane platform (assets, cycles, pages, work items, workspace), the fragmentation (e.g., 8 page tools) may overwhelm agents. Slightly over-scoped but not extreme.
Covers core CRUD for work items, projects, pages, and workspace but missing delete/update for cycles, modules, and states. Also lacks page commenting and label updates. Notable gaps exist in lifecycle coverage, which may force workarounds.