A
licenseNot graded
qualityC
maintenanceEnables AI agents to interact with Plane project management APIs, offering tools for managing projects, work items, cycles, modules, initiatives, and more through MCP.
MIT
8seneca Projects MCP Server
Officialby 8seneca-hub
Related Servers
Alternatives to 8seneca Projects MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI models to interact with a self-hosted Plane workspace through MCP tools, supporting task, project, cycle, and module management.-
- 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.-
- AlicenseBqualityDmaintenanceEnables interaction with Plane.so project management API through natural language, allowing users to manage issues, cycles, and projects.10MIT
- AlicenseAqualityCmaintenanceEnables interaction with self-hosted Plane project management instances using X-API-Key authentication, offering tools for project discovery, issue management, and workflow state operations.7MIT
- AlicenseBqualityDmaintenanceAn MCP server that enables LLMs to fully manage a Plane workspace, including projects, work items, states, labels, cycles, modules, comments, and members.38MIT
TDQS
C2.8/5.0
Scored across 54 tools
Disambiguation4/5
Most tools follow a clear CRUD-per-resource structure, so list/get/create/update/delete operations are easy to tell apart. A few names like delete_module_issue and delete_cycle_issue could be mistaken for deleting the issue itself, but the descriptions clarify the link-removal semantics.
Naming Consistency4/5
The dominant verb_noun snake_case pattern is consistent and predictable across the majority of tools. Outliers like get_issue_using_readable_identifier and delete_module_issue break the pattern, but they are few relative to the 54-tool surface.
Tool Count2/5
54 tools is far above a typical well-scoped MCP surface and would be better split into focused servers by resource family. The CRUD organization makes it navigable, but the sheer size creates significant selection and context overhead for an agent.
Completeness2/5
Several resource families have full CRUD, but the central issue resource lacks delete_issue and there is no generic get_issue by UUID. Comment operations only cover read/add, and project update/delete are missing, leaving notable dead ends for common workflows.
Maintenance
ActivityMaintained
ResponsivenessNo issues