Documentation

Runner: the machine where the agent works

The runner is the program that runs on a company VM or computer and executes agents with the Claude installed on that machine. It only opens outbound connections to CaseFy.

1. 1In CaseFy, open Agents › Runtimes › Connect a runtime. A one-time code appears, valid for 15 minutes.
2. 2On the machine, run the command below with that code.
3. 3The machine shows as connected, with its concurrent-run limit and what is running. Then pick, on each agent, where it runs.

casefy-runner connect <code>

• Use a dedicated machine: the agent has full access to it. Each case gets a clean working folder.
• Production secrets (database password, cloud key) stay on the machine, read from the company vault, never in CaseFy.
• Revoking disconnects immediately; an interrupted run goes back to the queue by itself.

MCP server: CaseFy inside Claude

Connect Claude to CaseFy as a remote MCP connector. Login is OAuth and Claude works with the same permissions as your user.

1. 1Copy the connector address from Settings › MCP in CaseFy.
2. 2In Claude, add a custom connector with that address and log in.
3. 3Each process sets, under Process settings › MCP, which tools apply to its cases.

https://api.casefy.io/mcp

• Claude receives the company manual and the process manual before acting.
• Secrets such as the runner token and webhook keys never leave through MCP.

Webhooks and API

Other systems create cases in CaseFy and get notified of what happened.

1. 1Inbound webhook: under Process settings › Automation, create an automation with that trigger. It generates a URL with a secret key.
2. 2The other system calls the URL and CaseFy creates the case. A repeated call doesn't duplicate it.
3. 3Outbound webhooks notify other systems when something changes on the case.

• Schedule is the other trigger that always creates a case: daily, weekly, monthly or business day, with time and time zone.
• Every case also has its own email address.