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, pick the AI app you use, and copy the prompt into it, or scan the code there with your phone. Your assistant fetches the setup instructions and gives you the steps for your app. The rest of this page is the same steps.

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. Leave token and header fields empty too: a static Authorization header switches the browser sign-in off and the connection fails. Any MCP-capable client works; the ones below are the common ones, grouped by what they are.

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.

Chat apps

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.

Grok

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

Gemini

The Gemini web app's custom-MCP option is available only to personal accounts in the United States at the time of writing. If you see it, paste the name and URL from the table above; if not, use Antigravity, which is also where Google now directs individual Gemini CLI users.

Coding agents in the terminal

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.

OpenCode

Works in the desktop app and the CLI. Add to ~/.config/opencode/opencode.jsonc:

{
  "mcp": {
    "hyreflow": {
      "type": "remote",
      "url": "https://recruit.hyreflow.ai/api/v2/mcp",
      "enabled": true
    }
  }
}

OpenCode opens the sign-in on first use. The first connection can take up to a minute.

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"
    }
  }
}

The Hermes CLI takes the same keys under mcp_servers in ~/.hermes/config.yaml, followed by hermes mcp login hyreflow.

Goose

Run goose configure, choose Add Extension → Remote Extension (Streaming HTTP), name it hyreflow and paste the URL. Leave the headers step empty. In Goose Desktop the same fields are under Extensions → Add custom extension with type Streamable HTTP. Goose opens the sign-in when the extension first loads.

Editors and IDEs

Cursor

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json in the project — Cursor Settings → Tools & MCP → New MCP Server opens it for you:

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

Cursor lists the server under Tools & MCP; click Login on its row to sign in. Cursor can also install the hyreflow plugin, which bundles the skills; see the plugin repository.

VS Code and GitHub Copilot

Run MCP: Add Server from the command palette, pick HTTP, paste the URL and name it hyreflow, or add to .vscode/mcp.json in the workspace:

{
  "servers": {
    "hyreflow": {
      "type": "http",
      "url": "https://recruit.hyreflow.ai/api/v2/mcp"
    }
  }
}

Click Start above the server entry. VS Code asks to allow the sign-in, then opens the browser.

Cline

In Cline Desktop, open MCP Servers → Remote Servers, name hyreflow, paste the URL and click Add Server; a browser tab opens for the sign-in. The same entry by hand, in cline_mcp_settings.json:

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

Windsurf (Devin desktop)

Windsurf now ships as the Devin desktop app. Open the MCP servers panel from the chat and choose View raw config, which opens mcp_config.json (%APPDATA%\Devin\mcp_config.json on Windows, ~/.codeium/windsurf/mcp_config.json on macOS and Linux). Add:

{
  "mcpServers": {
    "hyreflow": {
      "serverUrl": "https://recruit.hyreflow.ai/api/v2/mcp"
    }
  }
}

Note the key is serverUrl, not url. Save and click Refresh in the MCP panel; a browser tab opens for the sign-in.

Zed

Agent panel → ⚙ → Settings → MCP Servers → Add Server: name hyreflow, paste the URL, leave headers and the OAuth client ID empty. Or add to settings.json:

{
  "context_servers": {
    "hyreflow": {
      "enabled": true,
      "url": "https://recruit.hyreflow.ai/api/v2/mcp"
    }
  }
}

Zed opens the sign-in when the server first connects.

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" }
    }
  }
}

Agent builders

Microsoft Copilot Studio

hyreflow is added to an agent as a tool. Before you start, check the Microsoft side is in place. A company already building agents in Copilot Studio usually has all of it; a new tenant needs an admin for the first two.

• An environment with Dataverse. Agents are stored in Dataverse. If Copilot Studio shows Dataverse isn't set up in this environment, a Power Platform admin creates one: Power Platform admin center → Manage → Environments → New, type Developer or Sandbox, with Add a Dataverse data store on. Then switch to it from the environment picker in Copilot Studio.

  

• Rights in that environment. You need the Environment Maker role. If the Solution list is empty when you create the agent, create one first in Power Apps → Solutions → New solution (that needs System Customizer).

• A Copilot Studio license. Adding tools needs one; the free trial works.

• Custom connectors allowed. Copilot Studio reaches MCP servers through Power Platform connectors, so a data policy that blocks custom connectors blocks hyreflow too.

With the tool on end-user credentials, each person who uses the agent is asked to sign in to hyreflow from a card in the chat, and their runs spend the credits of the workspace they approve. If the tool is set to use the maker's credentials instead, everyone acts as the maker and spends the maker's credits.

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.

Troubleshooting

Spend protection

The server checks spend itself, without relying on the agent to check first:

• Confirmation for expensive runs. A tool or enrichment call estimated above 50 credits, or above a quarter of your remaining balance, does not run on the first request. The server returns the estimate, your current balance and a confirmation token; the agent should show you the cost and, once you approve, repeat the same call with that token. Cheap calls run straight through. Details in the MCP reference.
• A per-session spend cap, if you want one. A connection works as one session until it sits unused for 24 hours, then its next call starts a new session with a fresh cap. So a per-session cap set on the billing page covers each stretch of work that connection does. Hyreflow does not impose a default: the cap is yours to choose, and raising one mid-session is not something the client can do for you.

Prompts to start with

Call the hyreflow_billing_balance tool 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.

Naming the tool matters on the first call: hyreflow_tools_search searches the catalog of provider adapters (Apollo, Prospeo, and so on), not the 22 top-level tools, so a model told only to "check the balance" can wander through provider account tools instead of calling hyreflow_billing_balance.

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