Cursor

Connect Cursor to delegate autofix implementation to Cursor cloud agents. Polylane investigates and proposes the fix; Cursor opens the pull request on your GitHub. Bring your own Cursor API access.

Setup

1. In Cursor, go to Settings and create an API key (it starts with key_).
2. Make sure your target repositories are connected to your Cursor account.
3. Paste the key into Polylane.

Connecting makes Cursor the executor for every autofix the workspace creates. To route autofixes back through the Polylane executor, turn off Use Cursor for all autofixes on the Cursor integration page in Settings.

Your key is encrypted before it is stored, and the agent never sees it. Your Cursor plan must include Cloud Agent access.

Polylane's MCP tools

Nothing to set up: connecting Cursor provisions a Polylane API key for the workspace, and Polylane adds its MCP server to every Cursor cloud agent it launches. Agents can query Polylane (incidents, the infra graph, observability) while implementing the fix. To turn this off, set mcpInjectionEnabled: false on the Cursor integration via the integrations PATCH API.

For cloud agents you launch yourself, add the server in the Cursor dashboard under Integrations & MCP: transport Streamable HTTP, URL https://mcp.polylane.com/mcp, header Authorization: Bearer <key> with an API key from Settings → Coding agents in Polylane.

Disconnecting

Disconnect Cursor in Polylane, then revoke the API key in Cursor. The Polylane API key provisioned for MCP access is revoked automatically.