Hyreflow

MCP Setup

Call Hyreflow tools and workflows from any MCP client — no local install.

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

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

Connector settings

FieldValue
Namehyreflow
Remote MCP server URLhttps://recruit.hyreflow.ai/api/v2/mcp
OAuth Client IDLeave empty
OAuth Client SecretLeave empty

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

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.

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 Desktop

Open Settings → Connectors

Click Add custom connector.

Paste in the name and URL

Values from the table above. Skip the advanced OAuth fields, then click Add.

Sign in to Hyreflow

A browser window opens.

Select a workspace

The one Claude may act on.

Approve

The connection is live.

ChatGPT Work

Open Settings

Then the connector settings.

Add a custom MCP connector

Paste in the name and URL from the table above, and nothing in either OAuth field.

Sign in to Hyreflow

A browser window opens.

Select a workspace

The one ChatGPT Work may act on.

Approve

The connection is live.

Before you approve

Two things on the approval screen are worth a glance.

The workspace. The connection is bound to it — its catalog, saved workflows, integrations, and credit balance. Nothing from your other workspaces is reachable through it. To switch, remove the connector and authorize again.

The callback address. A client running on your machine should show a loopback address like http://127.0.0.1:3118/callback, not somewhere on the internet.

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.

On this page