Arcnm vs Carbon
A side-by-side look at the Arcnm and Carbon MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
A
ArcnmIndustrial & IoT · Remote HTTP/SSEManufacturing should-cost from CAD and drawings: cost drivers, process plan, lot sizes.39FairAuth: no auth requiredC
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 Arcnm for industrial & iot work over a hosted endpoint; choose Carbon for industrial & iot. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
AChoose Arcnm when
- You need dedicated capabilities in the Industrial & IoT domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
CChoose Carbon when
- You need dedicated capabilities in the Industrial & IoT domain.
- You have the keys it needs:
CARBON_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | A Arcnm | C Carbon |
|---|---|---|
| Category | Industrial & IoT | Industrial & IoT |
| Quality signal | 39/100 · Fair | 51/100 · Good |
| Install command | Confirmed | Not confirmed yet |
| Transport | Remote HTTP/SSE | — |
| Auth | No auth required | Not declared |
| Pricing | Not declared | Free |
| Required env vars | None listed | CARBON_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 2,737 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Arcnm | View Carbon |
Tools & capabilities
Arcnm tools
No tool names declared yet. Check the project README from the listing page.
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.
Arcnm
{
"mcpServers": {
"arcnm": {
"url": "https://arcnm.io/docs/mcp"
}
}
}
Carbon
No confirmed install command for Carbon yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Arcnm is categorized under Industrial & IoT and uses a remote HTTP/SSE transport. Carbon belongs to Industrial & IoT and uses an install path we have not confirmed yet. Pick Arcnm 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. Carbon has no confirmed install command yet — follow its own setup instructions.
Arcnm has no declared pricing — check the project's own site. Auth: no auth required. 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 arcnm and carbon-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Arcnm has a quality signal of 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Carbon has 51/100 (Good) with 0 views, 0 installs and 2,737 GitHub stars.