HumanOps

io.github.thepianistdirectorPublished by GitHub account thepianistdirectorv0.2.1Updated Oct 24, 2026

MCP server for AI agents to dispatch real-world tasks to verified human operators

The publisher's own server: TAP

VerifiedSTDIODesktop onlyProductivity & Workflow

Overview

AI-generated overview

HumanOps is a local MCP server that lets an AI assistant dispatch real-world tasks to verified human operators through the HumanOps API.

What you can do
Dispatch real-world tasks to verified human operators through the HumanOps service, so an assistant can hand off work that needs a person rather than a tool call. Authentication and endpoint behavior are configured through the HumanOps API key and base URL. A sandbox mode is available for testing before sending real requests. No individual tools are listed in the supplied material, so the exact operations are not documented here.
When to use it
Use it when an assistant needs to delegate a task that requires a real person to carry it out, rather than something a software tool can do. The sandbox setting makes it reasonable to try the workflow before using it for live requests.
Requirements
Runs as a local process via npx from the npm package @humanops/mcp-server, so Node.js is needed. Requires a HumanOps API key supplied in the HUMANOPS_API_KEY environment variable. The API base URL can be set with HUMANOPS_API_URL, and HUMANOPS_SANDBOX set to 'true' enables sandbox mode. Network access to the HumanOps API is implied.
Before you install
The server requires a HumanOps API key, a secret that should be kept out of logs and shared configuration. Tasks are dispatched to third-party human operators, so anything sent may be seen by people outside your organization; avoid including sensitive data. Real dispatches may involve cost or contractual terms with the HumanOps service, so test in sandbox mode first.

Installation

In SourceWeft

  1. Open HumanOps in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Human integrations