MCP Setup

Your whole tool catalog is exposed over the Model Context Protocol, so a client that can't run shell commands — Claude Desktop, ChatGPT in the browser or its desktop app, and similar chat surfaces — connects instead of installing the CLI. Same engine, same tools, same costs, same credit balance.

Fastest route: open hyreflow.ai/mcp and click Open in Claude, or scan the code there with your phone. Claude opens with a setup prompt written, and works through the steps below with you. The rest of this page is the same thing by hand.

Got a terminal? The CLI is the better fit there: start with the Quickstart.

Connector settings

Leave any OAuth client-ID/secret fields empty: hyreflow registers the client itself and drives the whole handshake. Any MCP-capable client works; the eight below are the common ones.

Two clients are configured by file rather than by a settings screen: Antigravity and Hermes. Antigravity is the only one anywhere that takes a client ID, because it does not register itself; that ID is published below and is the same for everyone. Their two blocks are not interchangeable.

What gates a custom server is the client's own setting, not a plan tier: on the ChatGPT desktop app it is Developer mode, on the web it is the MCPs tab under Settings → Plugins.

Terminal clients complete the handshake against a listener on a loopback port they pick when the flow starts, and hyreflow accepts any port, so there is no redirect URL or port to register.

Claude Code

claude mcp add --transport http hyreflow https://recruit.hyreflow.ai/api/v2/mcp

Then run /mcp → Authenticate. Sign in, pick a workspace, approve.

Codex

codex mcp add hyreflow --url https://recruit.hyreflow.ai/api/v2/mcp

Then run codex mcp login hyreflow. Sign in, pick a workspace, approve.

Claude Desktop

ChatGPT (web)

ChatGPT desktop

The desktop app will not accept a custom server until Developer mode is on, which is the one step that differs from the web flow.

Google Antigravity

Antigravity is configured by file, and it will not register itself, so this is the one client that needs a client ID rather than an empty field. It is the same for everyone and carries no secret.

Paste this whole block into .gemini/config/mcp_config.json in your home directory:

{
  "mcpServers": {
    "hyreflow": {
      "serverUrl": "https://recruit.hyreflow.ai/api/v2/mcp",
      "oauth": { "clientId": "mcp_3c39d0bc0c1f435941f7962f" }
    }
  }
}

Hermes

Also configured by file, but Hermes registers itself, so its block carries no client ID — and its keys differ from Antigravity's. The two blocks are not interchangeable.

{
  "mcpServers": {
    "hyreflow": {
      "url": "https://recruit.hyreflow.ai/api/v2/mcp",
      "auth": "oauth"
    }
  }
}

Grokbot

No settings screen and no config file — Grokbot adds the connector itself when you ask it to.

Before you approve

The screen also lists what the connection can do: run any tool in that workspace's catalog, enrich in bulk, run its saved workflows, read run history and the credit balance. Tool, enrichment and workflow runs spend that workspace's credits. There is no read-only variant and no second prompt per tool, so that screen is where to refuse. Deny returns the client an error and mints nothing.

Prompts to start with

Use hyreflow to check my credit balance, then describe the cheapest way to find work emails for one person.

Use hyreflow to find VPs of Engineering at 50-person fintech startups in London. Describe each tool's cost first, then source 10 candidates with titles and LinkedIn URLs.

Next: what an agent can do over the connection, the tools, the playbooks served with them, billing, and turning off run recording.