HITL (Human In The Loop)

MCP办公协作

提供方 未标注

办公协作 HTTP · 远程 OAuth 授权 社区 / 第三方 Claude DesktopClaudeCursorVS Code
查看接入方式

Let AI agents ask a real person for a decision (approve/deny, choice, text, rating) on their phone, Slack or Telegram, and wait for the answer. 28 tools.

一句话选型结论

按资料字段整理

HITL (Human In The Loop) 属于办公协作类 MCP 服务器,HTTP · 远程,OAuth 授权,可直接接入 Claude Desktop、Claude、Cursor 等,有可直接复制的远程端点配置。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类办公协作 传输方式HTTP · 远程 鉴权OAuth 授权 部署方式支持远程部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

办公协作
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

Productivity

安装与配置

HTTP · 远程 OAuth 授权
连远程 HTTPS 端点,通常为 Streamable HTTP
npx add-mcp 'https://mcp.hitl.sh/mcp'

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
日程与消息

查日程、发消息、约会议。

表单与审批

填表单、走审批流。

团队协作

同步任务、汇总进展。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在办公协作场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
HITL (Human In The Loop)当前 未标注 HTTP · 远程 支持远程部署 有 2026-11-20
CowAgent 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Karakeep MCP 未标注 未标注 未标注 无 2026-05-17
agentscope 未标注 stdio · 本地进程 本地部署 有 2026-04-11
note-gen 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Everywhere 未标注 stdio · 本地进程 本地部署 有 2026-04-12

服务器档案

办公协作
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类办公协作本站按上游分类展示
连接方式HTTP · 远程连远程 HTTPS 端点,通常为 Streamable HTTP
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型支持远程部署上游给出的部署形态
最近核验2026-11-20上游最后核验时间

详细介绍

9.5 KB
来自项目仓库与上游目录的原文,未做删改

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.

Tool Description
list_workflows List your workflows, newest first
get_workflow Get a workflow: steps, connections, input fields
get_workflow_input List the input fields a workflow reads, with an example body
run_workflow Start a run of an active workflow with its input
get_execution Get one run; with wait, answer as soon as it has finished
list_workflow_executions List a workflow's runs
watch_execution Get a live-updates URL and token for a run
retry_execution Run a failed run again with the same input
create_workflow, update_workflow, delete_workflow Build and change workflows
activate_workflow, pause_workflow, test_workflow Make a workflow runnable, stop it, or test-run it
list_workflow_revisions, publish_workflow_revision Published versions
list_workflow_humans, invite_to_workflow Who reviews a workflow; invite people by email
get_workflow_join_code, create_workflow_join_code, delete_workflow_join_code, rotate_workflow_join_code A workflow's join code
validate_join_code, join_with_code See where a join code leads; join with it
check_api_key, signup_status, confirm_signup, resend_signup_email The 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

  • 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```bash

HITL.sh Configuration

HITL_API_KEY=hitl_live_your_default_api_key

Auth0 OAuth Configuration

AUTH0_ISSUER_URL=https://your-tenant.us.auth0.com
AUTH0_AUDIENCE=https://mcp.hitl.sh

Auth0 M2M Application (for testing OAuth)

AUTH0_CLIENT_ID=your_client_id
AUTH0_CLIENT_SECRET=your_client_secret

Auth0 Management API (for per-user API keys)

AUTH0_MANAGEMENT_CLIENT_ID=your_management_client_id
AUTH0_MANAGEMENT_CLIENT_SECRET=your_management_client_secret


### Optional```bash
# HITL API Base URL override
HITL_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=localhost
HITL_ALLOW_HOSTS=

🚀 Quick Start

1. Clone and Install```bash

git clone <your-repo-url>
cd mcp.hitl.sh
npm 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
{
  &quot;mcpServers&quot;: {
    &quot;hitl&quot;: {
      &quot;command&quot;: &quot;npx&quot;,
      &quot;args&quot;: [&quot;-y&quot;, &quot;@hitl-sh/mcp&quot;],
      &quot;env&quot;: {
        &quot;HITL_API_KEY&quot;: &quot;your_hitl_api_key_here&quot;
      }
    }
  }
}

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

  • 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_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

  • HITL.sh - Human-in-the-Loop platform
  • MCP Specification - Model Context Protocol
  • Auth0 Documentation - OAuth provider
  • Vercel Documentation - Deployment platform

✨ Credits

Built with:
- Next.js 15
- mcp-handler
- Auth0
- HITL.sh

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
HITL (Human In The Loop) 怎么安装?

在客户端按下面的安装命令接入:npx add-mcp 'https://mcp.hitl.sh/mcp'。装完在客户端配置里引用同一个包或端点。

HITL (Human In The Loop) 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式是HTTP · 远程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

HITL (Human In The Loop) 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

HITL (Human In The Loop) 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

HITL (Human In The Loop) 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

HITL (Human In The Loop) 能提供哪些能力?

资料显示能力标签包括 Productivity。具体工具清单以官方文档为准。

HITL (Human In The Loop) 需要什么运行环境?

属于远程端点,不需要在本地装运行时。

HITL (Human In The Loop) 是本地还是远程?

它是远程端点,连服务地址即可。传输方式为HTTP · 远程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-11-20。