Senlay Physical Context vs Carbon

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

Senlay Physical Context logoSenlay Physical ContextIndustrial & IoTPhysical-world evidence and operability checks with provenance and explicit data gaps.32EmergingAuth: not declaredCarbon 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.57GoodAuth: not declared

Verdict: choose Senlay Physical Context for industrial & iot work; 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?

Senlay Physical Context logoChoose Senlay Physical Context when

  • You need dedicated capabilities in the Industrial & IoT domain.
Explore Senlay Physical Context

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecSenlay Physical Context logoSenlay Physical ContextCarbon logoCarbon
CategoryIndustrial & IoTIndustrial & IoT
Quality signal32/100 · Emerging57/100 · Good
Install commandNot confirmed yetConfirmed
Transport—Remote HTTP/SSE
AuthNot declaredNot declared
PricingNot declaredFree
Required env varsNone listedCARBON_API_KEY
Verified ownerCommunity listingCommunity listing
GitHub stars02,758
Directory activity 4 views 0 installs 0 upvotes 5 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Senlay Physical Context 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.

Senlay Physical Context

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

Carbon

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

Frequently asked questions

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

Senlay Physical Context 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 senlay-physical-context and carbon-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Senlay Physical Context has a quality signal of 32/100 (Emerging) with 4 views, 0 installs and 0 GitHub stars. Carbon has 57/100 (Good) with 5 views, 0 installs and 2,758 GitHub stars.