Hire a real human for real-world verification, product testing, AI output review, and errands.
MCP server for Human For AI — a human endpoint for AI agents. Let your AI agent hire a real human operator for tasks that need physical presence, human perception, or human judgment:
get_human_services for the full catalogAll services are free during the proof-of-concept pilot. No API key, no payment. Every task is reviewed by the human operator before acceptance; illegal, harmful, deceptive, unsafe, or privacy-invasive tasks are rejected. First response within 12 hours, any day of the week — typically much faster: the operator is push-notified the moment a task arrives.
| Tool | Purpose |
|---|---|
get_human_services | Service catalog, accepted task types, limits |
submit_human_task | Submit a task; returns a task_id for status polling |
check_task_status | Poll a submitted task by task_id |
message_human_operator | Ask questions / scope work before submitting |
check_task_status shows progress in real time, not just the final result:
seen_by_operator_at — the moment a human actually saw the task (usually well before the first status change)eta — operator-set delivery estimate, added when the task is acceptedstatus_history — every transition (submitted → accepted → delivered, or rejected) with timestampsclaude mcp add human-for-ai -- npx -y humanforai
{
"mcpServers": {
"human-for-ai": {
"command": "npx",
"args": ["-y", "humanforai"]
}
}
}
You don't need this package — connect directly to the hosted endpoint (streamable HTTP, no auth):
https://humanforai.dev/mcp
E.g. Claude (Settings → Connectors → Add custom connector), or:
claude mcp add --transport http human-for-ai https://humanforai.dev/mcp
This package is a thin stdio proxy to the hosted Human For AI MCP endpoint. Tool definitions come from the live server, so they are always current — the package itself has no logic to go stale.
Previously published as human-api, which still works but is deprecated in favor of this package.
get_human_services — see what the operator can dosubmit_human_task — be specific and self-contained; include contact_email to receive the deliverablecheck_task_status — poll with the returned task_idMIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y humanforaiMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"dev-humanforai-humanforai": {
"command": "npx",
"args": [
"-y",
"humanforai"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencehumanforainpmHuman For AI works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.