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

# Connect Warp

> Configure the local AIRCTRL MCP server in Warp.

export function AirctrlWordmark() {
  return <span className="airctrl-wordmark" aria-label="AIRCTRL">
      <span aria-hidden="true" className="airctrl-wordmark-air">AIR</span>
      <span aria-hidden="true" className="airctrl-wordmark-ctrl">CTRL</span>
    </span>;
}

Warp starts <AirctrlWordmark /> as a local MCP process. Read [MCP setup](/mcp/setup) first to choose the right identity and keep its sensitive configuration outside your project.

## Add <AirctrlWordmark /> in Warp

Open **Settings** > **Agents** > **MCP servers** in Warp, then add a local server. Set the command to `npx` and pass `-y @airctrl/mcp` as its arguments.

Add the selected human or Service Account identity through Warp's local secret configuration, following [MCP setup](/mcp/setup). Do not mix the two identity modes. Warp can sync a server configuration between your machines, but it does not sync its sensitive configuration. Configure that separately on every machine that runs <AirctrlWordmark />.

## Verify the connection

Open the <AirctrlWordmark /> MCP server in Warp and confirm that it is enabled. Then ask the agent:

```text theme={}
Check the AIRCTRL connection. Tell me which API URL and identity type are configured. Do not read or reveal any record values.
```

Warp should call the safe <AirctrlWordmark /> status tool. If you use a Service Account, ask it to list metadata from one assigned project instead of asking for accounts.

## Use it safely

State the account, project, and resource you intend to use. Ask for a read before any write. Review the proposed operation before approving it. Never include a token, passphrase, provider key, or decrypted value in chat.

## Troubleshoot or remove it

Open **Settings** > **Agents** > **MCP servers** and verify the <AirctrlWordmark /> command. If it cannot start, verify Node.js and the local secure configuration. A `403` response means the selected identity lacks permission; changing an ID cannot grant it.

Disable or remove <AirctrlWordmark /> from the same settings page when you no longer need it. See the [Warp MCP documentation](https://docs.warp.dev/reference/cli/mcp-servers) for client-specific options.