> ## 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 Claude Code to Chiplab

> Register Chiplab as an HTTP MCP server in Claude Code and authenticate once to call firmware simulation tools from any CLI coding session.

Claude Code manages MCP servers through its CLI, so you can register Chiplab with a single command and authenticate inside your first session. After setup, every Claude Code session has access to Chiplab's simulation tools without any additional configuration.

## Prerequisites

* Claude Code CLI installed and authenticated with Anthropic.

## Connect Chiplab

<Steps>
  <Step title="Register the MCP server">
    Run the following command in your terminal:

    ```bash theme={null}
    claude mcp add --transport http chiplab https://chiplab.veecle.ai/mcp
    ```

    Claude Code stores the server configuration globally, so it is available in every project without repeating this step.
  </Step>

  <Step title="Verify the registration">
    Confirm that Chiplab appears in Claude Code's server list:

    ```bash theme={null}
    claude mcp list
    ```

    You should see `chiplab` listed alongside any other registered MCP servers. If the entry is missing, re-run the `claude mcp add` command and check that the URL is correct.
  </Step>

  <Step title="Authenticate inside a session">
    Start a Claude Code session and run the `/mcp` command:

    ```text theme={null}
    /mcp
    ```

    Select **chiplab** from the list of registered servers. Claude Code opens a browser window for the OAuth flow, sign in with your Chiplab account and approve access. Once confirmed, the terminal session is authorized and ready.
  </Step>
</Steps>

<Note>
  After completing the OAuth flow, run `/mcp` again and Chiplab shows as **connected**. You only need to authenticate once per machine — subsequent sessions reuse the stored credentials.
</Note>

<Tip>
  Want Chiplab to run automatically after every change? Add a line to your project's `CLAUDE.md` file, such as: "After making firmware changes, test them on Chiplab before reporting back."
</Tip>

## Revoking access

To disconnect Claude Code from Chiplab, open the **API Keys** page in the dashboard, find the session under **Connected agents**, and click **Revoke**. The session is invalidated immediately and `/mcp` will show Chiplab as disconnected until you re-authenticate.