Skip to main content
Glama

Related Servers

Alternatives to arimair-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for the air-Q Cloud API, enabling remote retrieval of air quality sensor data and historical analysis through read-only tools like listing devices, fetching readings, and exporting charts or data.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      A read-only MCP server that exposes tools to query Datadog monitors and logs, and AWS CloudWatch Logs, and to group recurring errors by fingerprint. Designed for use with Claude Code to diagnose issues and propose fixes.
      MIT
    • A
      license
      C
      quality
      D
      maintenance
      An MCP server that provides seamless integration with Claude Desktop for querying and managing timeseries data in GigAPI Timeseries Lake.
      7
      6
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      A read-only MCP server that provides Claude Desktop with access to Garmin Connect running, strength-training, and calorie data via direct API calls.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      This read-only MCP Server allows you to connect to Adobe Analytics data from Claude Desktop through CData JDBC Drivers. For full CRUD support, check out the first managed MCP platform: CData Connect AI (https://www.cdata.com/ai/).
      3
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Read-only MCP server enabling natural language querying of personal health and cultural activity scores from the health.ojimpo.com dashboard via Claude.
      5
      10 npm
      MIT

    TDQS

    B3.1/5.0

    Scored across 36 tools

    Disambiguation2/5

    Multiple tools overlap in purpose, especially around data queries: data_recent vs device_realtime, monitor_search vs data_search vs data_raw_search vs stat_daily_avg, and monitor_rose vs monitor_rose_search. Descriptions clarify some differences, but several tool boundaries remain unclear and could easily cause misselection.

    Naming Consistency3/5

    Most tool names use snake_case with domain prefixes like device_, data_, stat_, correction_, report_, and monitor_, which provides structure. However, action verbs are inconsistent and some names are non-verb nouns or adjectives such as data_recent, monitor_rose, correction_factors, and report_v2_html, making the pattern less predictable.

    Tool Count2/5

    With 36 tools, the server exceeds the 25+ threshold and feels heavy. Several tools could be consolidated, such as the realtime variants, rose variants, and overlapping period-based data query tools, even though the overall domain is fairly broad.

    Completeness4/5

    The tool set gives broad read coverage for authentication, site/device context, raw and aggregated measurements, corrections, reports, and alarms. The lack of create/update/delete operations is acceptable for a monitoring-focused server, though alarm config is read-only and some reporting workflows are only partially surfaced.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues