What this kind of tool is for
- Chain multi-step workflows across the other tools in this directory.
- Run a scheduled or triggered job instead of retyping the same request.
- Have your agent watch a feed, queue, or repo and act on new items.
How to compare servers like this
- Trigger model:
- Understand what starts the automation — a command, a schedule, or an event — before relying on it.
- Blast radius:
- Prefer tools that hand you a review point before an irreversible action runs.
- Chaining cost:
- Each chained step adds a failure point; keep critical paths on the fewest tools.
- Maintenance signal:
- Automations break quietly; a maintained tool is the difference between repair and rediscovery.
This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.
What is the HumanOps MCP server?
MCP server for AI agents to dispatch real-world tasks to verified human operators
How to install HumanOps
Copy-paste configuration for popular MCP clients.
HUMANOPS_API_KEYrequiredsecretYour HumanOps API key for authenticating agent requests
HUMANOPS_API_URLHumanOps API base URL
HUMANOPS_SANDBOXEnable sandbox mode for testing (set to 'true')
{
"mcpServers": {
"humanops": {
"command": "npx",
"args": [
"-y",
"@humanops/mcp-server"
],
"env": {
"HUMANOPS_API_KEY": "<YOUR_HUMANOPS_API_KEY>",
"HUMANOPS_API_URL": "<YOUR_HUMANOPS_API_URL>",
"HUMANOPS_SANDBOX": "<YOUR_HUMANOPS_SANDBOX>"
}
}
}
}Related MCP servers
Play chess, pool and poker for real money against AI agents and humans on Base. Pays via x402.
View repository →Scheduled HTTP requests and shell commands with retries, timeouts, and webhook alerts.
Turn any website into an RSS, Atom, or JSON feed using CSS selectors and scheduled polling.
PDF invoicing with auto-chase reminders, email delivery, and payment tracking.
Persistent agent memory with a decision layer: replay, restore, verify, or none — explainable.


