Carbon MCP
Enables developers and designers to work with the Carbon Design System through tools for generating components, applying codemods, validating accessibility, converting design tokens, and searching documentation.
README
carbon-mcp
Local MCP (Model Context Protocol) server for the Carbon Design System — Advanced MVP for internal demos and production use.
🚧 Status: Proposal Submitted to Carbon
This project is a proposal submitted to the Carbon Design System repository.
- Issue: #20855
- Status: Awaiting maintainer feedback
- Proposed: Add to Carbon monorepo or create official
carbon-design-system/carbon-mcprepository
The Carbon team is reviewing this proposal. Once feedback is received, the code will be adapted accordingly.
🚀 Quickstart
-
Clone repo
git clone https://github.com/SandeepBaskaran/carbon-mcp.git cd carbon-mcp -
Install dependencies
npm install # or pnpm install -
Configure environment (optional)
cp .env.example .env # Edit .env to add API keys if needed (FIGMA_TOKEN, GITHUB_TOKEN) -
Start the server
npm run devServer will start on
http://localhost:4000 -
Test it out
# List available tools curl http://localhost:4000/tools # Generate a component (dry-run) curl -X POST http://localhost:4000/tool/generateComponent \ -H "Content-Type: application/json" \ -d '{"component_name": "PrimaryCard", "dry_run": true}'
🛠️ Tools (MVP)
Developer Tools
generateComponent— Generate Carbon React component + Storybook story + tests (dry-run default)codemodReplace— Apply codemods to convert existing components to Carbon equivalents (dry-run default)validateComponent— Validate component against Carbon patterns and accessibility guidelinestokenConverter— Convert design tokens (JSON) to CSS variables, SCSS maps, and JS tokens
Documentation Tools
searchDocs— Search local Carbon docs index with semantic/keyword matching
Designer Tools
themePreview— Generate static HTML previews for Carbon theme variants (light/dark/custom)figmaSync— Scaffold for Figma token sync (requires FIGMA_TOKEN in environment)
🔒 Safety & Destructive Operations
All destructive changes (writing to disk, modifying files) require:
confirm_destructive: truedry_run: false
Recommended workflow:
- Run with
dry_run: true(default) to preview changes - Review the output/patches
- Run again with
dry_run: falseandconfirm_destructive: trueto apply
Example: Generate Component (Safe Workflow)
# Step 1: Dry-run to preview
curl -X POST http://localhost:4000/tool/generateComponent \
-H "Content-Type: application/json" \
-d '{
"component_name": "PrimaryCard",
"dry_run": true,
"explain": true
}'
# Step 2: Apply changes
curl -X POST http://localhost:4000/tool/generateComponent \
-H "Content-Type: application/json" \
-d '{
"component_name": "PrimaryCard",
"dry_run": false,
"confirm_destructive": true
}'
📚 API Reference
Endpoints
| Method | Endpoint | Description |
|---|---|---|
| GET | /health |
Health check |
| GET | /tools |
List all available tools |
| GET | /tool/:name/schema |
Get schema for specific tool |
| POST | /tool/:name |
Execute a tool |
Tool Examples
1. Generate Component
POST /tool/generateComponent
{
"component_name": "PrimaryCard",
"props": {
"compact": "boolean",
"icon": "string"
},
"target_path": "src/components/PrimaryCard",
"dry_run": true,
"explain": true
}
Response:
{
"files": [
{
"path": "src/components/PrimaryCard/PrimaryCard.tsx",
"content": "import React from 'react'..."
}
],
"changed_files": [],
"dry_run": true,
"logs": [...],
"trace_id": "genc-1234567890",
"explanation": "Generated Carbon React component..."
}
2. Codemod Replace
POST /tool/codemodReplace
{
"codemod_name": "btn-old-to-carbon",
"files_glob": "src/**/*.{tsx,jsx}",
"dry_run": true
}
Response:
{
"dry_run_result": "3 files would be modified",
"patches": [
{
"file": "src/pages/Home.tsx",
"patch": "@@ -1,6 +1,6 @@..."
}
],
"changed_files": ["src/pages/Home.tsx"],
"logs": [...],
"trace_id": "codemod-1234567890"
}
3. Search Docs
POST /tool/searchDocs
{
"query": "Carbon Button aria roles",
"k": 5
}
Response:
{
"results": [
{
"title": "Button — Carbon React",
"path": "docs/components/button.md",
"snippet": "The Button component supports kinds: primary, secondary...",
"score": 0.98
}
],
"logs": [...],
"trace_id": "search-1234567890"
}
4. Token Converter
POST /tool/tokenConverter
{
"input_path": "tokens/tokens.json",
"outputs": ["css_vars", "scss_map", "js_tokens"],
"output_dir": "tokens",
"dry_run": true
}
5. Validate Component
POST /tool/validateComponent
{
"file_path": "src/components/MyButton/MyButton.tsx",
"rules": ["props", "accessibility", "tokens"]
}
Response:
{
"valid": false,
"errors": [],
"warnings": [
{
"type": "warning",
"rule": "accessibility",
"message": "Icon-only buttons should have aria-label"
}
],
"logs": [...],
"trace_id": "validate-1234567890"
}
6. Theme Preview
POST /tool/themePreview
{
"themes": ["white", "g10", "g90", "g100"],
"output_path": "theme-previews",
"dry_run": true
}
🔧 Development
Project Structure
carbon-mcp/
├── src/
│ ├── server/
│ │ ├── index.ts # Server bootstrap
│ │ ├── toolRegistry.ts # Tool registration
│ │ └── tools/ # Tool handlers
│ │ ├── generateComponent.ts
│ │ ├── codemodReplace.ts
│ │ ├── searchDocs.ts
│ │ ├── tokenConverter.ts
│ │ ├── validateComponent.ts
│ │ ├── themePreview.ts
│ │ └── figmaSync.ts
│ ├── lib/ # Utilities
│ │ ├── logger.ts
│ │ ├── fileUtils.ts
│ │ ├── templateUtils.ts
│ │ ├── codemodUtils.ts
│ │ ├── diffUtils.ts
│ │ └── tokenUtils.ts
│ ├── schemas/ # JSON schemas
│ └── templates/ # Component templates
├── package.json
├── tsconfig.json
└── README.md
Available Scripts
npm run dev # Start development server with hot reload
npm run build # Build TypeScript to dist/
npm start # Run production server
npm test # Run tests
npm run lint # Lint code
Adding a New Tool
- Create handler in
src/server/tools/myTool.ts - Create schema in
src/schemas/myTool.json - Register in
src/server/toolRegistry.ts - Update this README
🧪 Testing
npm test
Tests use Jest + ts-jest. Test files are located next to source files with .test.ts extension.
🔐 Security & Privacy
- No secrets in logs: The logger automatically redacts sensitive keys (tokens, passwords, API keys)
- Telemetry opt-in: Set
ANALYTICS_ENABLED=truein.envto enable (disabled by default) - File access: Tools only access files within the repo root
- Audit trails: All operations are logged with trace IDs for auditing
🌐 Environment Variables
| Variable | Required | Description |
|---|---|---|
PORT |
No | Server port (default: 4000) |
FIGMA_TOKEN |
No | Figma Personal Access Token for figmaSync |
GITHUB_TOKEN |
No | GitHub token for PR automation |
ANALYTICS_ENABLED |
No | Enable telemetry (default: false) |
CARBON_VERSION |
No | Carbon version to use (default: latest) |
📖 Common Codemods
btn-old-to-carbon
Replaces old <button className="btn-old"> with Carbon <Button kind="primary">
class-to-style
Refactors className styles that match Carbon tokens into token usage
replace-grid
Swaps custom grid with Carbon Grid
image-to-asset
Converts inline base64 images to static assets
🤝 Contributing
- Follow TypeScript best practices
- Add tests for new tools
- Update schemas and documentation
- Keep tools deterministic and idempotent
- Use dry-run by default for destructive operations
📝 License
MIT
🔗 Resources
Made with ❤️ for the Carbon Design System community
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.