Human-as-a-Service for AI agents. Delegate tasks that need a real human, get results via API.
Human-as-a-Service for AI agents. Delegate tasks that need a real human, get results via API. The needhuman mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 3 defined tools rather than through you.
MCP server for NeedHuman — Human-as-a-Service API for AI agents.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Everything the assistant can do here goes through one of these:
need_human — Submit a task for a human to complete. Returns a task IDcheck_task_status — Poll a task by ID. Returns status, result, and prooflist_tasks — List all tasks for the current API keyYou will need 3 environment variables: NEEDHUMAN_API_KEY, YOUR_KEY, TASK_ID. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the planning and project tracking group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. NeedHuman's toolset — need_human, check_task_status, list_tasks — is a fair guide to whether it matches your workflow. It is maintained by MariusAure; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| need_human | Submit a task for a human to complete. Returns a task ID. |
| check_task_status | Poll a task by ID. Returns status, result, and proof. |
| list_tasks | List all tasks for the current API key. |
{
"mcpServers": {
"needhuman": {
"command": "npx",
"args": ["-y", "@needhuman/mcp-server"],
"env": {
"NEEDHUMAN_API_KEY": "YOUR_KEY"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| NEEDHUMAN_API_KEY | Credential the server authenticates with. | Yes |
| YOUR_KEY | Credential the server authenticates with. | Yes |
| TASK_ID | Configuration value read at startup. | Optional |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.