Connect Claude Code

Claude 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 project

Create .mcp.json in the project root and add the local server command:

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

On Windows, Claude Code requires cmd /c npx for an npx server. Set command to cmd and use ['/c', 'npx', '-y', '@airctrl/mcp'] as its arguments. Add the selected human or Service Account identity through your local secure configuration, following MCP setup. Do not mix the two identity modes.

Verify the connection

Run this command from the project after saving the configuration:

claude mcp get airctrl

Then ask Claude Code:

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

Claude Code should show the MCP server and 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

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

Use claude mcp list to confirm the configured name. If the server does not start, verify Node.js is available and review the local secure configuration. A 403 response means the selected identity lacks permission; changing an ID cannot grant it. Remove the server with claude mcp remove airctrl, or delete its airctrl entry from .mcp.json. See the Claude Code MCP documentation for client-specific options.

​Add to one project

​Verify the connection

​Use it safely

​Troubleshoot or remove it

Add to one project

Verify the connection

Use it safely

Troubleshoot or remove it