No listening port
Runs as a local stdio process and communicates directly with the MCP client.
Query and analyse an Octopus Energy account through a local MCP server designed to keep credentials and energy data on your machine.
Privacy by design
The server runs locally, exposes named read-only Octopus operations and puts clear limits around network access, caching and potentially destructive maintenance.
Runs as a local stdio process and communicates directly with the MCP client.
Authenticated energy requests are limited to the Octopus API, with automatic redirects disabled.
Repeatable responses can be cached locally using private files and hashed filenames.
Queueing, rate limits, pagination caps and retry controls protect both the account and the upstream API.
What it can do
Install locally
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.
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