Skip to main content
Glama
darronz

Octopus Energy MCP Server

by darronz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Octopus Energy MCP Server

No user-submitted related servers found.

    Related Servers

    • mcp-octopus-energy

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to query UK energy tariffs and products via the Octopus Energy public API.
      2 npm
      MIT

    • mcp-carbon

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables users to query current and historical UK electricity carbon intensity, generation mix, and regional intensity data to schedule energy-intensive tasks during low-carbon periods.
      309 npm
      MIT
    • mcp-neso by pipeworx-io

      mcp-nesoofficial

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Access Great Britain electricity grid open data from the NESO API, enabling queries about generation, demand, and market data.
      185 npm
      MIT

    • mcp-elexon

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables access to Great Britain electricity grid and market data via the Elexon BMRS Insights API.
      149 npm
      MIT

    • Datadis MCP Server

      Jaimegruiz
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to access and analyze Spanish electricity consumption data via the Datadis API, providing tools for supply management, consumption analysis, anomaly detection, and executive reporting.
      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.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are clearly distinct: one retrieves electricity consumption data and the other retrieves gas consumption data. Their purposes do not overlap, and the descriptions specify different parameters and units, making misselection unlikely.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern with 'get_' prefix and descriptive nouns ('electricity_consumption', 'gas_consumption'). The naming is uniform and predictable across the set.

    Tool Count2/5

    With only 2 tools, the server feels thin for an energy data domain. While it covers electricity and gas consumption, typical energy APIs might include additional operations like tariff lookup, usage analysis, or billing information, suggesting a limited scope.

    Completeness2/5

    The toolset is severely incomplete for an energy data server. It only provides consumption retrieval, lacking essential operations such as tariff queries, historical data analysis, account management, or update capabilities, which could hinder agent workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources