trexi is headless by design — the product surface is the API and tooling, not a heavy UI. It exposes the ATS as Model Context Protocol tools, so Claude Code, Claude Desktop, or any MCP client can drive hiring in plain language.

​
Connect Claude Code (hosted)

The backend hosts an MCP server over Streamable HTTP — nothing to install.
  1. In the web app, open Settings → API keys and create a key. Copy it (trexi_sk_…) — it’s shown once.
  2. Add it to Claude Code:
The tools run as you, in the org the key belongs to — feedback and notes are attributed to you, and your role is enforced. Revoke a key anytime from the same Settings page. See Your team.

​
Local / offline (stdio)

For local development, run the backend in the open local mode (dev:local blanks the Clerk keys: no auth, a single active org):
Local mode has no auth and acts as an org owner — for local/agent use only. It activates only when the Clerk keys are unset, which the backend refuses in production.

​
Tools

​
What it looks like

Once registered, you describe the task and the agent calls the tools:
“Show me the pipeline for the Staff Engineer role, move Cara to the Interview stage, and leave a strong-yes note that her systems design was excellent.”
The agent calls list_jobs → list_candidates → move_candidate → add_feedback. Because the tools hit the same API as the dashboard, anything the UI can do is scriptable. See Jobs & your board and the candidate pipeline for the concepts behind these tools.