F
licenseC
qualityC
maintenanceEnables Claude to manage game development projects on HacknPlan, including tasks, boards, milestones, and GDD documents through natural language.
100
3
-
hacknplan-mcp
by mtuska
Related Servers
Alternatives to hacknplan-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables AI assistants to manage game development projects, sprints, tasks, and design documents via the HacknPlan API.916MIT
- FlicenseAqualityBmaintenanceEnables Claude to interact with the HAOps project management system for managing projects, modules, features, and issues.100-
- AlicenseNot gradedqualityDmaintenanceEnables AI-powered project management by connecting Claude to Planka kanban boards via 75+ MCP tools for creating, updating, and managing projects, boards, lists, and cards.1GPL 3.0
- AlicenseAqualityCmaintenanceEnables Claude to connect to an OpenProject instance and query, search, and manage projects, work packages, users, and time entries through natural language. Supports advanced filtering, pagination, and creation of work packages like epics and user stories.13MIT
- AlicenseAqualityBmaintenanceEnables Claude Code and Claude Desktop to manage ClickUp tasks, sprints, reports, workspace navigation, and docs through 25+ MCP tools.28MIT
TDQS
B3.2/5.0
Scored across 75 tools
Disambiguation5/5
Each tool targets a distinct resource and action (e.g., create_work_item vs. update_work_item vs. delete_work_item), and even similar operations like list_work_items, find_work_items, and my_work are clearly differentiated by their descriptions. The naming and descriptions make the purpose of each tool unambiguous, despite the large number of tools.
Naming Consistency4/5
The majority of tools follow a consistent snake_case verb_noun pattern (create_, update_, list_, get_, delete_, etc.). A few tools like portfolio_overview, schedule_overview, recent_activity, hacknplan_whoami, and my_work deviate from this pattern but remain in snake_case and are still readable and logically named.
Tool Count1/5
With 75 tools, this server far exceeds the typical well-scoped MCP server size of 3-15 tools and even the 25+ threshold for 'too many'. While the breadth reflects the full HacknPlan API, this is an extreme number that would overwhelm an agent and make tool selection unwieldy.
Completeness4/5
The tool set provides comprehensive CRUD coverage for most core resources: projects, stages, categories, tags, importance levels, boards, milestones, work items, subtasks, dependencies, comments, and design elements. A few minor gaps exist, such as lacking attachment upload/delete, user management within a project, and the ability to edit or delete comments, but the overall lifecycle is well-covered.
Maintenance
ActivityInactive
ResponsivenessNo issues