Skip to main content
Glama
donoree

superops-mcp

by donoree
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to superops-mcp

No user-submitted related servers found.

    Related Servers

    • superops-mcp

      Matt-Beyond-Tech
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables interaction with the SuperOps.ai PSA/RMM platform for managing clients, tickets, assets, and technicians via GraphQL API.
      Apache 2.0

    • SuperOps MCP Server

      Matt-Beyond-Tech
      A
      license
      A
      quality
      C
      maintenance
      MCP server for interacting with the SuperOps.ai PSA/RMM platform, providing tools for managing clients, tickets, assets, and technicians via GraphQL API.
      21
      Apache 2.0

    • groove-mcp

      ebenpaul
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables management of customer support tickets, contacts, agents, and knowledge base articles through the Groove HQ GraphQL API.
      14 npm
      MIT

    • nable-rmm-mcp

      MSPbotsAI
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables interaction with N-able RMM (N-sight) API to manage clients, sites, devices, and retrieve monitoring data such as checks, patches, and performance history.
      Apache 2.0
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    A3.6/5.0

    Scored across 21 tools

    Disambiguation5/5

    Each tool targets a distinct domain-action combination, and even overlapping areas like clients_list vs clients_search are clearly differentiated by filters vs name/email lookup. The custom GraphQL tools are explicitly positioned as fallbacks for advanced cases, not competing with the standard tools.

    Naming Consistency4/5

    The vast majority of tools follow a superops_<domain>_<action> pattern. Minor deviations exist: assets_software, assets_patches, and technicians_groups are noun-style getters, and the utility tools like status and navigate sit outside the pattern, but overall naming remains highly predictable.

    Tool Count4/5

    At 21 tools, the server is on the heavier side, but the count is justified by covering assets, tickets, clients, technicians, custom GraphQL, and connection/discovery utilities. Each tool maps to a meaningful operation with little redundancy.

    Completeness4/5

    The tool surface covers core asset, ticket, client, and technician workflows well, with ticket CRUD plus notes and time logging. Minor lifecycle gaps like ticket deletion or client creation are not directly exposed, but the presence of custom_query and custom_mutation provides a general escape hatch.

    Resources