Connect VS Code

Visual Studio Code starts as a local MCP process. Read MCP setup first to choose the right identity and keep its sensitive configuration outside your project.

Add to one workspace

Create .vscode/mcp.json in the workspace and add the local server command:

{
  "servers": {
    "airctrl": {
      "command": "npx",
      "args": ["-y", "@airctrl/mcp"]
    }
  }
}

You can also use MCP: Add Server from the Command Palette and select the workspace or your user profile. Add the selected human or Service Account identity through VS Code’s local secure configuration, following MCP setup. Do not mix the two identity modes.

Verify the connection

Open MCP: List Servers from the Command Palette. Review the command, trust , and confirm that it starts. Then ask the agent:

Check the AIRCTRL connection. Tell me which API URL and identity type are configured. Do not read or reveal any record values.

VS Code should call the safe 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

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

Troubleshoot or remove it

Use MCP: List Servers to review ‘s status. 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. Remove the airctrl entry from .vscode/mcp.json, or remove it through the MCP commands. See the VS Code MCP documentation for client-specific options.

​Add to one workspace

​Verify the connection

​Use it safely

​Troubleshoot or remove it

Add to one workspace

Verify the connection

Use it safely

Troubleshoot or remove it