Devin

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

Setup

1. In Devin, go to Devin API → Service users and provision a service user.
2. Copy its token (it starts with cog_).
3. Paste the token into Praxen Inc. The organization is detected automatically.

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

Your token is encrypted before it is stored, and the agent never sees it. Your Devin plan must include API access.

Give Devin Praxen Inc.'s MCP tools

Devin sessions can query Praxen Inc. directly (incidents, investigations, the infra graph, observability) over MCP while implementing a fix:

1. In Praxen Inc., open Settings → Coding agents and create an API key. One click creates it with every read scope the MCP tools check.
2. In Devin, go to Settings → Connections → MCP servers and click Add a custom MCP (requires the Manage MCP Servers permission).
3. Choose the Streamable HTTP transport and set the server URL to https://mcp.getpraxen.app/mcp.
4. Set the bearer token to the API key from step 1. Devin sends it as Authorization: Bearer <key>.

Disconnecting

Disconnect Devin in Praxen Inc., then revoke the service user token in Devin.