npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

mcp-human

v0.0.6

Published

MCP server for using Amazon Mechanical Turk as a human-in-the-loop service

Readme

A MCP Server for Humans

This MCP (Model Context Protocol) server allows AI assistants to delegate tasks to humans via Amazon Mechanical Turk. It provides a bridge between AI systems and human workers, enabling hybrid intelligence workflows.

Setup

Prerequisites

Configuring AWS credentials

# Configure AWS credentials for profile mcp-human
export AWS_ACCESS_KEY_ID="your_access_key"
export AWS_SECRET_ACCESS_KEY="your_secret_key"
aws configure set aws_access_key_id ${AWS_ACCESS_KEY_ID} --profile mcp-human
aws configure set aws_secret_access_key ${AWS_SECRETE_ACCESS_KEY} --profile mcp-human

Configuring MCP server with your MCP client

Claude code

Sandbox mode:

claude mcp add human -- npx -y mcp-human@latest 

The server defaults to sandbox mode (for testing). If you want to submit real requests, use MTURK_SANDBOX=false.

claude mcp add human -e MTURK_SANDBOX=false -- npx -y mcp-human@latest 

Generic

Update the configuration of your MCP client to the following:

{
  "mcpServers": {
    "human": {
      "command": "npx",
      "args": ["-y", "mcp-human@latest"]
    }
  }
}

e.g.: Claude Desktop (MacOS): ~/Library/Application\ Support/Claude/claude_desktop_config.json

TODO

Architecture

This system consists of two main components:

  1. MCP Server: A server implementing the Model Context Protocol that integrates with MTurk
  2. Form: A static HTML form.

The AI assistant connects to the MCP server, which creates tasks on MTurk. Human workers complete these tasks through a form, and their responses are made available to the AI assistant.

The Mechanical Turk form used is hosted on GitHub pages: https://syskall.com/mcp-human/. It gets populated with data through query parameters.

Configuration

The server can be configured with the following environment variables:

| Variable | Description | Default | |----------|-------------|---------| | MTURK_SANDBOX | Use MTurk sandbox (true) or production (false) | true | | AWS_REGION | AWS region for MTurk | us-east-1 | | AWS_PROFILE | AWS profile to use for credentials | mcp-human | | DEFAULT_REWARD | The reward amount in USD. | 0.05 | | FORM_URL | URL where the form is hosted. Needs to be https. | https://syskall.com/mcp-human/ |

Setting Up AWS User with Mechanical Turk Access

To create an AWS user with appropriate permissions for Mechanical Turk:

  1. Log in to the AWS Management Console:

    • Go to https://aws.amazon.com/console/
    • Sign in as a root user or an administrator
  2. Create a new IAM User:

    • Navigate to IAM (Identity and Access Management)
    • Click "Users" > "Create user"
    • Enter a username (e.g., mturk-api-user)
    • Click "Next" to proceed to permissions
  3. Set Permissions:

    • Choose "Attach existing policies directly"
    • Search for and select AmazonMechanicalTurkFullAccess
    • If you need more granular control, you can create a custom policy with specific MTurk permissions
    • Click "Next" and then "Create user"
  4. Create Access Keys:

    • After user creation, click on the username to go to their detail page
    • Go to the "Security credentials" tab
    • In the "Access keys" section, click "Create access key"
    • Choose "Application running outside AWS" or appropriate option
    • Click through the wizard and finally "Create access key"
  5. Save Credentials:

    • Download the CSV file or copy the Access key ID and Secret access key
    • These will be used as AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables
    • Important: This is the only time you'll see the secret access key, so save it securely
  6. Configure MTurk Requester Settings:

    • Visit the MTurk Requester website: https://requester.mturk.com/
    • Set up payment method and other account details
    • For testing, use the MTurk Sandbox: https://requestersandbox.mturk.com/

Note: Always start with the MTurk Sandbox (MTURK_SANDBOX=true) to test your integration without spending real money. Only switch to production when you're confident in your implementation.

MCP Tools

askHuman

Allows an AI to ask a question to a human worker on Mechanical Turk.

Parameters:

  • question: The question to ask a human worker
  • reward: The reward amount in USD (default: $0.05)
  • title: Title for the HIT (optional)
  • description: Description for the HIT (optional)
  • timeoutSeconds: Time until the HIT expires in seconds (default: 1 hour)
  • maxWaitSeconds: Maximum time to wait for a response in seconds (default: 5 minutes)

Example usage:

// From the AI assistant's perspective
const response = await call("askHuman", {
  question: "What's a creative name for a smart home device that adjusts lighting based on mood?",
  reward: "0.25",
  title: "Help with creative product naming",
  maxWaitSeconds: 600 // Wait up to 10 minutes
});

If a worker responds within the maxWaitSeconds window, the response will contain their answer. If not, it will return a HIT ID that can be checked later.

checkHITStatus

Check the status of a previously created HIT and retrieve any submitted assignments.

Parameters:

  • hitId: The HIT ID to check status for

Example usage:

// From the AI assistant's perspective
const status = await call("checkHITStatus", {
  hitId: "3XMVN1BINNIXMTM9TTDO1GKMW7SGGZ"
});

Resources

mturk-account

Provides access to MTurk account information.

URIs:

  • mturk-account://balance - Get account balance
  • mturk-account://hits - List HITs
  • mturk-account://config - Get configuration info

Limitations

  • Currently only supports simple text-based questions and answers
  • Limited to one assignment per HIT
  • No support for custom HTML/JS in the form
  • Simple polling for results rather than a webhook approach
  • Uses MTurk's ExternalQuestion format, which requires hosting a form

Future Enhancements

  • Support for qualification requirements
  • Support for multiple assignments per HIT
  • Ability to specify worker selection criteria
  • Custom form templates
  • WebSocket-based notifications for real-time responses
  • Integration with MTurk Review Policies