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

# Connect AI Coding Agents to Chiplab for Firmware Simulation

> Connect Cursor, OpenCode, or Claude Code to Chiplab's MCP server to access firmware simulation tools directly from your coding agent.

Chiplab exposes its simulation capabilities through the Model Context Protocol (MCP). Once your agent is connected, it can call tools like `ask`, `run`, and other tools 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 at `https://chiplab.veecle.ai/mcp`. This URL is public and requires no special handling. Authentication happens separately, through your browser session.

## Choose your agent

<CardGroup cols={3}>
  <Card title="Cursor" icon="arrow-pointer" href="/agents/cursor">
    Add Chiplab to Cursor's MCP settings and run firmware simulations from the editor's AI chat panel.
  </Card>

  <Card title="OpenCode" icon="terminal" href="/agents/opencode">
    Register Chiplab as a remote MCP server in OpenCode and authenticate from your terminal.
  </Card>

  <Card title="Claude Code" icon="code" href="/agents/claude-code">
    Register Chiplab as an HTTP MCP server in the Claude Code CLI and connect in a single command.
  </Card>
</CardGroup>

## 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.

Revoking is useful when you rotate machines, hand off a project, or suspect a session has been exposed.