Breadboard connects to AI tools through the Model Context Protocol (MCP), an open standard that lets an AI tool use outside services. Your AI tool writes the project. Breadboard gives it the part reference, checks the project and runs the simulation on Breadboard's servers. You use your own AI tool and its subscription.
Before you connect
Sign in to Breadboard and open Account → Developer. The AI tools · MCP panel shows the setup for each tool below, ready to copy, and the server address: https://api.breadboard.build/mcp. Use the full address, including /mcp.
You do not install anything from Breadboard. Your AI tool connects to the address over the internet and asks you to sign in to Breadboard. You do not paste a password or a key into the tool.
Claude Code
Run this command in a terminal. The user scope makes Breadboard available in all of your own Claude Code sessions.
claude mcp add --transport http --scope user breadboard https://api.breadboard.build/mcp
Then type /mcp in Claude Code, choose breadboard and sign in when your browser opens. See Claude Code's MCP instructions.
Claude app
In Claude, open Customize → Connectors. Choose + Add, then Add custom connector. Enter Breadboard as the name, paste the server address and choose Continue. If Claude asks about the OAuth client, choose Register automatically. Then choose Add and sign in to Breadboard.
To use it in a conversation, choose + at the lower left of the chat, then Connectors, and turn Breadboard on. On a Team or Enterprise plan, an owner adds the connector for the organization first. See Claude's custom connector instructions.
Codex
Run both lines in a terminal. The second line opens Breadboard in your browser to sign in.
codex mcp add breadboard --url https://api.breadboard.build/mcp codex mcp login breadboard
The Codex command line tool, the Codex IDE extension and the ChatGPT desktop app share this setting. See Codex's MCP instructions.
Cursor
Add this entry to ~/.cursor/mcp.json, together with any servers you already have.
{
"mcpServers": {
"breadboard": {
"url": "https://api.breadboard.build/mcp"
}
}
}Cursor asks you to sign in to Breadboard the first time it connects. Turn the server on or off from Customize in Cursor's sidebar. See Cursor's MCP instructions.
VS Code
VS Code uses MCP servers through GitHub Copilot. Add this entry to ~/.copilot/mcp-config.json, or to .mcp.json at the root of a workspace, together with any servers you already have.
{
"mcpServers": {
"breadboard": {
"type": "http",
"url": "https://api.breadboard.build/mcp"
}
}
}When VS Code offers Authenticate for the server, choose it and sign in to Breadboard. See VS Code's MCP instructions.
Allow the connection
Breadboard opens a window that asks you to allow the tool. Allow it only if you started the connection in that tool just now. The tool supplies its own name, and Breadboard cannot confirm it. The window lists what the tool asks to do:
- Read the part and board reference, and check projects for errors.
- Run circuits in the simulator and compile firmware.
- Read your cloud projects.
- Save new projects and new versions of your projects.
The tool cannot delete projects or versions, publish to the gallery, create share links, or change your account or billing. It cannot read other people's private projects. Firmware in an agent run has no real internet access. A tool that reads a project receives its contents, so check that tool's data policy before you connect private work.
Try it
Ask: “Use Breadboard to look up the Arduino Nano and explain its LED pin.” Then ask the tool to check a small project before it runs it. For a run, ask for a short bench, a clear verdict and the display images.
Plans and limits
Every tool is available to signed-in accounts. A free account gets a trial of 5 simulation minutes each month, with a verified, permanent email address. Pro includes 150 simulation minutes each month for AI tools, with a daily allowance of 30. The CI plan includes 1,500 each month, with a daily allowance of 240. A new run starts only while you have time left, and the last run can go a little past the allowance. See Pricing.
A run is charged by the second for the time it takes on Breadboard's servers, at least 10 seconds a run. Compiling uses your build minutes, and saving uses your cloud project limits. AI tool calls never use your copilot questions. The AI tools · MCP panel shows what your plan includes.
Results, images and project links
A run result can include images of the circuit's displays. Each image has a link that opens in a browser signed in to your Breadboard account. Only your account can open it. Run results and their images are kept for 24 hours, and firmware that the tool compiled or uploaded is kept for 24 hours too.
To keep the work, ask the tool to save the project with its firmware. A saved project is an ordinary cloud project: it appears in your project list and keeps its version history. The tool gives you a link that opens the project in the workbench when you are signed in.
Disconnect or fix a connection
Open Account → Developer. Under Connected agents, choose Disconnect next to the tool. Its next call is refused. Disconnecting cannot recall data the tool already received, and it does not stop a run or a build that has already started.
If sign-in expires, connect again from your AI tool. If the service is busy, wait before you try again, and do not send the same bench again and again. If a permission or plan is missing, read the message, then connect again with the permission or check your plan. Browser extensions that call the server from another website are not supported.