Skip to main content
Warp starts as a local MCP process. Read MCP setup first to choose the right identity and keep its sensitive configuration outside your project.

​
Add 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. 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 .

​
Verify the connection

Open the MCP server in Warp and confirm that it is enabled. Then ask the agent:
Warp 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

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 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 from the same settings page when you no longer need it. See the Warp MCP documentation for client-specific options.