How do I install the apsystems mcp server?

Use a recorded configuration for your client, replace example credential values and paths, and verify the documented runtime. Restart or reconnect the client, then inspect the available tools.

What credentials does it need?

It reads `APS_SYS_ID`, `APS_APP_ID`, `APS_APP_SECRET`, `APS_MCP_TRANSPORT`, `APS_MCP_SSE_ADDR`, `APS_DASHBOARD`, `APS_DASH_ADDR`, `APS_BASE_URL` from the environment. Store these in your client's env block or a secrets manager — never commit them to a repository — and grant the narrowest scope that still covers your use case.

SSyncDev

Start a project

Apsystems MCP Server

A production-ready [Model Context Protocol](https://modelcontextprotocol.io/) (MCP) server written in Go that wraps the APsystems OpenAPI, giving AI

Local serverstdioGo

What is the Apsystems MCP Server?

A production-ready Model Context Protocol (MCP) server written in Go that wraps the APsystems OpenAPI, giving AI assistants like

What it actually does

16 MCP tools — covering all APsystems API endpoints: system details, energy summaries, ECU/inverter/meter/storage data
HMAC-SHA256 signature authentication — — implements the APsystems signature protocol
Built-in web dashboard — — dark-themed single-page app with Chart.js energy visualizations
Rate limiting — — configurable request throttling to respect API limits
Automatic retries — — exponential back-off on transient errors and rate-limit responses
Dual transport — — stdio (default) or SSE over HTTP, selectable via environment variable

More MCP options

Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.

Maintainer setup documentation.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

Tool	What it does
get_system_details	System info: capacity, timezone, ECUs, status
get_inverters	List all ECUs and connected micro-inverters
get_meters	List all meter IDs
get_system_summary	Energy totals: today, month, year, lifetime (kWh)
get_system_energy	Energy by period: hourly/daily/monthly/yearly
get_ecu_summary	Energy summary for a specific ECU
get_ecu_energy	Period energy for an ECU (supports minutely telemetry)
get_inverter_summary	Per-channel energy for a single inverter
get_inverter_energy	Period/minutely data with DC power, current, voltage, AC telemetry
get_inverter_batch_energy	All inverters under an ECU in one call
get_meter_summary	Consumed/exported/imported/produced totals
get_meter_period	Period energy data for a meter
get_storage_latest	Live status: SOC, charge/discharge power
get_storage_summary	Energy summary for a storage ECU
get_storage_period	Period energy data for storage

How to install the Apsystems MCP Server

{
  "mcpServers": {
    "apsystems": {
      "command": "podman",
      "args": [
        "run",
        "-i",
        "--rm",
        "-p",
        "8888:8080",
        "-e",
        "APS_DASHBOARD=true",
        "-e",
        "APS_SYS_ID=${input:aps_sys_id}",
        "-e",
        "APS_APP_ID=${input:aps_app_id}",
        "-e",
        "APS_APP_SECRET=${input:aps_app_secret}",
        "docker.io/mehdijrgr/apsystems-mcp-server"
      ]
    }
  }
}

From the project documentation. Replace placeholders and example paths before connecting.

Example prompts to try

“Use Apsystems to get system details.”
“Use Apsystems to get inverters.”
“Use Apsystems to get meters.”

Frequently asked questions

A production-ready [Model Context Protocol](https://modelcontextprotocol.io/) (MCP) server written in Go that wraps the APsystems OpenAPI, giving AI assistants like Confirm the tools offered by your installed version in the connected client. Tool availability and permissions depend on the server and account configuration.