Carbon MCP

There are two steps required to set up Carbon MCP in Bob. First, you need to install Carbon MCP from the Bob Marketplace. Then, you need to install the carbon-builder-skill.

Step 1: Installing Carbon MCP

In Bob, select the settings icon in the upper right.

Select the MCP tab, then search for “Carbon” in the text field. Click the Install button.

Enter your Carbon access token and session ID in the modal dialogue, then click Install.

You will see a confirmation of a successful installation.

Step 2: Installing the carbon-build skill

Now that you’ve installed Carbon MCP, you need to install the carbon-builder skill, which provides Carbon-specific guidance to help the model generate better output.

Follow the instructions in Step 4: Adding the carbon-builder skill to install the carbon-builder skill for Bob.

• Use the Claude Code CLI and replace the <TOKEN> and <SESSION> with your Carbon MCP auth credentials

• Verify that Claude Code recognizes Carbon MCP by running claude mcp list

Carbon MCP can be set up in Claude Desktop as an Extension or Custom Connector. This section describes how to make both connections.

Adding Carbon MCP as an Extension

• Open Settings > Extensions > Advanced Settings

• Click Install Extension

• Install the Carbon MCP Claude Desktop extension, which can be downloaded here.

• Enter your Carbon MCP auth token and session ID in the modal, click Save to confirm.

• Verify that the Carbon MCP extension is configured by ensuring the toggle is switched on and shows as Enabled.

Adding Carbon MCP as a Custom Connector

• Open Settings > Connectors
• Click on Add Custom Connector
• When prompted for a name, enter carbon-mcp
• Under the Remote MCP server URL input, use https://mcp.carbondesignsystem.com/mcp
• Click Add

Carbon MCP can be set up in Cursor in one of the following ways:

• Click here to automatically configure the MCP server.
• Alternatively, manually configure the MCP server by opening the Command Palette and following the steps below.

• Search for and select “View: Open MCP Settings.”

• In the MCP Settings view, click “Add Custom MCP”.

• It will open a file with your MCP servers where you can add the following configuration:

• Replace <TOKEN> and <SESSION> with your actual Carbon MCP auth credentials. Save and close the file, then restart Cursor to apply the changes.

• Verify that the Carbon MCP extension is configured by ensuring the toggle is switched on and shows as Enabled.

Carbon MCP can be set up in Codex by editing your ~/.codex/config.toml.

• Replace <TOKEN> and <SESSION> with your actual Carbon MCP auth credentials. Save and close the file, then restart Codex to apply the changes.
• Verify that the Carbon MCP extension is configured by ensuring the toggle is switched on and shows as Enabled.

For IBMers:

• Open Figma Make and navigate to click “Connectors”
• Select the IBM tab
• Click the Connect button next to Carbon MCP
• A browser window will open — sign in with your IBMid when prompted
• After signing in successfully, return to Figma Make. The Carbon MCP connector dialogue should still be open (if not, reopen Connectors and select the IBM tab)
• Toggle on the Enable write tools button
• For each of the following tools, open its dropdown and select Always run:
• doc_search
• code_search
• get_charts
• Click Back, then click X to close the Connectors menu

Starting your first Make with Carbon MCP:

• In Figma Make, create a new Make file
• Select a LLM model from the model selector. NOTE: Gemini was observed to consume fewer tokens, while Anthropic’s Claude Opus 4.6 model (or later) tended to produce more accurate and complete code output
• Click Add context in the chat box, then select Carbon MCP from your connectors to attach it to the session
• Paste or attach your input design (e.g. a Figma frame or image), then include the suggested user prompt in the same message and send it to begin generation
• Once generation begins, Figma Make will create an initial draft. Before accepting it, switch to the Code view (top of the Make canvas)
• Open the GUIDELINES.txt file, copy its full contents, and paste them into GUIDELINES.md in the code view
• Return to the chat and continue the conversation — the model will incorporate these guidelines going forward

For non-IBMers:

• Open Figma Make and navigate to click “Connectors”
• Select the Created by you tab
• Click the Create connector button
• In the Create connector dialogue, enter carbon-mcp as the name and click Next
• In the MCP server URL field, enter https://mcp.carbondesignsystem.com/mcp and click Create
• Click the Connect button next to Carbon MCP
• A browser window will open — sign in with your Figma account when prompted
• After signing in successfully, return to Figma Make. The Carbon MCP connector dialogue should still be open (if not, reopen Connectors and select the Created by you tab)
• Toggle on the Enable write tools button
• For each of the following tools, open its dropdown and select Always run:
• doc_search
• code_search
• get_charts
• Click Back, then click X to close the Connectors menu

Starting your first Make with Carbon MCP:

