---
name: hyreflow-mcp-setup
description: Connect Hyreflow to an MCP client — Claude Code, Claude Desktop, or ChatGPT Work. Use when a user asks to add, install, connect or set up the Hyreflow MCP server or the Hyreflow connector, or sends this URL. Carry out the steps for the client you are running in instead of describing them. Skip when Hyreflow tools are already listed in this session.
---

# Connect Hyreflow over MCP

Hyreflow's tool catalog is served over the Model Context Protocol. Connecting gives you the
recruiting and enrichment tools, the saved workflows, and the skill documents of one Hyreflow
workspace.

**Work out which client you are running in, do that section, and stop.** The sections are
alternatives, not a sequence. If you cannot tell, ask the user.

If you are the Claude app on a phone — the likely case if the user reached you by scanning a code —
read **On a phone** below first.

## Connection details

| Field | Value |
| --- | --- |
| Name | `hyreflow` |
| Remote MCP server URL | `https://recruit.hyreflow.ai/api/v2/mcp` |
| OAuth Client ID | leave empty |
| OAuth Client Secret | leave empty |

Authorization is OAuth, and Hyreflow registers the client itself — leave both OAuth fields empty.
A Hyreflow API key is not a credential for this endpoint; do not send one and do not ask the user
for one.

## On a phone

A connector is added from Claude's settings on the web or in the desktop app, not from a phone
conversation, so do not send the user hunting for a menu that may not be there. Instead:

1. Tell them plainly that connecting takes a minute on a laptop, and that this chat can prepare it.
2. Ask what they are trying to do — sourcing candidates, finding work emails, qualifying a list.
3. Answer that question with what Hyreflow would do, so the trip to the laptop is worth making.
4. Give them the two things to bring: the connector URL from the table above, and this document's
   address, `https://www.hyreflow.ai/mcp.md`.

Do not try to run the Claude Code command below. There is no shell here.

## Claude Code

You can do this yourself. Run:

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

Then tell the user to run `/mcp` and choose **Authenticate**. They sign in, pick a workspace, and
approve. The handshake completes against a loopback listener on a port the client picks, and any
port is accepted, so there is nothing to register.

## Claude Desktop

Added through Settings, so this part is the user's to do. Give them these steps:

1. Open **Settings** → **Connectors** and click **Add custom connector**.
2. Enter the name and URL from the table above. Leave the advanced OAuth fields empty, then click
   **Add**.
3. Sign in to Hyreflow in the browser window that opens.
4. Select the workspace Claude may act on.
5. Approve.

## ChatGPT Work

1. Open **Settings**, then the connector settings.
2. Add a custom MCP connector with the name and URL from the table above, and nothing in either
   OAuth field.
3. Sign in to Hyreflow in the browser window that opens.
4. Select the workspace ChatGPT Work may act on.
5. Approve.

## What to tell the user before they approve

Two things on the approval screen are worth a glance, and it is the only place to refuse — there is
no read-only variant and no second prompt per tool.

- **The workspace.** The connection is bound to it: its catalog, saved workflows, integrations and
  credit balance. Nothing from their other workspaces is reachable through it. Switching means
  removing the connector and authorizing again.
- **The callback address.** A client running on their own machine shows a loopback address such as
  `http://127.0.0.1:3118/callback`, not an address on the internet.

Tool, enrichment and workflow runs spend that workspace's credits. Denying returns an error to the
client and mints nothing.

## Confirm it worked

List the tools available in this session. A live connection exposes the `hyreflow_*` tools —
searching and executing the catalog, bulk enrichment, workflows, and the credit balance.

Then check the balance and report it. A new account starts with 25 credits.

## Then

Read `hyreflow-recruit`'s SKILL.md before planning a pipeline, and a provider's playbook before
executing that provider's tool — the playbooks carry payload shapes and cost traps the tool schemas
do not. Both are served over the connection.

A good first request: source five software engineers at startups with verified personal emails and
LinkedIn URLs. Describe each tool's cost before running it.