Skip to main content
Glama
prestonmcgowan

tesla-powerwall

by prestonmcgowan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to tesla-powerwall

No user-submitted related servers found.

    Related Servers

    • victron-tcp

      lubosstrejcek
      A
      license
      A
      quality
      A
      maintenance
      Connect AI assistants to Victron Energy systems to read real-time solar, battery, grid, and inverter data from your local network via Modbus TCP or MQTT.
      32
      13 npm
      3
      MIT

    • Tesla MCP Server

      MyTeslaMate
      A
      license
      Not graded
      quality
      C
      maintenance
      Integrates with Tesla Fleet API and TeslaMate API to control vehicles, monitor energy (Powerwall/Solar), manage charging, and analyze driving data, with generative UI and skill workflows.
      3
      MIT

    • Home Assistant MCP Server

      mjrestivo16
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Home Assistant smart home devices through natural language. Control devices, manage automations, query entity states, and retrieve historical data across your home automation system.
      1
      MIT

    • homey-mcp

      tim661811
      A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to control a Homey Pro smart home hub, create automation flows from natural language, and query device and energy history.
      36
      15 npm
      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.2/5.0

    Scored across 18 tools

    Disambiguation3/5

    Most tools map to distinct resources, but several read-only getters overlap in purpose, such as get_status vs get_system_status and get_meters vs get_meters_aggregates. An agent may struggle to choose between status-related endpoints without deeper API knowledge.

    Naming Consistency5/5

    All tools use a consistent powerwall_ prefix with snake_case verb_noun names. The only non-get tools are login, logout, and set_operation, which clearly follow the same predictable action-based pattern.

    Tool Count4/5

    18 tools is on the heavier side but appropriate for a Powerwall gateway server that exposes many distinct API resources. Each tool appears to represent a real endpoint, so the count is justified rather than bloated.

    Completeness4/5

    The server covers authentication, status, meters, battery state, grid status, operation settings, configuration, and installer details. The main gap is limited write operations beyond setting operation mode, but for monitoring and basic control the surface is largely complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources