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

# Connect an agent

> Connect a coding agent to Chiplab over MCP. Setup steps for the clients people use most, and what to do when yours is not listed.

Chiplab exposes its simulation capabilities through the Model Context Protocol (MCP).
Once your agent is connected, it can call tools like `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 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

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](/agents/cursor)**
>
> Install with one click, or add the server to `mcp.json`.

> **[OpenCode](/agents/opencode)**
>
> Add Chiplab as a remote server in OpenCode's config.

> **[Claude Code](/agents/claude-code)**
>
> Add Chiplab with one `claude mcp add` command.

> **[Claude Desktop](/agents/claude-desktop)**
>
> Add Chiplab as a custom connector.

> **[VS Code](/agents/vs-code)**
>
> Install with one click, or add the server to `.vscode/mcp.json`.

> **[Codex](/agents/codex)**
>
> Add Chiplab with one `codex mcp add` command.

## Other clients

Any client with remote HTTP MCP and OAuth uses `https://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](https://discord.com/invite/F6GwZJ6ktP) or [open a request](https://github.com/veecle/chiplab/issues/new/choose).

## Managing connected sessions

After you complete the authentication flow, your agent session appears on the [API Keys](/platform/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.


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