How to use Ashby with Claude Code
You want Ashby inside Claude Code so it can prepare candidate debriefs, triage new applications, advance candidates through interviews, and record recruiting handoffs — without you copy-pasting between tabs. Here is the whole setup, once.
Create your Ashby gateway
The gateway is the thing Claude Code connects to, and it is where you decide which Ashby tools an agent may use. You create it once and every client reuses it.
-
Create an Arcade account
Sign up and open the dashboard. The free tier is enough to follow this through.
-
Create an MCP Gateway and select your Ashby tools
In the dashboard, create a gateway and pick the Ashby tools you want to expose. The gateway is what your client connects to, and it is where tool access is decided.
-
Copy your gateway URL
Every client below needs it.
https://api.arcade.dev/mcp/<YOUR-GATEWAY-SLUG>
Connect the gateway to Claude Code
-
Add the gateway as a remote HTTP MCP server
claude mcp add arcade --transport http "<YOUR_ARCADE_GATEWAY_URL>"
-
Verify it was added
claude mcp get arcade claude mcp list
-
Try it out
Open Claude Code in your project and ask it to use one of your Ashby tools.
Full Claude Code guide in the docs steps verified 2026-08-13
Try these Ashby prompts
Claude Code can now act on your Ashby account. Click a prompt to copy it.
Use tool permissions to keep an agent read-only until you are ready to allow notes, stage changes, or application archiving. Pair it with Contextual Access policies so a recruiting agent can review candidates without rejecting applications or changing their stage.