octopus-mcp
Related Servers
Alternatives to octopus-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceUnofficial MCP server for Hive (British Gas) smart heating. Lets Claude and other AI assistants check your thermostats, radiator valves, hot water, plugs and lights and, if you allow it, boost the heating, set temperatures, switch on the hot water and set holiday mode. Read-only by default, with an optional audit log of every change. Runs in Docker or as a one-click Claude Desktop bundle.26MIT
- AlicenseAqualityDmaintenanceAn unofficial MCP (Model Context Protocol) server that exposes a Vaillant heat pump's data to AI assistants like Claude. Query outdoor and room temperatures, hot water status, energy consumption, COP estimates, schedules, and diagnostics through natural conversation.4MIT
- AlicenseAqualityDmaintenanceAn MCP server that enables any AI agent to call Claude using your existing Max/Pro subscription via OAuth, avoiding additional API billing.11MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for EmonCMS energy monitoring API, enabling AI assistants to query energy feeds, inputs, and historical data.1MIT
- AlicenseAqualityDmaintenanceAn MCP server for the Octopus Energy Japan GraphQL API that allows users to retrieve electricity consumption, cost estimates, and contract details. It enables 30-minute interval usage analysis and postal code area searches while ensuring privacy by excluding personal address information.314 npm1MIT
- AlicenseBqualityDmaintenanceMCP server combining TeslaMate historical analytics with Fleet API live data and commands. Works with Claude Code, Claude Desktop, Cursor, and any MCP-compatible client.292MIT
TDQS
Scored across 20 tools
Tools are largely distinct, and several descriptions explicitly cross-reference their neighbours (plan_schedule explains how it differs from find_cheapest_slots). The main soft spots are the three slot-finding tools (find_cheapest_slots, find_greener_slots, plan_schedule) and the overlapping price/overview tools (get_product vs get_unit_rates, get_balance vs get_account), but the descriptions give enough detail to choose correctly.
Every tool uses the octopus_ prefix plus a consistent snake_case verb_noun pattern (find_region, get_consumption, list_bills, plan_schedule, compare_tariffs). The small number of verbs (find, get, list, plan, compare) is used uniformly and predictably.
20 tools is on the heavy side but is justified by a broad domain spanning accounts, tariffs, consumption, solar, devices, rewards and scheduling. Each tool maps to a distinct API area, though it sits at the upper edge of comfortable scope.
Read/analysis coverage is excellent: account overview, balance, bills, transactions, consumption, live usage, solar, tariff pricing, comparison, scheduling and Octoplus rewards are all present, plus a postcode-to-region helper. Gaps are on the action side — no submitting meter readings and no way to actually join a Saving Session or execute a schedule, only retrieve its join code.