MCP server for Octopus Energy account analysis
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"octopus-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# octopus-mcp > Unofficial. Not affiliated with Octopus Energy. Uses the public REST API and the community-known Kraken GraphQL endpoint; the latter is unofficial and may break without notice. A Model Context Protocol server that lets Claude analyse your Octopus Energy account: usage, costs, tariff comparisons, Saving Sessions, Octoplus rewards. Works with **Claude Code**, **Claude Desktop**, and any MCP-compatible client. ## Install ### Claude Code (recommended) ```bash # 1. Install the MCP server uv tool install octopus-mcp # 2. Save your credentials in your OS keychain octopus-mcp configure # 3. Install the plugin from this repo (in Claude Code): /plugin install DanielChicot/octopus-mcp ``` ### Claude Desktop / Cursor / other MCP clients Install the server, configure credentials, then add to your MCP client config: ```json { "mcpServers": { "octopus": { "command": "uvx", "args": ["octopus-mcp"] } } } ``` For Claude Desktop, the config lives at `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS). ## Credentials You need: - `OCTOPUS_API_KEY` — find at [octopus.energy → My account → Personal details → Developer settings](https://octopus.energy/dashboard/new/accounts/personal-details/api-access) - `OCTOPUS_ACCOUNT_NUMBER` — `A-XXXXXXXX`, on any bill or in your account Optional (only some Kraken queries): - `OCTOPUS_EMAIL` / `OCTOPUS_PASSWORD` Resolution order: shell env > `.env` > OS keyring > error. The recommended path is `octopus-mcp configure` which writes to the OS keyring so secrets never sit in plaintext config. ## Tools | Tool | What it does | |---|---| | `bill_summary(period)` | Total kWh and £ per fuel for a period | | `usage_breakdown(period, group_by)` | Aggregated kWh by hour/day/week/month | | `peak_hours(period, top_n)` | Top-N highest-usage half-hours | | `compare_tariff(target_product_code, period, fuel)` | Replay your usage against another Octopus tariff | | `current_tariff()` | What…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.