Cursor
Connect
Connect Cursor from the terminal. Pass --help for the flags Cursor accepts.
praxen integration connect --type cursorAPI key from your Cursor account.
Connect Cursor to delegate autofix implementation to Cursor cloud agents. Praxen Inc. investigates and proposes the fix; Cursor opens the pull request on your GitHub. Bring your own Cursor API access.
Setup
- In Cursor, go to Settings and create an API key (it starts with
key_). - Make sure your target repositories are connected to your Cursor account.
- Paste the key into Praxen Inc.
Connecting makes Cursor the executor for every autofix the workspace creates. To route autofixes back through the Praxen Inc. 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.
Praxen Inc.'s MCP tools
Nothing to set up: connecting Cursor provisions a Praxen Inc. API key for the workspace, and Praxen Inc. adds its MCP server to every Cursor cloud agent it launches. Agents can query Praxen Inc. (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.getpraxen.app/mcp, header Authorization: Bearer <key> with an API key from Settings → Coding agents in Praxen Inc.
Disconnecting
Disconnect Cursor in Praxen Inc., then revoke the API key in Cursor. The Praxen Inc. API key provisioned for MCP access is revoked automatically.
Disconnect
Disconnecting stops every sync and check and deletes the credentials Praxen Inc. held. Everything Praxen Inc. set up in Cursor is removed as well; nothing is left behind.
praxen integration disconnect <id>