HacknPlan MCP
Related Servers
Alternatives to HacknPlan MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables Claude to interact with HacknPlan project management via the MCP protocol. Provides tools for managing projects, work items, boards, milestones, time logs, design models, and cross-project portfolio views.7510 npmMIT
- 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-
- FlicenseNot gradedqualityCmaintenanceEnables managing GitHub Projects v2 boards through Claude Code and Codex, including project and item administration, field updates, sprint boards, epic rollups, and desired-state planning.-
- 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
- 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
TDQS
Scored across 103 tools
Tools are clearly separated by resource type (board, milestone, design element, etc.) with distinct actions (create, get, update, replace, delete). However, the high number of tools and the presence of both update and replace for some resources could cause minor confusion, though descriptions clarify they are PATCH vs PUT.
All tool names follow a consistent verb_noun pattern using lowercase and underscores. Verbs like create, get, list, update, delete, replace, close, reopen are used uniformly across resource types, with no mixing of conventions.
With 103 tools, the set is very heavy. While each tool serves a specific purpose, many are redundant CRUD variants (e.g., separate replace_ and update_ for the same resource), and the overall count far exceeds typical MCP server scopes, making it unwieldy for agents.
The tool surface is remarkably comprehensive, covering all major entities (projects, boards, work items, milestones, design elements, roles, tags, stages, webhooks) with full CRUD, plus metrics, attachments, comments, and user management. Only minor gaps like bulk operations or advanced search are missing.