Fronius MCP vs Carbon
A side-by-side look at the Fronius MCP and Carbon MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Fronius MCP for industrial & iot work as a local process; choose Carbon for industrial & iot over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
Choose Carbon when
- You need dedicated capabilities in the Industrial & IoT domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
CARBON_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Industrial & IoT | Industrial & IoT |
| Quality signal | 48/100 · Fair | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Free |
| Required env vars | None listed | CARBON_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 2,758 |
| Directory activity | 1 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 5 | Not listed |
| Full listing | View Fronius MCP | View Carbon |
Tools & capabilities
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
Carbon tools
No tool names declared yet. Check the project README from the listing page.
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.
Fronius MCP
{
"mcpServers": {
"fronius-mcp": {
"command": "uvx",
"args": [
"fronius-mcp"
]
}
}
}
Carbon
{
"mcpServers": {
"carbon-2": {
"url": "https://docs.carbon.ms/api/mcp"
}
}
}
Frequently asked questions
Fronius MCP is categorized under Industrial & IoT and uses a local stdio subprocess. Carbon belongs to Industrial & IoT and uses a remote HTTP/SSE transport. Pick Fronius MCP for industrial & iot work and Carbon 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.
Fronius MCP has no declared pricing — check the project's own site. Carbon is listed as free. 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 fronius-mcp and carbon-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Fronius MCP has a quality signal of 48/100 (Fair) with 1 views, 0 installs and 1 GitHub stars. Carbon has 57/100 (Good) with 5 views, 0 installs and 2,758 GitHub stars.