
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
概覽
讓 AI 助理執行 HITL 工作流程,在手機上向真人請求決策並等待回覆。
- 可以做什麼
- 列出、檢視並建立工作流程,包含步驟、連線、輸入欄位與範例輸入內容
- 執行、重試、測試、啟用與暫停工作流程,並列出或等待執行結果
- 透過即時更新網址追蹤執行,並查看已發布版本
- 查看工作流程的審核者,並以電子郵件邀請審核者
- 建立、輪替、驗證工作流程加入碼並用它加入
- 檢查 API 金鑰並處理代理註冊狀態
- 適用情境
- 當代理在任務中途需要真人判斷(例如核准、選擇或確認某事),且應停住等待有人在 HITL 手機應用程式上作答時使用。適合已有 HITL 工作流程,或想由助理建立與管理工作流程的情境。
- 執行需求
- 遠端端點 mcp.hitl.sh;主要端點需要 OAuth 登入,簡化端點則以 HITL API 金鑰作為 Bearer 權杖。審核者需要 HITL 帳號與專用 HITL 手機應用程式才能接收並完成任務。另有本機 stdio 版本,透過 npx 執行並在環境變數中提供 HITL API 金鑰。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 HITL (Human in the Loop),將其新增到工作區。
- 連接 所需的 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
- 為需要使用其工具的對話啟用該服務。
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
- Add MCP Connector in ChatGPT with URL above
- Sign up through the OAuth flow
- (Optional) Add your personal HITL API key at:
https://mcp.hitl.sh/setup-api-key - Start using HITL tools!
For OpenAI Agent Builder / Zapier / Make.com (Direct API Key):
URL: https://mcp.hitl.sh/mcp-simple
- Add MCP Server with URL above
- Authentication: Bearer Token
- Token: Your HITL API key (e.g.,
hitl_live_abc123...) - 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.
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
- Node.js 18+ (download)
- HITL.sh API key (get one here)
- Auth0 account (sign up)
- Vercel account for deployment (sign up)
🔧 Environment Variables
Required for Production
Optional
🚀 Quick Start
1. Clone and Install
2. Set Up Auth0
Follow the setup guide in PER_USER_API_KEY_SETUP.md to:
- Create an Auth0 account and tenant
- Create an API with audience
https://mcp.hitl.sh - Create M2M applications for testing and management
- Configure Auth0 Action for per-user API keys
3. Configure Environment Variables
Create .env.local:
4. Run Locally
Server runs on http://localhost:3000
5. Test OAuth Flow
🌐 Deploy to Vercel
1. Push to GitHub
2. Deploy to Vercel
- Go to vercel.com/new
- Import your GitHub repository
- Add all environment variables from
.env.local - 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
- Auth0 Dashboard → Applications → Create Application
- Name:
ChatGPT MCP Connector - Type: Single Page Application
- Configure callback URLs (see above)
- Enable Connections → Username-Password-Authentication
2. Connect in ChatGPT
- ChatGPT → Settings → MCP Connectors
- Add connector with your Vercel URL:
(Note: Use base URL, not
/mcpendpoint) - Authentication: OAuth
- 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:
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
Test All Tools
📁 Project Structure
🔐 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
- CLAUDE.md - For future Claude Code sessions
- PER_USER_API_KEY_SETUP.md - Complete Auth0 setup guide
- CLAUDE_DESKTOP_SETUP.md - Local Claude Desktop integration
🐛 Troubleshooting
"Invalid token" errors
- Check that
AUTH0_ISSUER_URLmatches your Auth0 tenant - Verify token hasn't expired
- Ensure
AUTH0_AUDIENCEishttps://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_keyin user_metadata - User must log out/in to get new token with API key
🤝 Contributing
Contributions welcome! Please:
- Fork the repository
- Create a feature branch
- Make your changes
- Submit a pull request
📄 License
MIT License - see LICENSE file for details
🔗 Links
- HITL.sh - Human-in-the-Loop platform
- MCP Specification - Model Context Protocol
- Auth0 Documentation - OAuth provider
- Vercel Documentation - Deployment platform
✨ Credits
Built with:
來源:README.md,提交 348de77
工具
0版本歷史
1- v1.0.0最新Nov 19, 2026
評分
已滿足適用檢查項的 85%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通必需25 分
- 已宣告認證方式必需10 分
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分
其他 Human 整合

TAP
tech.human官方發布者
TAP 是託管式遠端 MCP 端點,透過佔位密鑰、政策檢查與可選的人工核准,為 AI 代理隔離憑證。
UGC, the Human Ad Network
africa.ugc官方發布者
UGC(「Human Ad Network」)的遠端 MCP 端點,讓助理在對話中處理廣告活動、剪輯與 Clip Studio。
Human Use
dev.humanuse
把真人變成 MCP 工具:代理呼叫 photo、errand 等工具後,卡片出現在對方手機上,回答以 JSON 回傳。
Coordination Game — Staked 1v1 Human or AI Turing Test MCP
由 GitHub 帳號 corsur 發布
遠端 MCP 伺服器,用於帶質押的 1v1 社交推理遊戲:助理會被匿名配對、與對手聊天,並猜測對方是人類還是 AI。

Human Creative AI Workflow & Eval Lab
由 GitHub 帳號 jdurey 發布
遠端 MCP 伺服器,提供多模型 AI 工作流程診斷、代理評測沙箱、護欄稽核、評審量表校準,以及 SOP 轉 SCORM/QTI 編譯。