Ext Ops Panel
Open dashboard
Comparison

io.github.flowiesner/fronius-mcp vs Nrel

io.github.flowiesner/fronius-mcp is an MCP server published by flowiesner. Marketplaces we read that list it: 1 (Official MCP Registry). Nrel is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceio.github.flowiesner/fronius-mcpNrel
Official MCP Registry Listed
Version: 0.1.2
Downloads/month (PyPI): 80
Downloads/week (PyPI): 26
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

io.github.flowiesner/fronius-mcp vs Nrel
Factio.github.flowiesner/fronius-mcpNrel
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (fronius-mcp)Remote server (gateway.pipeworx.io/nrel/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/flowiesner/fronius-mcpgithub.com/pipeworx-io/mcp-nrel
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 404 (6 days ago)

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

io.github.flowiesner/fronius-mcp

In its own words, on Official MCP Registry:

Real-time Fronius inverter data in Claude — PV, battery, grid and smart meter via local Solar API.

Nrel

In its own words, on Official MCP Registry:

NREL MCP — wraps the US National Renewable Energy Laboratory developer API

How to run each

io.github.flowiesner/fronius-mcp As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio fronius-mcp -- uvx fronius-mcp

Nrel As a remote MCP server

Claude Code
claude mcp add --transport http nrel https://gateway.pipeworx.io/nrel/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Nrel has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: io.github.flowiesner/fronius-mcp · What it can do: Nrel · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built