> ## Documentation Index
> Fetch the complete documentation index at: https://docs.veecle.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> Chiplab is an MCP platform that gives AI coding agents direct access to chip-accurate firmware simulation, without any physical hardware. Built by Veecle.

Chiplab is built for AI-assisted embedded development.
Connect your coding agent once, and from then on you just describe what you want in plain language: "test this firmware on an STM32," "check if this build works on the nRF52840."
Your agent handles the rest: uploading your binary, running it on a chip-accurate virtual board, and reporting back the results.

## 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 what it can do right now for the current list of tools.
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.
* Projects: group uploads and runs under a server-minted `project_id`, so the work persists across sessions and is shared with everyone who has access.
* `run`: Upload a compiled ELF and execute it on a virtual chip. The run starts in the background; your agent waits for it, then downloads the captured UART output.

Today `run` covers single-chip execution and the UARTs you ask to capture, with more peripheral support and richer fault/panic traces on the way.

How a session moves through them is on [Core concepts](/concepts). The full pages are [ask](/tools/ask), [run](/tools/run), and [test](/tools/test). A pipeline runs that same loop. The setup is on [Test in CI](/use-cases/ci-on-every-pr).

## Knowledge corpus

Every simulation run deposits observed behavior into Chiplab's knowledge corpus, indexed by chip family, failure pattern, and board configuration.
Your firmware code and binaries are not part of the corpus, only the chip-level behavior observed during the run.
Your agent's answers draw on what Chiplab has learned about each chip, so every simulation gets more useful over time.

## Supported agents

Setup steps for Cursor, OpenCode, Claude Code, Claude Desktop, VS Code, and Codex are on [Connect an agent](/agents/overview).
A client that can add a remote HTTP MCP server and sign in through the browser uses the same URL.

All of them connect to Chiplab over HTTP using the MCP.
Authentication runs through a browser-based OAuth 2.0 flow, so there are no tokens to manage.

> **[Quickstart](/quickstart)**
>
> Run your first simulation in under five minutes.

> **[Connect an agent](/agents/overview)**
>
> Setup for Cursor, OpenCode, Claude Code, Claude Desktop, VS Code, and Codex.

## Use cases

> **[Test without hardware](/use-cases/test-without-hardware)**
>
> See what the firmware prints on a virtual board.

> **[Debug crashes](/use-cases/debug-a-crash)**
>
> Read the run status and UART, then ask about board gotchas.

> **[Test in CI](/use-cases/ci-on-every-pr)**
>
> Fail the pipeline when the expected UART output is missing.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.