Powerbeat

ai.powerbeatPublished by powerbeat.aiOfficial publisherv0.6.0Updated Oct 26, 2026

Home energy for AI assistants: live Power flow, Energy history, solar forecast, and device control.

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

Powerbeat is a remote MCP server that gives AI assistants live home energy data — power flow, energy history, solar forecast and device control.

What you can do
Read live power flow for the home's energy setup, showing how energy moves between sources and loads at the moment of the request. Look up energy history to review past consumption or production over time. Retrieve a solar forecast to plan around expected generation. Control connected devices through the assistant, subject to the account's permissions.
When to use it
Useful when you want an assistant to answer questions about current or past home energy use, plan around solar output, or act on connected devices without opening a separate app.
Requirements
A remote endpoint reached over streamable HTTP; no local package or runtime is needed. Sign-in is required through OAuth, so an account with the provider is needed. Network access to the hosted endpoint is required.
Before you install
The server can control devices, so assistant actions may change the state of physical equipment in the home. It exposes household energy data to the assistant and the provider. Review which devices are connected and what the account is allowed to control before granting access.

Installation

In SourceWeft

  1. Open Powerbeat in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.powerbeat%2Fpowerbeat/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "powerbeat": {
      "type": "http",
      "url": "https://mcp.powerbeat.ai/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

4
  1. v0.6.0LatestOct 26, 2026
  2. v0.4.0Oct 12, 2026
  3. v0.3.0Oct 9, 2026
  4. v0.2.0Oct 9, 2026

Score

67% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.