What Chiplab does
Chiplab exposes its capabilities to your agent over MCP. You don’t call these directly; your agent discovers and uses them automatically based on what you ask it to do. Chiplab’s tool surface is always evolving. Ask Chiplab directly (call theask tool with no arguments) for the current, complete list of what’s available.
Treat the summary below as illustrative, not a frozen contract.
Available now
ask: Query Chiplab’s knowledge base with any natural-language question about the platform, its tools, or firmware development patterns.run: Execute firmware on a virtual chip and get back the run result, console output, and pass/fail status.
run covers single-chip execution and console output, with more peripheral support and richer fault/panic traces on the way.
See the full reference in Tools Overview.
Knowledge corpus
Every simulation run deposits observed behavior into Chiplab’s knowledge corpus, indexed by chip family, failure pattern, and board configuration. Chiplab never collects your firmware code or binaries as part of this, only the chip-level behavior observed during the run. The corpus is shared, so your agent’s answers can draw on patterns observed across the platform, making each simulation more useful over time.Supported agents
Chiplab works with any MCP-capable coding agent, with step-by-step setup guides for Cursor, OpenCode, Claude Code, Claude Desktop, VS Code, and Codex. Other MCP-capable clients, GitHub Copilot among them, connect the same way; see Connect an Agent for the full list. All of them connect to Chiplab over HTTP using the MCP protocol. Authentication is handled through a browser-based OAuth 2.0 flow, no manual token management required.Quickstart
Run your first simulation in under five minutes.
Connect an Agent
Agent-specific setup guides for Cursor, OpenCode, Claude Code, and more.
Tools Overview
What your agent can do with Chiplab, and how the tool surface evolves.