Aiseg2 MCP logo

Aiseg2 MCP

Read-only MCP access to live power, circuit, daily, historical, and cost data from a Panasonic AiSEG2 controller.

Install Aiseg2 MCP

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "aiseg2-mcp": {
      "command": "uvx",
      "args": [
        "aiseg2-mcp"
      ],
      "env": {
        "AISEG_URL": "YOUR_VALUE_HERE",
        "AISEG_PASSWORD": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The aiseg2-mcp MCP server connects an MCP client to a Panasonic AiSEG2 HEMS controller through its local web interface. It reads live power flow, circuit measurements, circuit names, daily totals, and longer-term energy and cost history from the controller's SD-card export. Use it when an agent needs household energy data without changing device settings. The project was tested with AiSEG2 MKN713-series hardware and firmware Ver.2.97I-01, so other models or firmware may produce parsing errors.

Use cases

  • Inspect current household power flow
  • Identify the circuits using the most electricity
  • Query daily generation and grid totals
  • Analyze historical energy exports
  • Review historical energy costs

Key features

  • Read-only AiSEG2 web-interface access
  • Live power-flow and battery readings
  • Per-circuit consumption and circuit-name lookup
  • Daily energy totals
  • Paginated energy and cost history
  • Stdio and streamable-HTTP transports

Tools6

What Aiseg2 MCP lets your agent do. Expand a tool for its parameters.

Self-reported~207 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

9/9 checks healthy over the last 48d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 7d ago via OSV.dev · aiseg2-mcp (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

Last commit3d agoMost recent push to the default branch.
Tools exposed6Callable tools this server registers over MCP.

How Aiseg2 MCP works

What aiseg2-mcp MCP server does

The aiseg2-mcp MCP server exposes read-only energy data from a Panasonic AiSEG2 home energy management controller. It is intended for MCP clients that need to inspect household electricity information through the controller's local web interface, rather than operate or configure the device.

Live tools report current generation and consumption in kW, whether electricity is being bought or sold, battery state, generation sources, and the circuits using the most power. Circuit data can also be returned for every measured circuit in watts, ordered from highest consumption to lowest. A separate listing provides the registered circuit IDs and names used by the controller.

Daily totals cover cumulative generation, consumption, grid purchases, and grid sales for the current day. Historical tools read the AiSEG2's SD-card export and return energy measurements in Wh or energy costs in JPY.

How it works

The server authenticates to the AiSEG2 web interface with HTTP Digest authentication and reads the pages and export data needed by its tools. It does not expose device-control operations: the tools are marked read-only, and the implementation does not use the controller's action endpoints. Each result includes an as_of timestamp in UTC showing when the live value was read or when the history export was downloaded.

get_history supports 30-minute, hourly, daily, monthly, and yearly data. It accepts date ranges appropriate to the selected granularity, optional metric and circuit filters, and limit/offset pagination. get_cost_history supports daily, monthly, and yearly cost data with date ranges and pagination.

The history export is cached after download. The first history request may therefore be slower, while later requests can reuse the cached file until its configured time-to-live expires. An SD card must be inserted in the AiSEG2 for either history tool to work.

Setup and configuration

Run the package with uvx, from source with Python 3.12+ and uv, or as the published GHCR container. Set AISEG_URL to the controller's HTTP base URL and AISEG_PASSWORD to its Digest-auth password. AISEG_USER defaults to aiseg.

The package defaults to stdio transport. The container defaults to streamable HTTP on port 8000, with the MCP endpoint at /mcp and a health endpoint at /health. Transport, bind host, port, cache directory, cache lifetime, and log level can be changed with the documented environment variables.

Tools and capabilities

  • get_power_flow: reads instantaneous flow, battery state, buying or selling state, sources, and top-consuming circuits.
  • get_circuit_breakdown: returns measured circuit loads and their total, ranked by watts.
  • list_circuits: returns the controller's registered circuit IDs and names.
  • get_daily_totals: returns today's cumulative energy figures.
  • get_history: queries long-term energy export data with granularity, filters, and pagination.
  • get_cost_history: queries long-term cost export data in JPY.

Limitations and notes

The aiseg2-mcp MCP server is unofficial and is not affiliated with Panasonic. Its web-interface parsing was verified against MKN713-series AiSEG2 devices running firmware Ver.2.97I-01; undocumented page changes on other versions may cause tools to fail.

The AiSEG2 and server are designed for a trusted LAN because the controller uses plain HTTP. A streamable-HTTP deployment has no built-in authentication and should be placed behind an authenticating reverse proxy before being exposed beyond a trusted network. Keep AISEG_DISABLE_DNS_REBINDING_PROTECTION disabled unless that proxied arrangement is in use.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Aiseg2 MCP

aiseg2-mcp is an MCP server that connects MCP clients to a Panasonic AiSEG2 HEMS controller over its local web interface. Its main tools read live power flow, circuit consumption and names, daily totals, SD-card energy history, and energy-cost history. It is unofficial and read-only.

Install it with uvx, run it from source, or use the GHCR Docker image. The source option requires Python 3.12+ and uv. Set AISEG_URL and AISEG_PASSWORD before starting the package or container.

Yes, aiseg2-mcp can be added to Claude Code with its stdio uvx command and the AISEG_URL and AISEG_PASSWORD environment variables. The README provides a `claude mcp add` example.

Only the history tools require an SD card. `get_history` and `get_cost_history` read the AiSEG2's SD-card CSV export, while live power, circuit, and daily-total tools read the controller's web interface.

Yes, all exposed tools are read-only. The server reads the AiSEG2 interface and uses only the display-refresh POST behavior used by the web UI; it does not change settings or call action endpoints.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewAiseg2 MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/aiseg2-mcp?style=directory)](https://allmcps.com/mcp/aiseg2-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/aiseg2-mcp"><img src="https://allmcps.com/api/badge/aiseg2-mcp?style=directory" alt="Aiseg2 MCP on AllMCPs" /></a>