Carbon logo

Carbon

Permission-aware MCP access to Carbon’s manufacturing ERP, MRP, MES, QMS, inventory and traceability operations.

Install Carbon

Run the project’s own setup commands, in order.

Setup steps from the project

carbon installs with its own commands rather than a config we can generate, so these are copied as-is. Run them in order in a terminal. Source: github.com

  1. 1. Install
    git clone https://github.com/crbnos/carbon.git && cd carbon
    

Overview

The carbon MCP server exposes Carbon’s manufacturing operations to hosted or local AI agents. It uses the same authenticated operations as Carbon’s REST API, with access limited by the API key or signed-in user’s permissions. Carbon combines ERP, MRP, MES and QMS data in one Postgres-backed system covering planning, production, inventory, quality, costing and traceability. Reach for it when an agent needs to inspect or update manufacturing records through Carbon rather than through separate systems.

Use cases

  • Query manufacturing orders and inventory records
  • Inspect lot and serial genealogy
  • Plan materials against demand and supply
  • Update quality and production operations

Key features

  • Permission-aware MCP access
  • ERP, MRP, MES and QMS operations
  • Shared REST and MCP operation model
  • Lot and serial traceability
  • Self-hosted or Carbon Cloud deployment

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

34/34 checks healthy over the last 23d

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars2.8kStargazers on the source repository.
Last commitTodayMost recent push to the default branch.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How Carbon works

What carbon does

The carbon MCP server gives AI agents access to operations in Carbon, an open-source manufacturing platform combining enterprise resource planning, material requirements planning, manufacturing execution and quality management. Carbon stores these areas in one Postgres schema, so engineering, planning, production, quality and accounting work from shared records.

The server is intended for manufacturing workflows such as quoting, sales orders, purchasing, inventory, invoicing, job costing, material planning, production execution, quality management and lot or serial traceability. It also exposes capabilities related to bills of materials, routings, revisions, configuration, workflows, maintenance and assets. The available operation set follows Carbon’s API rather than presenting a separate data model.

This listing belongs to the Industrial & IoT category and is relevant to teams building agent workflows around production data, shop-floor execution or manufacturing administration.

How it works

Carbon provides the same manufacturing operations through HTTP and MCP interfaces. MCP presents those operations as tools for hosted or local AI agents, while HTTP exposes them through POST requests under /api/v1/{module}/{operation}. The API has a published OpenAPI specification for typed client generation, and both interfaces use the same arguments.

Each operation validates its input, updates dependent records and checks the permissions of the authenticated identity. Access is therefore tied to the API key or signed-in user used by the connection. Carbon also applies tenant-scoped records, row-level security and role- or attribute-based access controls across its application, API and MCP server.

The carbon MCP server can be used with Carbon Cloud or with a self-hosted deployment. Self-hosted installations expose the same API beneath /api/v1, allowing the deployment to run in a company VPC, on-premises environment or air-gapped network.

Setup and configuration

Create an API key in Carbon under Settings → API Keys, then authenticate requests with the key. The documented HTTP example uses the CARBON_API_KEY environment variable as a bearer token. MCP connections are scoped to the permissions of that key or to the signed-in user, so the selected identity determines which records and operations an agent can use.

Carbon is available as a managed cloud application or as a self-hosted installation. Cloud provides the managed application, database, updates and backups.

Tools and capabilities

The carbon MCP server provides permission-aware access to Carbon API operations across areas including:

  • Quotes, sales orders, purchasing, inventory, invoicing and actual job costs
  • Demand and supply planning, versioned bills of materials, routings and finite-capacity scheduling
  • Digital travelers, operator terminals, 3D work instructions, barcode capture and labor capture
  • Inspections, first article inspection, nonconformance, corrective and preventive action, calibration and risk management
  • Forward and backward lot and serial genealogy
  • Engineering revisions, change orders, supersession and product configuration
  • Rule-based workflows, scheduled maintenance, fixed assets and kanban replenishment

The surrounding Carbon platform also lists integrations with Onshape, SolidWorks, Paperless Parts, Linear, Jira, Slack, Ramp, Stripe and Zebra.

Limitations and notes

The carbon MCP server is permission-aware, so an agent cannot be assumed to have unrestricted access to Carbon data. Its available actions depend on the API key or signed-in user and the deployment’s access controls.

Review Carbon’s MCP documentation before connecting a particular agent client. Carbon is licensed under AGPL-3.0.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Carbon

carbon is an MCP server that connects AI agents to Carbon’s manufacturing ERP, MRP, MES and QMS platform. Its main tools expose authenticated operations for inventory, planning, production, quality, costing, bills of materials and lot or serial traceability. Access follows the permissions of an API key or signed-in Carbon user.

Create an API key under Settings → API Keys and configure the connection according to Carbon’s MCP documentation. Self-hosted deployments provide the same API beneath `/api/v1`.

Authenticate with a Carbon API key or a signed-in Carbon user. The documented API example stores the key in `CARBON_API_KEY` and sends it as a bearer token. MCP access is restricted to the permissions associated with that identity.

It states that Carbon MCP is available to hosted or local AI agents, but it does not document client-specific configuration or compatibility.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewCarbon AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/carbon-2?style=directory)](https://allmcps.com/mcp/carbon-2)
HTML Embed
<a href="https://allmcps.com/mcp/carbon-2"><img src="https://allmcps.com/api/badge/carbon-2?style=directory" alt="Carbon on AllMCPs" /></a>