Human For AI
Hire a real human for real-world verification, product testing, AI output review, and errands.
Connect it
Settings → Connectors → Add custom connector
URL: https://humanforai.dev/mcpSettings → Apps & Connectors → Advanced → Developer mode
Create connector with URL: https://humanforai.dev/mcp{
"mcpServers": {
"humanforai": {
"url": "https://humanforai.dev/mcp"
}
}
}claude mcp add --transport http humanforai https://humanforai.dev/mcp{
"servers": {
"humanforai": {
"type": "http",
"url": "https://humanforai.dev/mcp"
}
}
}{
"mcpServers": {
"humanforai": {
"command": "npx",
"args": [
"-y",
"humanforai@0.1.4"
]
}
}
}claude mcp add humanforai -- npx -y humanforai@0.1.46 tools, verified live
get_human_servicesread-onlyFetch the Human For AI manifest: available services, operator profile (location, languages, working hours), response times, accepted and rejected task types, and trust & safety policy. Call this first to decide whether and how to hire the human. The catalog is examples, not limits — unlisted needs are welcome as custom_human_in_the_loop.
submit_human_taskSubmit a task for the human operator to perform in the real world. Returns a task_id immediately; the human reviews every task before accepting it (this is not instant execution). The operator is push-notified on submission; check_task_status shows seen_by_operator_at once a human has seen the task. Free during the pilot. contact_email must be a real mailbox (MX-checked) — it is how the deliverabl
check_task_statusread-onlyLook up a submitted task by its task_id. Returns current status (submitted → accepted → delivered, or rejected), status history with timestamps, seen_by_operator_at (the moment a human actually saw the task — usually well before the first status change), eta (operator-set delivery estimate, once accepted), and any operator notes. Once delivered, the response also carries receipt (a signed JWS bind
message_human_operatorSend a free-form message to the human operator — questions, scoping, custom or recurring projects, anything that is not yet a ready-made task. reply_to is REQUIRED: an email a human can read (MX-checked), or an https URL to receive the reply as a signed webhook push. The response also carries thread_url + access_token — every message is a pollable thread, so you can read the reply with check_messa
check_message_threadread-onlyRead the thread for a message you sent: the original text, every reply oldest-first, and whether the operator has answered. Needs the message_id and the access_token from the submission response. An empty replies list means no answer yet — the operator works at human speed, so poll occasionally rather than in a loop.
reply_in_message_threadAdd a follow-up to a thread you opened — answer a question the operator asked, add detail, correct yourself, or withdraw the request. Prefer this over sending a brand-new message about the same subject. Needs the message_id and access_token from the submission response.
Alternatives in Developer Tools
Compare →GIGitHubOfficialA
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
GIGitDiagramA
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
MDMCP Docs ServerOfficialA
AI access to Mapbox docs, API references, style specs, and guides. No token required.
MGMCP GrafanaOfficialA
An MCP server giving access to Grafana dashboards, data and more.
MDMCP Devkit ServerOfficialA
Provides AI assistants with direct access to Mapbox developer APIs and documentation.
Front-End ChecklistA
Review frontend code and live pages against 386 quality-gated web development rules.