Skip to main content
Glama
Matt-Beyond-Tech

SuperOps MCP Server

by Matt-Beyond-Tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to SuperOps MCP Server

No user-submitted related servers found.

    Related Servers

    • superops-mcp

      WYRE-AI
      A
      license
      A
      quality
      A
      maintenance
      An MCP server for SuperOps PSA/RMM, enabling MSPs to manage tickets, assets, clients, and field technician operations through SuperOps's API.
      22
      3
      Apache 2.0

    • superops-mcp

      donoree
      A
      license
      A
      quality
      C
      maintenance
      Enables interaction with the SuperOps.ai PSA/RMM platform via its GraphQL API, providing tools for managing clients, tickets, assets, technicians, and custom queries.
      21
      Apache 2.0

    • 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

    • VSA-X-MCP

      perrytrienekens
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that wraps the VSA X API to enable querying and managing devices, assets, organizations, and rate limits, with centralized configuration and authentication forwarding.
      -

    • level-mcp

      pbozzay
      A
      license
      B
      quality
      D
      maintenance
      MCP server for the Level v2 REST API, enabling management of alerts, automations, devices, groups, tags, updates, and custom fields through typed tools.
      35
      MIT
    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

    A3.6/5.0

    Scored across 21 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action. Assets, clients, technicians, and tickets have separate tools for listing, getting, and specific operations (e.g., patches, software, search, groups, notes, time logging). Utility tools like custom_query and navigate serve clear auxiliary purposes without overlapping domain tools.

    Naming Consistency5/5

    All tools follow a consistent 'superops_{domain}_{action}' pattern with snake_case. Domains are plural (e.g., assets, clients) and actions describe the operation (list, get, create, etc.). The pattern is uniform across all 21 tools, making it predictable for agents.

    Tool Count4/5

    21 tools cover multiple domains (assets, clients, technicians, tickets) plus utility tools. While slightly above the 3-15 ideal range, the count is justified by the breadth of functionality needed for a PSA/RMM platform. It is not excessive and each tool has a clear role.

    Completeness4/5

    Core workflows for tickets (CRUD, notes, time logging) and assets (list, details, patches, software) are well-covered. Clients and technicians have basic retrieval and listing, but lack create/update/delete tools. The custom mutation/query tools fill advanced gaps, but some standard operations are missing.

    Resources