Log inSubmit server

Carbon vs Ros MCP

A side-by-side look at the Carbon and Ros MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Carbon logoCarbonIndustrial & IoT · Remote HTTP/SSEOpen-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.56GoodAuth: not declaredRos MCP logoRos MCPIndustrial & IoTMCP server that supports ROS2 topics, services, and actions communication, and controls robots using natural language.36FairAuth: no auth required

Verdict: choose Carbon for industrial & iot work over a hosted endpoint; choose Ros MCP for industrial & iot. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Carbon logoChoose 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.
Explore Carbon

Ros MCP logoChoose Ros MCP when

  • You need dedicated capabilities in the Industrial & IoT domain.
  • Its auth model fits you: No auth required.
  • You have the keys it needs: ROS_DOMAIN_ID, ROS_LOG_DIR.
Explore Ros MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecCarbon logoCarbonRos MCP logoRos MCP
CategoryIndustrial & IoTIndustrial & IoT
Quality signal56/100 · Good36/100 · Fair
Install commandConfirmedNot confirmed yet
TransportRemote HTTP/SSE—
AuthNot declaredNo auth required
PricingFreeFree
Required env varsCARBON_API_KEYROS_DOMAIN_IDROS_LOG_DIR
Verified ownerCommunity listingCommunity listing
GitHub stars2,75636
Directory activity 3 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
ToolsNot listedNot listed
Full listingView Carbon View Ros MCP

Tools & capabilities

Carbon tools

No tool names declared yet. Check the project README from the listing page.

Ros 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

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "carbon-2": {
      "url": "https://docs.carbon.ms/api/mcp"
    }
  }
}

Ros MCP

No confirmed install command for Ros MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

Carbon is categorized under Industrial & IoT and uses a remote HTTP/SSE transport. Ros MCP belongs to Industrial & IoT and uses an install path we have not confirmed yet. Pick Carbon for industrial & iot work and Ros 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. Ros MCP has no confirmed install command yet — follow its own setup instructions.

Carbon is listed as free. Ros MCP is listed as free. Auth: no auth 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 yutarop-ros-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 56/100 (Good) with 3 views, 0 installs and 2,756 GitHub stars. Ros MCP has 36/100 (Fair) with 4 views, 0 installs and 36 GitHub stars.

Popular comparisons with Carbon

Popular comparisons with Ros MCP