HacknPlan MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HACKNPLAN_API_KEY | Yes | Your HacknPlan API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsB | List all projects in your workspace |
| get_projectB | Get details of a specific project |
| create_projectC | Create a new project |
| update_projectA | Partially update a project's name or description (PATCH — only provided fields are changed) |
| delete_projectB | Permanently delete a project |
| close_projectA | Archive (close) a project without deleting it. Use reopen_project to restore it. |
| reopen_projectB | Reopen a previously closed (archived) project |
| get_project_metricsC | Get progress and burndown metrics for a project |
| change_project_ownerC | Transfer ownership of a project to another user |
| list_boardsC | List all boards in a project |
| get_boardC | Get details of a specific board |
| create_boardC | Create a new board in a project |
| update_boardB | Partially update a board (PATCH — only provided fields are changed) |
| delete_boardB | Permanently delete a board |
| close_boardA | Archive (close) a board without deleting it. Use reopen_board to restore it. |
| reopen_boardC | Reopen a previously closed (archived) board |
| get_board_metricsC | Get progress and burndown metrics for a board |
| list_milestonesC | List all milestones in a project |
| get_milestoneC | Get details of a specific milestone |
| create_milestoneC | Create a new milestone in a project |
| update_milestoneB | Partially update a milestone (PATCH — only provided fields are changed) |
| delete_milestoneC | Permanently delete a milestone |
| close_milestoneA | Archive (close) a milestone without deleting it. Use reopen_milestone to restore it. |
| reopen_milestoneB | Reopen a previously closed (archived) milestone |
| get_milestone_metricsC | Get progress and burndown metrics for a milestone |
| list_work_itemsC | List work items in a project with optional filters and sorting |
| get_work_itemC | Get details of a specific work item |
| create_work_itemC | Create a new work item (task) in a project |
| update_work_itemC | Update an existing work item |
| clone_work_itemC | Create a copy of an existing work item |
| delete_work_itemC | Permanently delete a work item |
| list_categoriesC | List work item categories in a project |
| create_categoryC | Create a new work item category in a project |
| get_categoryC | Get details of a specific category |
| update_categoryB | Partially update a category (PATCH — only provided fields are changed) |
| delete_categoryC | Permanently delete a category |
| list_stagesB | List workflow stages in a project |
| create_stageC | Create a new workflow stage in a project |
| get_stageC | Get details of a specific stage |
| update_stageB | Partially update a stage (PATCH — only provided fields are changed) |
| delete_stageC | Permanently delete a stage |
| list_importance_levelsA | List importance levels in a project (used as importanceLevelId when creating work items) |
| create_importance_levelC | Create a new importance level in a project |
| get_importance_levelC | Get details of a specific importance level |
| update_importance_levelB | Partially update an importance level (PATCH — only provided fields are changed) |
| delete_importance_levelC | Permanently delete an importance level |
| list_project_usersC | List users in a project |
| get_project_userC | Get details of a specific user within a project |
| get_current_userA | Get information about the currently authenticated user |
| replace_projectC | Full replacement of a project (PUT — all fields required) |
| replace_boardC | Full replacement of a board (PUT — all fields required) |
| replace_milestoneB | Full replacement of a milestone (PUT — all fields required) |
| set_default_boardC | Set the default board for a project |
| clear_default_boardC | Remove the default board setting for a project |
| list_work_item_attachmentsB | List all attachments on a work item |
| get_work_item_attachmentC | Get details of a specific work item attachment |
| delete_work_item_attachmentC | Delete an attachment from a work item |
| add_project_userC | Add a user to a project |
| update_project_userC | Partially update a user's project membership (PATCH) |
| replace_project_userC | Full replacement of a user's project membership (PUT) |
| add_team_to_projectC | Add an entire team to a project |
| list_project_rolesC | List all roles in a project |
| create_project_roleC | Create a new role in a project |
| get_project_roleC | Get details of a specific project role |
| update_project_roleC | Partially update a project role (PATCH) |
| replace_project_roleC | Full replacement of a project role (PUT) |
| delete_project_roleC | Delete a project role |
| list_project_tagsC | List all tags in a project |
| create_project_tagB | Create a new tag in a project |
| update_project_tagC | Partially update a project tag (PATCH) |
| replace_project_tagC | Full replacement of a project tag (PUT) |
| delete_project_tagB | Delete a project tag |
| list_design_elementsC | List design elements (GDD documents) in a project |
| create_design_elementB | Create a new design element (GDD document) in a project |
| get_design_elementB | Get details of a specific design element |
| update_design_elementC | Partially update a design element (PATCH) |
| replace_design_elementC | Full replacement of a design element (PUT) |
| delete_design_elementC | Delete a design element |
| get_design_element_metricsC | Get metrics for a design element |
| list_design_element_attachmentsC | List attachments on a design element |
| get_design_element_attachmentC | Get a specific attachment on a design element |
| delete_design_element_attachmentC | Delete an attachment from a design element |
| list_design_element_commentsB | List comments on a design element |
| create_design_element_commentC | Add a comment to a design element |
| update_design_element_commentC | Update a comment on a design element (PUT — replaces content) |
| delete_design_element_commentC | Delete a comment from a design element |
| list_design_element_typesA | List design element types in a project (used as typeId when creating design elements) |
| create_design_element_typeC | Create a new design element type in a project |
| get_design_element_typeC | Get details of a specific design element type |
| update_design_element_typeC | Partially update a design element type (PATCH) |
| replace_design_element_typeC | Full replacement of a design element type (PUT) |
| delete_design_element_typeC | Delete a design element type |
| list_project_eventsC | List activity events for a project |
| list_project_filesC | List files stored in a project |
| delete_project_fileC | Delete a file from a project |
| get_project_storageA | Get file storage quota and usage for a project |
| list_webhook_event_typesA | List all available webhook event types |
| list_webhooksC | List all webhooks configured for a project |
| create_webhookC | Create a new webhook for a project |
| get_webhookC | Get details of a specific webhook |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.