Skip to main content
Glama

Related Servers

Alternatives to ApexMCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables MCP hosts to inspect TP-Link Omada SDN controllers through the Web API with read-only tools returning clean JSON, optional allowlisted writes, monitoring modes, and a doctor that diagnoses configuration failures.
      35
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables monitoring and controlling KegLand RAPT fermentation chambers and RaptPill hydrometers through the RAPT.io API, including temperature control, PID configuration, and telemetry retrieval.
      23
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables natural language control of AC Infinity UIS grow controllers to read tent climate, sensor data, port settings, and automations, and to modify port modes, power levels, timers, schedules, and automation rules via MCP clients like Claude or Codex.
      18
      2
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables MCP-compatible clients to query and manage LenelS2 S2 NetBox physical access-control systems via the NBAPI, with read-only tools by default and opt-in write/destructive operations.
      51
      41 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables managing VyOS appliances through their HTTP API, providing tools for configuration, operational commands, and interactive troubleshooting.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to inspect, query, and diagnose problems within an Octopus Deploy instance, with tools for projects, deployments, releases, runbooks, tasks, tenants, Kubernetes, targets, certificates, accounts, and approvals, plus a structured REST backstop. Runs read-only by default-optional write and delete modes so assistants can also create releases, deploy, and run runbooks under confirmation.
      547 npm
      MIT

    TDQS

    B3.2/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools target clearly different facets: live outlet state vs. event log vs. duty-cycle aggregates vs. probe history vs. probe stats are well separated. The notable overlaps are apex_water_parameters versus apex_get_probes (curated chemistry summary vs. filtered raw readings) and apex_power_summary versus probes with pwr/Amps filters, but the descriptions make the intended split reasonably clear.

    Naming Consistency4/5

    All names share the apex_ prefix and consistent snake_case, and the noun phrases are descriptive (probe_history, outlet_events, duty_cycle). The only inconsistency is verb style: some use get_ (get_program, get_outlets, get_config) while equally retrieval-oriented tools use bare nouns (system_info, water_parameters, feed_status).

    Tool Count5/5

    Fourteen tools is well within the sweet spot and each one covers a distinct slice of controller telemetry (state, config, history, aggregates, health). Nothing looks like padding or a near-duplicate kept just to fill space.

    Completeness4/5

    For a monitoring surface it is thorough: identity, config sections, probe readings, history, stats, outlet state, event timing, duty cycle, feed status and module health are all covered. The obvious gap is any control operation — no setting outlet modes, triggering a feed cycle, or rebooting modules — so agents hit a dead end if the task requires action rather than observation.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues