octopus-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OCTOPUS_EMAIL | No | Optional email for some Kraken queries. | |
| OCTOPUS_API_KEY | Yes | Your Octopus Energy API key from developer settings. | |
| OCTOPUS_PASSWORD | No | Optional password for some Kraken queries. | |
| OCTOPUS_ACCOUNT_NUMBER | Yes | Your Octopus Energy account number (e.g., A-XXXXXXXX). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bill_summaryC | Total cost (£/pence) per fuel for a period |
| current_tariffB | Currently active tariff per fuel |
| usage_breakdownC | Aggregated kWh by hour/day/week/month |
| peak_hoursC | Top-N highest-usage half-hours |
| compare_tariffC | Replay actual usage against another Octopus tariff |
| get_accountA | Account details + meters + tariff history |
| list_productsB | Browse Octopus product catalogue |
| get_productB | Detail for one product code |
| get_consumption_rawC | Half-hourly consumption rows for a meter |
| saving_session_historyC | Octoplus saving sessions joined and points/kWh earned |
| kraken_queryC | Escape hatch: run an arbitrary Kraken GraphQL query |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool targets a distinct aspect: billing, tariffs, account details, consumption data, product catalog, and saving sessions. The only potential overlap is between get_consumption_raw and usage_breakdown, but they differ in granularity (raw vs aggregated). kraken_query is clearly a fallback.
Tools follow snake_case, but verb placement varies: some start with verbs (compare_tariff, get_account), others with nouns (bill_summary, peak_hours). Still, all names are descriptive and readable, with no mixing of conventions.
11 tools cover account management, tariffs, consumption, billing, and saving sessions without overwhelming. Each tool serves a clear purpose, and the count feels right for an energy provider MCP server.
Core operations (account info, tariff details, consumption data, billing) are covered. Missing features like tariff switching or payment actions may be addressed by the kraken_query escape hatch, but the primary user needs are met.