Carbon vs OctoEverywhere MCP
A side-by-side look at the Carbon and OctoEverywhere MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
C
CarbonIndustrial & IoTOpen-source manufacturing ERP, MES and QMS. Quoting, MRP, inventory, shop floor, quality and lot/serial traceability on one Postgres schema, with a REST API and MCP server. Self-host or use Carbon Cloud.51GoodAuth: not declaredVerdict: choose Carbon for industrial & iot work; choose OctoEverywhere MCP 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?
CChoose Carbon when
- You need dedicated capabilities in the Industrial & IoT domain.
- You have the keys it needs:
CARBON_API_KEY.
Choose OctoEverywhere MCP when
- You need dedicated capabilities in the Industrial & IoT domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | C Carbon | |
|---|---|---|
| Category | Industrial & IoT | Industrial & IoT |
| Quality signal | 51/100 · Good | 41/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | Not declared | API key required |
| Pricing | Free | Free |
| Required env vars | CARBON_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2,737 | 38 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Carbon | View OctoEverywhere MCP |
Tools & capabilities
Carbon tools
No tool names declared yet. Check the project README from the listing page.
OctoEverywhere MCP 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.
Carbon
No confirmed install command for Carbon yet — follow the setup steps linked from its listing page rather than a guessed package name.
OctoEverywhere MCP
{
"mcpServers": {
"octoeverywhere-mcp": {
"url": "https://octoeverywhere.com/mcp?utm_campaign=mcp_repo&utm_content=header&utm_source=github"
}
}
}
Frequently asked questions
Carbon is categorized under Industrial & IoT and uses an install path we have not confirmed yet. OctoEverywhere MCP belongs to Industrial & IoT and uses a remote HTTP/SSE transport. Pick Carbon for industrial & iot work and OctoEverywhere 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. OctoEverywhere MCP is listed as free. Auth: api key required. 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 octoeverywhere-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 51/100 (Good) with 0 views, 0 installs and 2,737 GitHub stars. OctoEverywhere MCP has 41/100 (Fair) with 3 views, 0 installs and 38 GitHub stars.