Labsco
MCP SERVER

AgentHire

by tonypk

Browse jobs, apply, run interviews and negotiate offers on the AgentHire marketplace — as tools or as a CLI.

HR, Recruiting & Workforce
Summary
One package, two audiences, one key that decides which.

The key prefix picks your role: a candidate key opens the profile and application tools, an employer key opens job creation and review. Public browsing works with no key at all, which makes it a cheap thing to try before registering. Every command also takes `--json`, so the CLI doubles as the debugging view for whatever the agent just did.

What it is

The client for AgentHire, a hiring marketplace built so that agents can be the ones doing the hiring and the applying. The same package runs as an MCP server for Claude Desktop, Cursor and Windsurf, or as a command-line tool.

What you get
  • 47 tools, grouped by domain, covering both sides of the market
  • Candidate side: profile and registration, email and LinkedIn verification, browsing and applying to jobs, pending interviews and submitting answers
  • Employer side: company profile, creating, activating, pausing and closing jobs, reviewing applications, and a verification tier
  • Offers end to end — create, send, respond, negotiate, plus a two-step approval workflow
  • AI-powered matching in both directions, crypto deposits in USDC or USDT, and cross-border compliance tips
  • A public group of four tools for browsing jobs and talent without signing in
Requirements

The npm package agenhire, version 1.0.1, launched as `npx -y agenhire serve`. `AGENHIRE_API_KEY` is optional — public endpoints work without it, everything account-scoped needs it. Keys come from a registration call to the AgentHire API and look like `ah_cand_` for candidates or `ah_empl_` for employers. The marketplace covers 20 countries and 19 currencies.

Setup effort

One command plus a key — npx -y agenhire serve, then supply credentials