> ## 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 Cursor to Chiplab

> Add Chiplab as an MCP server in Cursor and run embedded firmware simulations directly from your editor's AI chat panel without a physical board.

Cursor supports MCP servers natively. Once connected, Cursor's AI panel gains access to Chiplab's simulation tools and can call them automatically whenever your conversation involves firmware.

## Prerequisites

* Cursor installed and up to date.

## Connect Chiplab

<Steps>
  <Step title="Open MCP settings in Cursor">
    In Cursor, open **Settings** → **Tools & MCP** → **New MCP server**. This opens the MCP server configuration panel where you can register external servers.
  </Step>

  <Step title="Add the Chiplab config">
    Paste the following JSON into `~/.cursor/mcp.json`:

    ```json ~/.cursor/mcp.json theme={null}
    {
      "mcpServers": {
        "chiplab": {
          "url": "https://chiplab.veecle.ai/mcp"
        }
      }
    }
    ```

    If `mcp.json` already contains other servers, add the `"chiplab"` entry inside the existing `"mcpServers"` object rather than creating a new file.
  </Step>

  <Step title="Connect and authenticate">
    Back in **Settings** → **Tools & MCP**, find the **chiplab** entry and click **Connect**. Cursor opens a browser window where you complete the OAuth sign-in. Once you approve access, the browser redirects back and Cursor marks the server as connected.
  </Step>
</Steps>

<Note>
  Reload Cursor after saving `mcp.json` so the Chiplab tools show up in the AI chat panel. You can do this with **Developer: Reload Window** from the command palette.
</Note>

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

## Revoking access

To disconnect Cursor from Chiplab, open the **API Keys** page in the dashboard, find the session under **Connected agents**, and click **Revoke**. The session is invalidated immediately.