Skip to main content
Glama
tbranzov

HAOps MCP Server

by tbranzov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to HAOps 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
      8 npm
      MIT

    • System Task MCP

      luis1amaral
      A
      license
      A
      quality
      B
      maintenance
      Enables Claude to interact with System Task projects, teams, and tasks, providing daily briefs, project reports, team load, and risk identification, as well as creating and updating tasks and demands.
      15
      MIT

    • OpenProject MCP Server

      devsergioherrera
      A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      13
      MIT

    • freedcamp

      cubo3
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects Claude to a project-management account so it can list and manage projects, tasks, comments, and files through eight REST API tools, including creating and updating tasks and adding comments.
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    A3.5/5.0

    Scored across 137 tools

    Disambiguation4/5

    Most tools have distinct purposes with clear descriptions, but there is some overlap (e.g., multiple 'claim' tools, bulk vs individual skill updates). The descriptions help differentiate, but the sheer number may still cause confusion.

    Naming Consistency5/5

    All tools follow a consistent 'haops_verb_noun' pattern (e.g., haops_list_issues, haops_create_feature). Naming is uniform and predictable across the entire set.

    Tool Count2/5

    With 137 tools, the surface area is extremely large. While it reflects a comprehensive system, it likely includes many rarely used tools and can overwhelm agents. A more focused set would be preferable.

    Completeness4/5

    The tool set covers a wide range of domains (project management, git, helpdesk, documentation, skills, protocols, memory). There are minor gaps (e.g., missing some lifecycle transitions), but overall it is quite complete for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources