Cursor integration: connect Cursor to Polylane
Connect Cursor Cloud Agents to Polylane with your Cursor API key. Delegate an investigated fix to an agent with production context and review its PR.
Get started for freeWhat Polylane does with Cursor.
Polylane investigates, Cursor implements
The investigation ends with a root cause and an evidence trail; Cursor's cloud agents take the handoff and open the pull request on your GitHub.
PRs that link back
Every pull request links back to the investigation that produced it, so the reviewer sees the evidence, not just the diff.
Your key, your account
Bring your own Cursor API key. Polylane routes the fix through the agent your team already trusts.
How to set up Cursor
- Create a key_ API key in Cursor Settings. Ensure your Cursor account has Cloud Agent access and your target repositories are connected.
- Paste the key into the Cursor integration in Polylane and connect.
- Review Use Cursor for all autofixes in the integration settings. Connecting selects Cursor as the workspace autofix executor; turn this setting off to return to Polylane’s executor.
Permissions and access
This is Cursor Cloud Agent API access, not a token for reading a local editor’s buffers. Your Cursor account and repository authorization determine where agents can implement changes. Polylane encrypts the API key and does not expose it to the investigation agent.
Discovery, refresh and the connected view
Polylane launches Cursor cloud agents for fix implementation and follows their work toward a GitHub pull request. Connecting also provisions a workspace Polylane API key and injects the Polylane MCP server into agents it launches, so they can read incident, infrastructure and observability context. Set mcpInjectionEnabled: false with the integrations PATCH API to disable that injection.
Example workflow
After an investigation identifies the failing code path in a connected GitHub repository, delegate its implementation to a Cursor cloud agent. The launched agent can query the infrastructure graph through the injected MCP connection while making the patch. Review the pull request in GitHub; this workflow does not depend on having a local Cursor session open.
Disconnect and revoke access
Disconnect Cursor in Polylane and revoke its key in Cursor. The Polylane API key provisioned for injected MCP access is revoked automatically. For cloud agents launched outside Polylane, configure MCP yourself in Cursor Integrations & MCP using Streamable HTTP and a bearer key from Polylane Settings → Coding agents.
Cursor setup and troubleshooting
Common questions.
Is this the same as using Polylane inside the Cursor editor?
No. This connection delegates implementation to Cursor Cloud Agents. The /for/cursor/ page covers using Polylane’s tools from Cursor as a coding-agent client.
Do launched Cursor agents need manual MCP configuration?
No. Polylane injects its MCP server into agents it launches by default. Agents you launch yourself need their own MCP configuration.