Factory
Connect
Connect Factory from the terminal. Pass --help for the flags Factory accepts.
praxen integration connect --type factoryAPI key from your Factory account.
Connect Factory to delegate autofix implementation to Factory droids. Praxen Inc. investigates and proposes the fix; a droid implements it on a Factory managed computer and pushes the pull request. Bring your own Factory API access.
Setup
- In Factory, go to Settings → API keys and create an API key (it starts with
fk-). - Make sure the Factory organization's GitHub connection has access to your target repositories.
- Paste the key into Praxen Inc.
Connecting makes Factory the executor for every autofix the workspace creates. To route autofixes back through the Praxen Inc. executor, turn off Use Factory for all autofixes on the Factory integration page in Settings.
Your key is encrypted before it is stored, and the agent never sees it. Your Factory plan must include API and remote workspace access.
Give droids Praxen Inc.'s MCP tools
Droids can query Praxen Inc. directly (incidents, the infra graph, observability) over MCP while implementing a fix. Create an API key in Praxen Inc. under Settings → Coding agents (one click, every read scope the MCP tools check), then commit .factory/mcp.json to the repository:
{
"mcpServers": {
"praxen": {
"type": "http",
"url": "https://mcp.getpraxen.app/mcp",
"headers": { "Authorization": "Bearer YOUR_API_KEY" }
}
}
}
Disconnecting
Disconnect Factory in Praxen Inc., then revoke the API key in Factory.
Disconnect
Disconnecting stops every sync and check and deletes the credentials Praxen Inc. held. Everything Praxen Inc. set up in Factory is removed as well; nothing is left behind.
praxen integration disconnect <id>