Use Case

Recruiting that runs as an operating system.

An AgentLed MCP workspace keeps role knowledge, sourcing criteria, candidate enrichment, approvals, outreach, scheduling, and ATS feedback in one loop - so each hiring run learns from the last.

01The Problem

Role knowledge is scattered

Hiring manager notes, must-have skills, compensation bands, interview feedback, and disqualifiers live across docs, Slack, ATS fields, and memory.

Shortlists lack evidence

Candidate lists often hide why someone matched, which trade-offs were accepted, and what still needs human review before outreach.

Recruiting loops do not learn

Replies, screen outcomes, interview notes, and offer decisions rarely flow back into sourcing criteria for the next run.

02How It Works
01

Load role and hiring context

AgentLed MCP turns job specs, manager notes, scorecards, past hires, compensation rules, and disqualifiers into reusable role knowledge.

02

Source against explicit criteria

Agents search LinkedIn, referrals, portfolios, and talent databases with hard filters, nice-to-haves, exclusion rules, and location or availability constraints.

03

Enrich candidate records

Profiles are enriched with work history, contact paths, public projects, company context, seniority signals, and evidence for each fit or risk call.

04

Review before outreach

OpenClaw and Codex prepare ranked shortlists, outreach angles, and confidence notes so recruiters can approve, edit, or reject candidates before messages send.

05

Run outreach and scheduling

Hermes sends approved outreach, routes replies, follows up with context, and books screens against recruiter and interview panel availability.

06

Update ATS and Knowledge Graph

Every reply, screen result, rejection reason, interview note, and hire outcome updates the ATS and Knowledge Graph so future searches get sharper.

03Connected Tools
AgentLed MCPCodexOpenClawHermesLinkedInHunter.ioATSGoogle CalendarSlackKnowledge Graph

Turn this operation into an agent-run workspace.