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 整合