MCP Reference

What a connected agent sees, once setup is done. The server speaks the 2024-11-05, 2025-03-26, 2025-06-18 and 2025-11-25 revisions of the protocol.

Tools

• hyreflow_tools_search — find tools by intent ("find software engineers", "verify emails"). The usual entry point. Names a matching recipe in its recipes field.

• hyreflow_tools_describe — input contract and exact credit cost before running. Argument-priced methods quote a worst case, not a base price. Also reports a side_effect flag per method, so an agent can tell a reversible lookup from a write to your ATS.

• hyreflow_tools_execute — run it. Waterfall sourcing like people search runs exactly as the CLI does it: house provider order, dedup, BYOK skips.

• hyreflow_workflows_list / hyreflow_workflow_run / hyreflow_workflow_runs — list this workspace's saved workflows, run one by the name or id that list returns, poll the run id it gives back. To drive it from a prompt:

  Run my "<workflow name>" workflow through Hyreflow and tell me when it finishes, with the total credits spent.

• hyreflow_enrich_run — row-by-row bulk enrichment.

• hyreflow_billing_balance — check spend.

• hyreflow_onet_lookup — job title → O*NET-SOC codes. Free, and needed before job-openings discovery, which takes codes rather than titles. "Head of Talent Acquisition" resolves by dropping the seniority prefix; each result carries the official title and description so a loose match can be checked.

• hyreflow_feedback — send feedback or a bug report, returns the filed issue's URL. Free. The session is attached so we can see the run that prompted it. Your client will ask before sending — it reaches real people.

Every result reports the credits it charged in _meta.

Tools that only read are marked read-only, so a client that groups tools by permission can auto-approve the safe set — catalog search, playbook reading, run status, balance. Anything that spends credits or writes to a connected system stays outside that group and keeps asking: hyreflow_tools_execute, hyreflow_enrich_run, and any workflow run.

The playbooks come with it

An MCP client installs nothing, so the agent skills are served over the connection instead — in full: the recruiting playbook, a playbook per provider covering access rules, payload shapes and cost traps, the pipeline recipes, and the sub-agent prompts.

Reading a provider's playbook before executing that provider's tool is the difference between a call that works and one that burns credits on a malformed payload. Three things point at the right one: hyreflow_tools_search names a recipe, hyreflow_tools_describe names a provider playbook, and every hyreflow_tools_execute result carries the same pointer in _meta.playbook.

Connecting also hands the agent the routing table — the index mapping a task ("a job description → a shortlist", "a company just raised") to the document that covers it, so it knows which playbook to open before reading anything.

They arrive two ways, and every client supports at least one:

• as MCP resources, addressed hyreflow://skills/<skill>/<path> — clients that show resources let you attach one to a conversation directly.
• as tools: hyreflow_skills_list (every skill and document), hyreflow_skill_read (one document in full — a skill name alone returns its SKILL.md, or add a path like provider-playbooks/apollo.md), hyreflow_skill_search (find a document by term; searching a provider name is the fastest route to its playbook).

Billing

Tool calls bill identically on every surface — MCP, CLI, or API. A connected client counts as one session, so per-session spend caps cover everything it does, and every charge lands on the approved workspace's balance. See pricing.

Run recording

A run trace records which tool ran, which provider served it, timing and outcome (personal data redacted), and which client made the call — grouped per connection, so a trace reads as one client's work. That's what lets us answer "why did this run do that?" when you report a problem. Recording never changes results or billing.

A client that lets you set request headers can opt out with X-Hyreflow-Telemetry: 0 — in Claude Code, add it when you connect:

claude mcp add --transport http hyreflow https://recruit.hyreflow.ai/api/v2/mcp \
  --header "X-Hyreflow-Telemetry: 0"

Clients that don't expose headers have no per-connection setting. For those, a workspace can have recording pinned on or off for the entire workspace — a support or debugging arrangement we set up with you. A pin takes precedence over anything a client sends. Ask us what your workspace is set to, or to clear it.