Lumenhaus Energy

io.github.zhuyu1022Published by GitHub account zhuyu1022v0.1.0Updated Oct 25, 2026

Read-only MCP server for Lumenhaus Energy sites, devices, charging sessions, and energy history.

VerifiedSTDIODesktop onlyFinanceData & Analytics

Overview

AI-generated overview

A read-only local MCP server that lets an assistant look up Lumenhaus Energy sites, devices, charging sessions and energy history.

What you can do
Read-only access to Lumenhaus Energy account data, covering sites, devices, charging sessions and energy history. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Useful when you want an assistant to answer questions about your Lumenhaus Energy sites, devices, charging sessions or past energy use without opening the vendor's interface.
Requirements
Runs locally via npx (Node.js). Requires the LUMENHAUS_API_BASE_URL environment variable and a short-lived Lumenhaus bearer token in LUMENHAUS_ACCESS_TOKEN. Desktop only; network access to the Lumenhaus API is needed.
Before you install
The server needs a bearer access token in LUMENHAUS_ACCESS_TOKEN, which grants access to your Lumenhaus account data; keep it out of logs and shared configuration. The token is described as short-lived, so expect to refresh it. The manifest declares read-only access, but the individual tools are not listed, so verify what it can reach.

Installation

In SourceWeft

  1. Open Lumenhaus Energy in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestOct 14, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.