HITL (Human in the Loop)

io.github.hitl-shPublished by GitHub account hitl-shv1.0.0Updated Nov 19, 2026

Let AI agents ask a real person for a decision on their phone and wait for the answer.

The publisher's own server: TAP

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Lets an AI assistant run HITL workflows that ask a real person for a decision on their phone and wait for the answer.

What you can do
  • List, inspect and build workflows, including steps, connections, input fields and example input bodies
  • Run, retry, test, activate and pause workflows, and list or wait on their runs
  • Track runs with live-update URLs and published revisions
  • See who reviews a workflow and invite reviewers by email
  • Create, rotate, validate and join with workflow join codes
  • Check the API key and handle agent signup status
When to use it
Use it when an agent needs a human judgment call mid-task, such as approving, choosing or confirming something, and should block until a person answers on the HITL mobile app. It suits agents that already have HITL workflows or want to build and manage them from the assistant.
Requirements
Remote endpoint at mcp.hitl.sh; OAuth sign-in is required for the main endpoint, while the simpler endpoint takes a HITL API key as a bearer token. A HITL account and the dedicated HITL mobile app are needed for reviewers to receive and complete tasks. A local stdio variant runs via npx with a HITL API key in the environment.
Before you install
The service is built around a third-party mobile app and sends task content to HITL's servers and to invited human reviewers. Tools can create, update, delete, activate and pause workflows and invite people by email, so changes affect live automation. The API key is a credential; keep it out of shared configs. Some workflow routes are documented as only live on a development API host.

Installation

In SourceWeft

  1. Open HITL (Human in the Loop) in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.hitl-sh%2Fhitl/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "hitl-human-in-the-loop": {
      "type": "http",
      "url": "https://mcp.hitl.sh/mcp"
    }
  }
}

README

HITL.sh MCP Server

HITL.sh is a mobile-powered Human-in-the-Loop platform designed to give AI systems instant access to real human judgment. The entire system is built around our dedicated mobile app, which is required for the product to function and enables human reviewers to receive and complete tasks in real time.

🚀 Quick Start for Users

Choose the endpoint that matches your platform:

For ChatGPT Users (OAuth):

URL: https://mcp.hitl.sh/mcp

  1. Add MCP Connector in ChatGPT with URL above
  2. Sign up through the OAuth flow
  3. (Optional) Add your personal HITL API key at: https://mcp.hitl.sh/setup-api-key
  4. Start using HITL tools!

📚 Full ChatGPT Guide

For OpenAI Agent Builder / Zapier / Make.com (Direct API Key):

URL: https://mcp.hitl.sh/mcp-simple

  1. Add MCP Server with URL above
  2. Authentication: Bearer Token
  3. Token: Your HITL API key (e.g., hitl_live_abc123...)
  4. Start using HITL tools!

📚 Full OpenAI Agent Builder Guide


🛠️ For Developers

Features

  • OAuth 2.1 Authentication - Secure OAuth flow with Auth0 integration
  • Per-User API Keys - Users can configure their own HITL.sh API keys
  • Workflow tools - Find, run, build and manage HITL workflows, and choose who reviews them
  • ChatGPT Compatible - Works as a connector in ChatGPT
  • Claude Desktop Support - Standalone stdio server for local use
  • Production Ready - Deployed on Vercel with proper error handling

🛠️ Available Tools

HITL is workflows: an agent runs a workflow, the workflow asks your humans, and the run finishes with their answer.

ToolDescription
list_workflowsList your workflows, newest first
get_workflowGet a workflow: steps, connections, input fields
get_workflow_inputList the input fields a workflow reads, with an example body
run_workflowStart a run of an active workflow with its input
get_executionGet one run; with wait, answer as soon as it has finished
list_workflow_executionsList a workflow's runs
watch_executionGet a live-updates URL and token for a run
retry_executionRun a failed run again with the same input
create_workflow, update_workflow, delete_workflowBuild and change workflows
activate_workflow, pause_workflow, test_workflowMake a workflow runnable, stop it, or test-run it
list_workflow_revisions, publish_workflow_revisionPublished versions
list_workflow_humans, invite_to_workflowWho reviews a workflow; invite people by email
get_workflow_join_code, create_workflow_join_code, delete_workflow_join_code, rotate_workflow_join_codeA workflow's join code
validate_join_code, join_with_codeSee where a join code leads; join with it
check_api_key, signup_status, confirm_signup, resend_signup_emailThe key and agent signup

Loops, requests, images, sessions, people, organizations, teams, webhooks and uploads are no longer tools (the API still serves them). The workflow routes are live on dev.api.hitl.sh and answer 404 on api.hitl.sh until they ship there; set HITL_API_BASE=https://dev.api.hitl.sh/v1 to use them now.

Both endpoints (/mcp and /mcp-simple) register these tools from @hitl-sh/core, the same package behind the stdio server @hitl-sh/mcp, so the remote and local servers expose identical tools.

📋 Prerequisites

🔧 Environment Variables

Required for Production

bash
# HITL.sh ConfigurationHITL_API_KEY=hitl_live_your_default_api_key
# Auth0 OAuth ConfigurationAUTH0_ISSUER_URL=https://your-tenant.us.auth0.comAUTH0_AUDIENCE=https://mcp.hitl.sh
# Auth0 M2M Application (for testing OAuth)AUTH0_CLIENT_ID=your_client_idAUTH0_CLIENT_SECRET=your_client_secret
# Auth0 Management API (for per-user API keys)AUTH0_MANAGEMENT_CLIENT_ID=your_management_client_idAUTH0_MANAGEMENT_CLIENT_SECRET=your_management_client_secret

