Skip to main content
Glama
ffleurey

ha-analytics-mcp

by ffleurey

Related Servers

Alternatives to ha-analytics-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for InfluxDB 2.x, tuned for Home Assistant long-term storage, enabling reading sensor history, finding anomalies, and running Flux queries.
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for Home Assistant that lets you control and query your smart home through natural language via MCP clients. Provides tools for entities, devices, services, automations, scripts, history, add-ons, and system info, with read-only access by default and optional configurable write support.
      1
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Read-only MCP server for querying AI usage metrics (exact tokens, cost, latency, errors, productivity) from a local SQLite database, enabling charts and analysis in Claude Code and Cursor.
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enhanced Home Assistant MCP server with 22 context efficient tools for smart home control, automation trace debugging, entity registry management, CEL expression queries, and long-term statistics.
      22
      3
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      MCP server for chatting with physical-world data from robotics, drones, automotive, and IoT sources using natural language. It generates auditable SQL queries over Apache Arrow/DuckDB to let you analyze, summarize, and build data pipelines.
      25
      397
      Apache 2.0

    TDQS

    A4.4/5.0

    Scored across 10 tools

    Disambiguation3/5

    Multiple list tools (list_devices, list_device_entities, list_entities) overlap in returning entity_ids, and while descriptions offer guidance, the boundaries between device-centric and entity-centric discovery could confuse an agent. The analytics tools are well-separated by sensor type.

    Naming Consistency5/5

    All tools follow the ha_history_<verb>_<noun> pattern in snake_case, with verbs like list, get, and detect, making the set highly predictable and consistent.

    Tool Count5/5

    10 tools is well-scoped for a Home Assistant analytics server, covering discovery, state, statistics, history, and consumption without unnecessary bloat.

    Completeness5/5

    The tool set covers the full analytics workflow: discover areas/devices/entities, retrieve current state, compute stats, measure consumption, detect sessions, and inspect state history. No major gaps for the stated purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues