nod-mcp
OfficialRelated Servers
Alternatives to nod-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceProvides comprehensive tools for managing GitHub projects, milestones, tasks, and sprints. This server integrates deeply with GitHub Projects V2, offering features like automated kanban workflows, sprint planning, and custom field management.84397 npm101MIT
- AlicenseNot gradedqualityDmaintenanceProvides project management capabilities through terminal, web UI, or MCP stdio, including plans, code analysis, and filesystem-safe operations.13 npmMIT
- FlicenseAqualityDmaintenanceProvides tools for managing project knowledge graphs, enabling structured representation of projects, tasks, milestones, resources, and team members.616-
- FlicenseNot gradedqualityFmaintenanceEnables unified management of work items from multiple tools through a kanban, providing CRUD, status transitions, comments, links, enrichment, dispatch, and board tools via MCP.-
- AlicenseNot gradedqualityBmaintenanceProvides tools for governed project work, including project setup, workspace management, and task execution, with credential-safe MCP wiring.MIT
- AlicenseNot gradedqualityCmaintenanceEnables managing GitHub Project views, priorities, dependencies, and metrics through natural language.1MIT
TDQS
Scored across 8 tools
Most tools have distinct resource+action names (e.g., work_item_list vs work_item_get), but 'board' is a bare noun with unclear scope and could overlap with work_item_list or timeline. The three view-like tools (board, timeline, dependency_graph) are conceptually separate but lack descriptions to clarify boundaries.
Five tools follow a consistent resource_verb pattern (project_get, work_item_list, work_item_get, work_item_create, work_item_update), but 'board', 'timeline', and 'dependency_graph' break that pattern as bare nouns. The mix is readable but not uniform.
Eight tools is a well-scoped number for a project management server, falling comfortably within the ideal 3–15 range. Each tool appears to cover a distinct operation or view without excessive redundancy.
The surface covers create, read (list/get), and update for work items, but lacks a delete operation and any create/list/update for projects (only project_get is present). Board and timeline tools are read-only, which may be acceptable but leaves lifecycle gaps.