Optional

bash
# HITL API Base URL overrideHITL_API_BASE=https://api.hitl.sh/v1
# Extra hosts allowed to receive the API key (comma-separated). The client only sends# keys to hitl.sh and its subdomains, so set this to use a local API, e.g.# HITL_API_BASE=http://localhost:8080/v1 with HITL_ALLOW_HOSTS=localhostHITL_ALLOW_HOSTS=

🚀 Quick Start

1. Clone and Install

bash
git clone <your-repo-url>cd mcp.hitl.shnpm install

2. Set Up Auth0

Follow the setup guide in PER_USER_API_KEY_SETUP.md to:

  1. Create an Auth0 account and tenant
  2. Create an API with audience https://mcp.hitl.sh
  3. Create M2M applications for testing and management
  4. Configure Auth0 Action for per-user API keys

3. Configure Environment Variables

Create .env.local:

bash
cp .env.example .env.local# Edit .env.local with your credentials

4. Run Locally

bash
npm run dev

Server runs on http://localhost:3000

5. Test OAuth Flow

bash
node scripts/test-oauth.mjs http://localhost:3000/mcp

🌐 Deploy to Vercel

1. Push to GitHub

bash
git add .git commit -m "Initial commit"git push origin main

2. Deploy to Vercel

  1. Go to vercel.com/new
  2. Import your GitHub repository
  3. Add all environment variables from .env.local
  4. Click Deploy

3. Configure Auth0 with Vercel URL

Update your Auth0 applications with your Vercel URL:

For ChatGPT OAuth Client (SPA):

  • Allowed Callback URLs: https://chatgpt.com/connector_platform_oauth_redirect
  • Allowed Web Origins: https://chatgpt.com, https://chat.openai.com
  • Allowed Logout URLs: https://chatgpt.com, https://chat.openai.com

🤖 Using with ChatGPT

1. Create Auth0 SPA Client

  1. Auth0 Dashboard → Applications → Create Application
  2. Name: ChatGPT MCP Connector
  3. Type: Single Page Application
  4. Configure callback URLs (see above)
  5. Enable Connections → Username-Password-Authentication

2. Connect in ChatGPT

  1. ChatGPT → Settings → MCP Connectors
  2. Add connector with your Vercel URL:
    https://your-app.vercel.app
    (Note: Use base URL, not /mcp endpoint)
  3. Authentication: OAuth
  4. Complete login flow

3. Set Your HITL API Key

Visit https://your-app.vercel.app/setup-api-key to configure your personal HITL.sh API key.

💻 Using with Claude Desktop

For local Claude Desktop integration, use the published stdio server @hitl-sh/mcp:

1. Configure Claude Desktop

Add to ~/Library/Application Support/Claude/config.json:

json
{  "mcpServers": {    "hitl": {      "command": "npx",      "args": ["-y", "@hitl-sh/mcp"],      "env": {        "HITL_API_KEY": "your_hitl_api_key_here"      }    }  }}

From a clone of this repo, node scripts/claude-desktop-server.mjs runs the same server.

2. Restart Claude Desktop

The HITL tools will appear in Claude Desktop!

See CLAUDE_DESKTOP_SETUP.md for detailed instructions.

🧪 Testing

Test OAuth Flow

bash
node scripts/test-oauth.mjs http://localhost:3000/mcp

Test All Tools

bash
node scripts/test-all-tools.mjs http://localhost:3000/mcp your_api_key

📁 Project Structure

mcp.hitl.sh/├── app/│   ├── mcp/route.ts                    # Main MCP endpoint (OAuth)│   ├── mcp-simple/route.ts             # MCP endpoint with a raw API key│   ├── setup-api-key/page.tsx          # User API key setup page│   ├── api/update-hitl-key/route.ts    # API key update endpoint│   └── .well-known/│       ├── oauth-protected-resource/   # OAuth discovery│       └── oauth-authorization-server/ # Auth server metadata├── lib/│   └── auth0-verify.ts                 # Auth0 token verification├── scripts/│   ├── claude-desktop-server.mjs       # Stdio server (wraps @hitl-sh/core)│   ├── test-oauth.mjs                  # OAuth flow test│   └── test-all-tools.mjs              # All tools test└── docs/ (via .md files)

🔐 Security

  • OAuth 2.1 with PKCE for secure authentication
  • JWT verification using Auth0 JWKS
  • Per-user API keys stored securely in Auth0 user metadata
  • Environment variable fallback for shared API key
  • CORS properly configured for ChatGPT

📚 Documentation

🐛 Troubleshooting

"Invalid token" errors

  • Check that AUTH0_ISSUER_URL matches your Auth0 tenant
  • Verify token hasn't expired
  • Ensure AUTH0_AUDIENCE is https://mcp.hitl.sh

ChatGPT connection fails

  • Verify Auth0 SPA client has connections enabled
  • Check callback URLs are configured correctly
  • Ensure dynamic client registration is disabled

Per-user API keys not working

  • Verify Auth0 Action is deployed and in Login flow
  • Check user has hitl_api_key in user_metadata
  • User must log out/in to get new token with API key

🤝 Contributing

Contributions welcome! Please:

  1. Fork the repository
  2. Create a feature branch
  3. Make your changes
  4. Submit a pull request

📄 License

MIT License - see LICENSE file for details

🔗 Links

✨ Credits

Built with:

Source: README.md at commit 348de77

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 19, 2026

Score

85% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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
  • License10 pts

Other Human integrations