Skip to main content
Glama
Sydney-Robotics-Academy

ops-mcp

by Sydney-Robotics-Academy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to ops-mcp

No user-submitted related servers found.

    Related Servers

    • uptime-kuma-rest

      gaido-dev
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLM clients to manage Uptime Kuma HTTP(S) monitors, groups, tags, and notifications, and to retrieve heartbeats, stats, and incident history through MCP tools.
      MIT

    • status-aggregator-mcp

      weiseer
      A
      license
      A
      quality
      D
      maintenance
      Aggregates status of multiple SaaS providers into a single MCP server, enabling AI agents to check service health and incidents via tools like list_services, get_status, and check_all.
      4
      44 npm
      Apache 2.0

    • uptime-kuma-mcp-server

      mehbul
      A
      license
      A
      quality
      B
      maintenance
      Enables managing Uptime Kuma monitoring through natural language, including creating, editing, pausing, and deleting monitors, plus retrieving heartbeats, status, metrics, notifications, and status pages.
      12
      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

    B3.4/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools have distinct purposes targeting different systems (Statuspage vs Uptime Kuma) and actions (create, list, update). However, 'ops_create_maintenance' and 'ops_schedule_maintenance' could cause confusion as both create maintenance, with the latter being a combined operation for both systems. The descriptions help clarify this overlap, but agents might initially misselect between them.

    Naming Consistency5/5

    All tools follow a consistent 'ops_verb_noun' pattern with snake_case throughout. The verbs (create, list, update, end, schedule) are clear and predictable, and the nouns (maintenance, components, incidents, monitors) accurately describe the resources. This uniformity makes the tool set easy to navigate and understand.

    Tool Count5/5

    With 9 tools, this server is well-scoped for managing maintenance and incidents across Statuspage and Uptime Kuma. Each tool serves a specific function without redundancy, covering key operations like listing, creating, updating, and ending maintenance. The count is appropriate for the domain, providing comprehensive coverage without being overwhelming.

    Completeness4/5

    The tool set offers strong coverage for maintenance and incident management across two systems, including CRUD-like operations (create, list, update/end). Minor gaps exist, such as no tool to delete or update Uptime Kuma maintenance specifically, and no direct incident creation for Statuspage. However, agents can work around these using the available tools, and core workflows are well-supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources