Skip to main content
Glama
aveq-research

Surfmeter MCP Server

Official
by aveq-research
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Surfmeter MCP Server

No user-submitted related servers found.

    Related Servers

    • ConnectWise API Gateway MCP

      jasondsmith72
      F
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server that provides a comprehensive interface for interacting with the ConnectWise Manage API, simplifying API discovery, execution, and management for both developers and AI assistants.
      2 npm
      18
      -

    • meshcore-mcp

      dpup
      A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol server that exposes a MeshCore node and the mesh reachable through it as a clean, high-signal interface for AI agents or tools.
      30
      8 npm
      1
      MIT

    • Supabase MCP Server

      JoshuaRileyDev
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that provides programmatic access to the Supabase Management API. This server allows AI models and other clients to manage Supabase projects and organizations through a standardized interface.
      8
      40 npm
      52
      MIT

    • MCP API Server

      fikri2992
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants to make HTTP requests (GET, POST, PUT, DELETE) to external APIs through standardized MCP tools.
      4
      2
      MIT

    • hetzner-mcp

      devinoldenburg
      A
      license
      Not graded
      quality
      A
      maintenance
      Model Context Protocol server for full Hetzner Cloud + Storage API automation. Exposes all official Hetzner operations as MCP tools so AI agents can manage servers, networking, load balancers, firewalls, volumes, DNS zones, and storage boxes from one server.
      1
      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.8/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but get_system_status bundles multiple concerns (server metadata, client status history, thresholds, AI status) and could be confused with get_clients for status-related queries. The two search tools are structurally similar as well, though their target document types are clear.

    Naming Consistency5/5

    All tools follow a consistent surfmeter_<verb>_<object> pattern with snake_case throughout. The progression from search_actions → describe_action → execute_*_action is predictable and logical.

    Tool Count5/5

    Ten tools is well-scoped for this domain: direct client/measurement/anomaly/status access plus a generic action discovery and execution workflow. Each tool serves a distinct role without unnecessary bloat.

    Completeness4/5

    The dynamic action system fills coverage gaps for less-common operations, making the surface quite capable. However, direct client lifecycle management is incomplete (get and update only, no create/delete), and measurements/anomalies are only accessible via search rather than direct retrieval.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources