Carbon vs Fronius MCP
A side-by-side look at the Carbon and Fronius MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Carbon for industrial & iot work; choose Fronius MCP for industrial & iot as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Carbon when
- You need dedicated capabilities in the Industrial & IoT domain.
- You have the keys it needs:
CARBON_API_KEY.
Choose Fronius MCP when
- You need dedicated capabilities in the Industrial & IoT domain.
- You prefer a local stdio subprocess transport.
- You want tools like
configure_inverter, solar_power_flow, solar_meter.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Industrial & IoT | Industrial & IoT |
| Quality signal | 52/100 · Good | 48/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Free | Not declared |
| Required env vars | CARBON_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2,756 | 1 |
| Directory activity | 4 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 5 |
| Full listing | View Carbon | View Fronius MCP |
Tools & capabilities
Carbon tools
No tool names declared yet. Check the project README from the listing page.
Fronius MCP tools 5
configure_inverterSet your inverter's IP address — run this once on first setupsolar_power_flowPV generation, grid exchange, house load, battery power, autonomy, energy totalssolar_meterGrid power per phase, cumulative energy in/out, voltage, current, frequencysolar_batteryState of charge, voltage, current, temperature, capacity, statussolar_devicesAll connected devices with type, bus index, and serial number
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Carbon
No confirmed install command for Carbon yet — follow the setup steps linked from its listing page rather than a guessed package name.
Fronius MCP
{
"mcpServers": {
"fronius-mcp": {
"command": "uvx",
"args": [
"fronius-mcp"
]
}
}
}
Frequently asked questions
Carbon is categorized under Industrial & IoT and uses an install path we have not confirmed yet. Fronius MCP belongs to Industrial & IoT and uses a local stdio subprocess. Pick Carbon for industrial & iot work and Fronius MCP for industrial & iot.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Carbon has no confirmed install command yet — follow its own setup instructions.
Carbon is listed as free. Fronius MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add carbon-2 and fronius-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Carbon has a quality signal of 52/100 (Good) with 4 views, 0 installs and 2,756 GitHub stars. Fronius MCP has 48/100 (Fair) with 1 views, 0 installs and 1 GitHub stars.