HITL (Human in the Loop)

io.github.hitl-sh由 GitHub 账号 hitl-sh 发布v1.0.0更新于 Nov 19, 2026

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

发布方自己的服务:TAP

已验证Streamable HTTP可网页运行效率与工作流沟通与协作

概览

AI 生成的概览

让 AI 助手运行 HITL 工作流,在手机上向真人请求决策并等待其答复。

可以做什么
  • 列出、查看并构建工作流,包括步骤、连接、输入字段和示例输入体
  • 运行、重试、测试、启用和暂停工作流,并列出或等待运行结果
  • 通过实时更新链接跟踪运行,并查看已发布版本
  • 查看工作流的审核人,并通过电子邮件邀请审核人
  • 创建、轮换、校验工作流加入码并用其加入
  • 检查 API 密钥并处理代理注册状态
适用场景
当智能体在任务中途需要真人判断(例如批准、选择或确认某事),并且应阻塞等待有人在 HITL 手机应用上作答时使用。适合已有 HITL 工作流、或希望由助手构建和管理这些工作流的场景。
运行要求
远程端点 mcp.hitl.sh;主端点要求 OAuth 登录,简化端点使用 HITL API 密钥作为 Bearer 令牌。审核人需要 HITL 账户和专用 HITL 手机应用才能接收并完成任务。另有本地 stdio 版本,通过 npx 运行并在环境变量中提供 HITL API 密钥。
安装前请注意
该服务依赖第三方手机应用,任务内容会发送到 HITL 服务器及受邀的真人审核者。工具可创建、更新、删除、启用和暂停工作流,并通过电子邮件邀请他人,因此会影响正在运行的自动化。API 密钥属于凭据,请勿放入共享配置。文档说明部分工作流路由目前仅在开发 API 主机上可用。

安装

在 SourceWeft 中

  1. 打开 控制台中的 HITL (Human in the Loop),将其添加到工作区。
  2. 连接 所需的 凭据。它们会被私密存储,绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.hitl-sh%2Fhitl/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。

{
  "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:

来源:README.md,提交 348de77

工具

0
该服务器需要登录,因此 SourceWeft 无法在没有账号的情况下读取其工具,也未收录。已连接账号所能看到的内容可能因账号及其权限而异。

版本历史

1
  1. v1.0.0最新Nov 19, 2026

评分

已满足适用检查项的 85%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

其他 Human 集成