Connect AI
Save your assistant’s work, inspect the board, and continue in KiCad.
Example conversation · In-chat board views require enrollment and a supported client · Saving requires your explicit write consent · b-parasite by rbaron, CC BY-SA 4.0
Bring a BoardRepo link to the assistant you already use. It can follow connections, read component values, and inspect source files alongside you.
Search real open hardware by what you want to build.
“Find a Bluetooth soil moisture sensor that runs on a coin cell.”
Trace a signal through the schematic, with parts and nets to inspect.
“How does b-parasite measure soil moisture? Show me the signal path.”
Review the BOM and available check results before ordering parts or boards. Running new checks requires board ownership or check permission.
“Read the available check results and explain what I should review.”
Example questions to try after connecting. Start with b-parasite by rbaron.
Keep the source, inspect the changes, and continue in KiCad.
An assistant with file-upload support and your save permission can publish a personal project or a new version.
Open the saved version in your browser. Review the schematic, PCB and source, and compare revisions.
Download the source or pull the current version with BoardRepo for KiCad. Make your next changes in the editor.
Schematic
PCBYour assistant reads the designs themselves: schematics, nets, BOMs, and source files. Your consent determines access: public boards, plus your own boards including private ones if you approve that scope. Organization access needs separate consent and current board access.
Add the BoardRepo MCP server so you can search and read hardware boards for me. It is a remote HTTP MCP server at https://boardrepo.com/mcp. Search and read public KiCad and Altium boards, including available BOMs, schematics, and source files. In-chat schematic, PCB, 3D, and comparison views require an enrolled account and a supported client. Read access is the default. Saving boards, when available, requires my explicit write consent; set up read access for this request. Auth is OAuth via dynamic client registration, so there is no API key or secret to set. Run the right command for my MCP client, then start the OAuth sign-in and tell me once it is connected. For Claude Code that is: claude mcp add --scope user --transport http boardrepo https://boardrepo.com/mcp If that command is not recognized, use my client's own way of adding a remote or HTTP MCP server with that URL.
Paste it into Claude Code, Cursor, Codex, Gemini CLI, or another coding agent to add BoardRepo. Complete the browser sign-in and approve the access you want to grant.
https://boardrepo.com/mcpOpens BoardRepo in Claude's connector directory. Press Connect, approve BoardRepo access, then ask Claude to search BoardRepo or to read a board's schematic and BOM. A connector belongs to your account rather than to one app, so it works in Claude on the web, in the desktop app, and on mobile without setting it up again.
After connecting, open a conversation and enable BoardRepo under + → Connectors. Try: “Use BoardRepo to open rbaron/b-parasite. Explain its available schematic and BOM, cite the board, and say what you could not inspect.” Connecting alone does not start a task. If Claude cannot find the tools, check its Tool access setting; Auto and On demand load connectors according to the request.
https://boardrepo.com/mcp, and continue.On a Team or Enterprise workspace, a person with the required management role first adds BoardRepo; each member then connects their own account. Free plans allow one custom connector. Follow Claude's current setup guide if the menus differ.
https://boardrepo.com/mcp under Connection, and select OAuth.Legacy Apps interface: use Settings → Apps → Create(or Workspace settings → Apps → Create for admins). Enter the same URL, choose OAuth, complete sign-in and the tool scan, then create the app.
Custom MCP setup is currently on ChatGPT web. Plan and workspace policies determine the available actions: full modify/write support is available to Business, Enterprise and Edu, while Pro supports read/fetch connections. Check OpenAI's current requirements. Use BoardRepo in a regular chat; its tool set does not establish support for every research mode. Workspace admins must review and refresh app actions when new tools are added; changing the server alone does not update an approved app.
Run this once, then run /mcp and approve the browser sign-in:
claude mcp add --scope user --transport http boardrepo https://boardrepo.com/mcpDrop --scope user to add it to the current project only.
Add the server, then start the OAuth login:
codex mcp add boardrepo --url https://boardrepo.com/mcp
codex mcp login boardrepoRemote MCP over OAuth is recent in Codex. If codex mcp add or codex mcp login is not recognized, update Codex (check codex --version).
Cursor opens and asks you to sign in to BoardRepo. Approve it once and you are connected.
Add this to ~/.cursor/mcp.json, then click Login when Cursor shows "Needs login":
{
"mcpServers": {
"boardrepo": { "url": "https://boardrepo.com/mcp" }
}
}VS Code opens and asks you to Allow the sign-in. Then, in Chat, switch to Agent mode and turn on the BoardRepo tools.
https://boardrepo.com/mcp, name it, and choose Global or Workspace.{
"servers": {
"boardrepo": { "type": "http", "url": "https://boardrepo.com/mcp" }
}
}Needs GitHub Copilot. An organization policy can disable MCP.
Run this once, then approve the sign-in in your browser:
gemini mcp add --transport http boardrepo https://boardrepo.com/mcpAdd this to ~/.gemini/settings.json. Use httpUrl, not url, or streaming HTTP will not work:
{
"mcpServers": {
"boardrepo": {
"httpUrl": "https://boardrepo.com/mcp",
"authProviderType": "dynamic_discovery"
}
}
}https://boardrepo.com/mcp, continue, and approve the sign-in.Currently limited to personal Google accounts, ages 18+, in the US, with Activity on.
Add it to your OpenCode config: opencode.json in the project, or the global ~/.config/opencode/opencode.json. OpenCode runs the OAuth sign-in for a remote server itself, so there is no key to paste:
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"boardrepo": {
"type": "remote",
"url": "https://boardrepo.com/mcp",
"enabled": true
}
}
}Open Settings → Cascade → MCP Servers → Add custom server and paste https://boardrepo.com/mcp.
Edit ~/.codeium/windsurf/mcp_config.json. Windsurf calls the field serverUrl, not url:
{
"mcpServers": {
"boardrepo": { "serverUrl": "https://boardrepo.com/mcp" }
}
}Windsurf should open the BoardRepo sign-in in your browser. If it does not, update Windsurf. Never type your BoardRepo password into an assistant.
LM Studio opens and adds BoardRepo. The button needs 0.3.17 or newer; signing in from inside LM Studio needs 0.4.10 or newer.
Open the Program tab in the right sidebar, choose Install → Edit mcp.json, and add:
{
"mcpServers": {
"boardrepo": { "url": "https://boardrepo.com/mcp" }
}
}On an older build, or if LM Studio never asks you to sign in, use the fallback under "Any other MCP client" below, which runs the sign-in in your browser instead.
BoardRepo is a standard remote MCP server (Streamable HTTP) at https://boardrepo.com/mcp. Any MCP client that supports Streamable HTTP and OAuth dynamic client registration can connect with just this URL.
Older clients cannot call a remote server directly. Run BoardRepo through the mcp-remote bridge instead: it sits on your machine, talks to us over the network, and opens the BoardRepo sign-in in your browser the first time you use it.
{
"mcpServers": {
"boardrepo": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://boardrepo.com/mcp"]
}
}
}Needs Node.js installed. The bridge is a third-party package, not published by BoardRepo.
Prefer to browse first? Head to the board library.