The hiring tool your agents can call.
Aperturio is MCP-first by design. A /hire request is just an MCP call — so an agent can originate and manage a hire exactly like a person, while a human recruiter keeps the judgment on every candidate.
Hiring as a primitive, not a destination
Marketplaces and sourcing tools are places you log into. Aperturio is a capability your existing tools — and your agents — can call. The same /hire works in Claude Cowork, Cursor, Slack, and any MCP client. As MCP adoption compounds, Aperturio's surface area grows with it. (MCP hit 97M+ SDK downloads and 50+ enterprise partners in 2026.)
Agents start and run. Humans verify.
An agent calls /hire
Same request a founder would make, with role, salary, and context.
AI agents source
The market is scanned and matches surface.
A human recruiter reviews
Every candidate. This step never changes.
Results return via MCP
Shortlist, follow-ups, and scheduling, back into your workflow.
What you connect to
Aperturio exposes a /hire MCP tool plus tools for follow-ups, candidate Q&A, and scheduling. Point any MCP client or agent at it and you're live. Install + FAQ →
# The agent calls one MCP tool: request_talent
result = mcp.aperturio.request_talent(
role="Founding Account Executive",
role_category="revenue_growth",
stage="series_a",
engagement="full_time",
urgency="within_30_days",
latam_ok=False,
requester_email="founder@acme.com",
context="Series A revenue-ops SaaS. We've burned a quarter "
"on a generalist exec search. Looking for a founding "
"AE who has sold AI-native tools to RevOps buyers."
)
# → REQ-2026-0042. Aperturio replies by email within 1 business day.
# A human recruiter owns the placement. No candidate list returns here.One tool, one call. Server-side re-extraction keeps quality consistent across consuming models.