• In Figma Make, create a new Make file
• Select a LLM model from the model selector. NOTE: Gemini was observed to consume fewer tokens, while Anthropic’s Claude Opus 4.6 model (or later) tended to produce more accurate and complete code output
• Click Add context in the chat box, then select Carbon MCP from your connectors to attach it to the session
• Paste or attach your input design (e.g. a Figma frame or image), then include the suggested user prompt in the same message and send it to begin generation
• Once generation begins, Figma Make will create an initial draft. Before accepting it, switch to the Code view (top of the Make canvas)
• Open the GUIDELINES.txt file, copy its full contents, and paste them into GUIDELINES.md in the code view
• Return to the chat and continue the conversation — the model will incorporate these guidelines going forward

• Open your repository in GitHub and navigate to “Settings”.

• In the Settings sidebar, open Copilot and select “Coding agent”.

• Add the MCP configuration

• Replace <TOKEN> and <SESSION> with your actual Carbon MCP auth credentials, then click “Save MCP configuration”.

Carbon MCP can be set up in VS Code in one of the following ways:

• Click here to automatically configure the MCP server.
• Alternatively, manually use VS Code CLI and replace the <TOKEN> and <SESSION> with your Carbon MCP auth credentials

If the MCP client you are using is not listed, refer to their documentation for remote servers and use https://mcp.carbondesignsystem.com/mcp as the URL.

• Select the Bob Advanced mode, which is required to support skills.
• Download the carbon-builder skill and unzip it.
• Place the skill in .bob/skills/ at your project root (project-scoped) or in ~/.bob/skills/ (global).

Bob reads name and description from SKILL.md to determine when to activate the skill. The references/ files are automatically available to Bob once the skill is active. Verify the skill is visible by running /list-skills inside Bob.

Project-scoped (recommended for teams):

• Commit .bob/skills/carbon-builder/ to your repository so the skill is shared across the team without each developer needing to install it separately.

Global (available in all projects on this machine):

Claude Code discovers skills automatically from .claude/skills/ at your project root. No additional configuration is needed beyond having carbon-mcp configured as an MCP server.

• Download the carbon-builder skill and unzip it.

Project-scoped (recommended for teams):

• Commit .claude/skills/carbon-builder/ to your repository so the skill is version-tracked alongside the project and available to every developer on the team without a separate install.

Global (available in all projects on this machine):

Download the carbon-builder skill. No need to unzip; Claude Desktop accepts the ZIP file directly.

• Open Settings > Capabilities and ensure Cloud code execution and file creation is enabled
• Navigate to Customize > Skills
• Click the + to Upload a skill and select the downloaded carbon-builder.zip

Claude Desktop will activate the skill automatically based on its description. You can verify it appears in your Skills list and toggle it on or off from there.

Cursor uses MDC-format rule files in .cursor/rules/.

• Download the carbon-builder skill and unzip it.
• Create the rules directory:

• Create .cursor/rules/carbon-builder.mdc:

Ensure carbon-mcp is configured as an MCP server in Cursor’s settings.

GitHub Copilot coding agent supports Agent Skills from your repository in .github/skills/. Unlike local desktop clients, there is no global install location because the agent runs against the contents of the repository.

• Download the carbon-builder skill and unzip it.

Repository-scoped install:

Commit .github/skills/carbon-builder/ to your repository so the skill is available to GitHub Copilot coding agent when it works on issues, pull requests, or delegated coding tasks for that repo.

GitHub Copilot coding agent reads the name and description fields from SKILL.md and loads the skill automatically when the current task matches the skill’s purpose.

• VS Code supports Agent Skills as project skills in .github/skills/, .claude/skills/, or .agents/skills/, and as personal skills in ~/.copilot/skills/, ~/.claude/skills/, or ~/.agents/skills/.
• Use .github/skills/ in your repository if you want the skill to be shared with your team. Use ~/.copilot/skills/ if you want it available across all of your local projects in VS Code.
• Download the carbon-builder skill and unzip it.

Project-scoped (recommended for teams):

• Commit .github/skills/carbon-builder/ to your repository so the skill is version-tracked and available to other developers using VS Code on the same repo.

Global (available in all projects on this machine):

To verify the skill is available in VS Code:

• Open the Command Palette and run Chat: Open Chat Customizations
• Open the Skills tab and confirm carbon-builder appears in the list
• Or type /skills in chat to open the skills menu

VS Code reads the name and description from SKILL.md and loads the skill automatically when it is relevant to the current task.

If your MCP client is not listed above, refer to its documentation for installing skills.

Most agent tools that support custom instructions load context from a Markdown file or a dedicated directory at the project root. Common patterns include:

• A single instructions file such as AGENTS.md, AGENT.md, or .agent/instructions.md
• A rules or skills directory such as .agent/skills/, .rules/, or a client-specific equivalent
• Download the carbon-builder skill and unzip it.
• To install the carbon-builder skill in any of these clients, paste the body of SKILL.md (everything below the closing --- of the frontmatter) into the appropriate file. If the client supports a directory of files, copy the carbon-builder/ folder there. Refer to your client’s documentation for the exact path and format it expects.