No listening port
Runs as a local stdio process and communicates directly with the MCP client.
Project / 01 Open source · public preview
Octopus Energy Private MCP.
Query and analyse an Octopus Energy account through a local MCP server designed to keep credentials and energy data on your machine.
Added
Tools21
RuntimeNode.js 22+
LanguageTypeScript
TransportLocal stdio
LicenceMIT
Privacy by design
Local by default.
The server runs locally, exposes named read-only Octopus operations and puts clear limits around network access, caching and potentially destructive maintenance.
Restricted outbound access
Authenticated energy requests are limited to the Octopus API, with automatic redirects disabled.
Private local cache
Repeatable responses can be cached locally using private files and hashed filenames.
Bounded requests
Queueing, rate limits, pagination caps and retry controls protect both the account and the upstream API.
What it can do
Questions the server can answer.
- 01Analyse electricity usage and identify peak times or missing readings.
- 02Find the cheapest contiguous windows on an Agile tariff.
- 03Replay actual consumption against exact tariff codes.
- 04Inspect meters, active agreements, smart devices and planned dispatches.
- 05Check an Octoplus balance and current API rate-limit status.
Install locally
Install it on your own machine.
You will need Node.js 22 or newer, an Octopus Energy API key and your account number. The beginner guide covers Mac, Windows and Linux, including ChatGPT desktop and Codex setup.
Credentials are never entered on this website.
They are configured only on the computer that runs the MCP server.
# Download and prepare the server
git clone https://github.com/soothill/octopus-energy-private-mcp.git
cd octopus-energy-private-mcp
npm ci
cp .env.example .env
# Add your credentials locally, then build
npm run build
npm startOctopus Energy Private MCP is an independent community project. It is not affiliated with or endorsed by Octopus Energy.
Source, tests and documentation