# carbon [Health: Active]

**Category:** 🏭 Industrial & IoT  
**Repository:** https://github.com/crbnos/carbon  
**GitHub Stars:** 2737  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/carbon-2

## Description
Open-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.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What carbon MCP server does

The carbon MCP server connects AI agents to Carbon, an open-source manufacturing platform combining ERP, MRP, MES and QMS functions. It gives agents access to the same manufacturing operations used by the Carbon application and REST API, rather than exposing an unrelated automation layer.

Carbon stores engineering, planning, production, quality and accounting data in one Postgres schema. Depending on the operations available to the authenticated identity, an agent can work with areas such as quotes, sales orders, purchasing, inventory, invoicing, job costs, bills of materials, routings, scheduling, shop-floor execution, inspections, nonconformance, CAPA, maintenance, assets and lot or serial traceability.

This places the carbon MCP server in the Industrial & IoT category for teams that want an AI interface to manufacturing records and workflows.

## How it works

Carbon exposes its operations through both HTTP and MCP. The interfaces use the same arguments, while each operation validates its input, updates dependent records and checks the permissions of the authenticated user or API key.

For hosted deployments, the API is available under the Carbon application domain. Self-hosted deployments provide the same API at `/api/v1`. MCP access is scoped to the permissions associated with the API key or signed-in user, so the agent does not automatically receive unrestricted access to the company’s data.

Carbon’s shared identity and permissions apply across the application, API and MCP server. Its underlying platform also supports tenant-scoped records, row-level security, role- and attribute-based access, and realtime database subscriptions.

## Setup and configuration

Create an API key from **Settings → API Keys** when connecting through an authenticated API workflow. Carbon’s documentation shows the key supplied as a Bearer token in the `Authorization` header; the example uses a `CARBON_API_KEY` environment variable.

Organizations can use Carbon Cloud, which provides the managed application, database, updates and backups, or deploy Carbon themselves in a VPC, on-premises environment or air-gapped network. The repository also supports local development from source. The supplied material does not specify a separate MCP client configuration file, command, or local server launch procedure.

## Tools and capabilities

The carbon MCP server exposes Carbon manufacturing operations as agent tools. Supported business areas documented for Carbon include:

- Quoting, sales orders, purchasing, inventory and invoicing
- Material demand and supply planning
- Versioned bills of materials, routings and finite-capacity scheduling
- Digital travelers, operator terminals, work instructions, barcode and labor capture
- Inspections, FAI, nonconformance, CAPA, calibration and risk management
- Forward and backward lot and serial genealogy
- Revisions, change orders, supersession and product configuration
- General ledger, journals, multi-entity and multi-currency accounting
- Scheduled maintenance, fixed assets and kanban replenishment

The carbon MCP server uses Carbon’s permission-aware operation model, so the usable tool surface depends on the identity making the request.

## Limitations and notes

The README does not list individual MCP tool names, schemas, supported prompts, resources, transport details or client-specific setup instructions. Confirm those details in Carbon’s MCP documentation before building an integration around a particular operation.

Access is limited by the authenticated identity’s permissions. API and MCP requests therefore may not expose every manufacturing module or record to every agent. Carbon can be used as a hosted service or self-hosted, but deployment, backup and update responsibilities differ between those options.

_Full upstream README: https://allmcps.com/mcp/carbon-2/readme_