ask and run directly inside a chat or terminal session, no manual API calls, no context switching, no physical board required.
How it works
Chiplab acts as an MCP server; your coding agent acts as the MCP client. When you send a message that involves firmware simulation, your agent automatically discovers the available tools and calls them on your behalf. Authentication happens once via a browser-based OAuth flow; you never need to copy tokens or manage credentials manually.MCP server URL
Chiplab’s MCP server is available athttps://chiplab.veecle.ai/mcp.
This URL is public and requires no special handling.
Authentication happens separately, through your browser session.
Choose your agent
These are the clients with setup steps. Open a card for that client’s clicks and config. Every client connects to the same server and signs in once through your browser.
Cursor
Install with one click, or add the server to
mcp.json.
OpenCode
Add Chiplab as a remote server in OpenCode’s config.
Claude Code
Add Chiplab with one
claude mcp add command.Claude Desktop
Add Chiplab as a custom connector.
VS Code
Install with one click, or add the server to
.vscode/mcp.json.
Codex
Add Chiplab with one
codex mcp add command.Other clients
Any client with remote HTTP MCP and OAuth useshttps://chiplab.veecle.ai/mcp.
A client that only speaks local stdio needs its remote-connector screen. Claude Desktop is that case: its JSON config does not accept this URL.
If your client cannot connect and you need it supported, tell us which one on Discord or open a request.
Managing connected sessions
After you complete the authentication flow, your agent session appears on the API Keys page of the Chiplab dashboard under Connected agents. From there you can:- See when the agent first connected and when it was last active.
- Revoke any session instantly; the agent loses access immediately and must re-authenticate to reconnect.