Skip to main content
Glama
Lint111

HacknPlan MCP Server

by Lint111
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to HacknPlan MCP Server

No user-submitted related servers found.

    Related Servers

    • hacknplan-mcp

      mtuska
      A
      license
      B
      quality
      C
      maintenance
      Enables 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.
      75
      10 npm
      MIT

    • Tonle OpenProject MCP Server

      liratanak
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to interact with OpenProject's API v3 for comprehensive project management operations including work packages, projects, time tracking, users, and all other OpenProject features through natural language.
      3
      MIT

    • OpenProject MCP Server

      cyborgx0x
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to manage OpenProject work packages, projects, and time tracking. It provides comprehensive tools for creating, updating, and querying tasks and project metadata through the OpenProject API.
      11
      25 npm
      1
      MIT

    • sprrint

      ejasmuhamed
      A
      license
      C
      quality
      B
      maintenance
      Enables agents to manage projects, tasks, sprints, the Black Hole, comments, invites, and workspace settings through the Sprrint API using natural language or tool calls.
      40
      MIT

    • OpenProject MCP Server

      Tangaratta-Engineering
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with OpenProject installations for comprehensive project management, including creating projects and work packages, managing users and assignments, creating dependencies, and generating Gantt charts through natural language commands.
      14
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 91 tools

    Disambiguation3/5

    Many tools have clearly distinct purposes, but there are overlapping pairs like get_my_current_tasks vs get_my_tasks, and multiple create work item tools (create_work_items, create_work_item_atomic, create_subtask, create_from_template) which may confuse an agent. The deletion workflow also has several steps (batch_delete_work_items, confirm_deletion, cancel_deletion) that could be grouped.

    Naming Consistency4/5

    Naming largely follows a verb_noun pattern with underscores (e.g., create_work_items, list_projects). Minor inconsistencies include mixed verb prefixes (add_comments vs create_comments) and compound names like get_active_sprint_overview, but overall the pattern is predictable.

    Tool Count2/5

    With 91 tools, the server is extremely heavy. Typical MCP servers have 3-15 tools; this is far beyond and likely to overwhelm agents. Many tools could be consolidated (e.g., batch operations combined with single-item calls).

    Completeness5/5

    The tool set covers nearly every aspect of the domain: full CRUD for work items, boards, milestones, projects, design elements, comments, attachments, dependencies, time tracking, user info, cache management, and even administrative controls like setting default project. No obvious gaps are apparent.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources