Skip to main content
Cursor 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 .cursor/mcp.json in the project root and add the local server command:
Use Cursor’s user configuration when you want available across your projects. Add the selected human or Service Account identity through Cursor’s local secure configuration, following MCP setup. Do not mix the two identity modes.

​
Verify the connection

Open Cursor’s MCP server settings and confirm that is enabled. Then ask the agent:
Cursor 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

Use Cursor’s MCP settings to review the server status and logs. If the server does not 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 .cursor/mcp.json, or remove it in the MCP settings. See the Cursor MCP documentation for client-specific options.