
AgentGate
io.github.agentkitai由 GitHub 账号 agentkitai 发布v0.0.3更新于 Oct 25, 2026
Human-in-the-loop approval gateway for AI agents over MCP: request, decide, approve.
概览
AgentGate 是一个人在环审批网关,让 AI 代理在执行操作前提交请求,经策略判定和人工审批后再执行。
- 可以做什么
- 提交、读取和列出审批请求,包括按 ID 查询状态以及按状态等条件筛选,并对待处理请求作出批准或拒绝并附上理由。创建、替换和删除审批策略,并按优先级列出策略。按条件分页读取审计日志,并列出审计记录中的不同操作者。请求可路由到仪表盘、Slack、Discord 或电子邮件,Webhook 会向外部系统通知请求事件。
- 适用场景
- 适用于代理可能执行发邮件、删文件或部署等有后果的操作时,希望由策略自动批准安全操作、自动拒绝危险操作,其余交由人工决定。也适合需要保留代理决策审计记录的团队。
- 运行要求
- 通过 npx 作为 MCP 服务器在本地运行,但需要一个可访问的 AgentGate 服务器(用 Docker 或从源码自托管,数据库为 SQLite 或 PostgreSQL)。MCP 客户端配置需提供 AGENTGATE_URL 和 AGENTGATE_API_KEY,API 密钥在初始化时生成且只显示一次。可选的 Slack、Discord 和 SMTP 凭据用于启用其他审批渠道。
安装
在 SourceWeft 中
- 打开 控制台中的 AgentGate,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
AgentGate
Human-in-the-loop approval system for AI agents.
Agents request. Policies decide. Humans approve.
Keep humans in control of what AI agents can do.
[npm version] [MIT License] [CI] [TypeScript]
Your AI agent wants to send an email, delete a file, or deploy to production. Should it? AgentGate lets you define policies that auto-approve safe actions, auto-deny dangerous ones, and route everything else to a human — via dashboard, Slack, Discord, or email.
✨ Highlights
- 🛡️ Policy engine — auto-approve, auto-deny, or route to humans based on rules
- 👥 Multi-channel approvals — Slack, Discord, email, or web dashboard
- 🔌 TypeScript SDK + MCP — works with any agent framework or Claude Desktop
- 🪝 Webhooks with retry — real-time notifications with exponential backoff
- 📝 Full audit trail — every request, decision, and action logged, each policy decision tagged with the OWASP LLM Top-10 risk it mitigates (compliance evidence)
- 🐳 Docker-ready — one
docker-compose upfor the full stack - 🔐 Production-hardened — SSRF protection, ReDoS defense, structured logging, graceful shutdown
- 🔗 One-click decision links — approve or deny directly from notification emails and webhooks
- ♿ Accessible UI — keyboard-navigable approval modals, focus trapping, ARIA labels
- 💀 Skeleton loading — smooth loading states across every dashboard page
- ⚡ Fast & lightweight — Hono server, SQLite or PostgreSQL
Quickstart
Drop AgentGate into an MCP client (Claude Desktop / Cursor / VS Code) — point it at the gateway:
Dashboard
See all pending requests at a glance, color-coded by urgency so you know what needs attention first.
Approval Requests
Review, approve, or deny requests — filter by status to focus on what matters.
Audit Log
Search through every decision with filters for event type, action, actor, and date range.
Request Detail
Drill into any request to see parameters, context, timeline, and audit trail — with one-click Approve/Deny buttons.
API Keys
Manage API keys with fine-grained scopes, rate limits, and usage tracking. Create, edit, or revoke keys from the dashboard.
Webhooks
Configure webhook endpoints for real-time notifications. Add URLs, pick events, and let AgentGate handle retries automatically.
Login
Sign in with your API key — create one via the CLI or ask your admin.
Table of Contents
- Quick Start
- Architecture
- Packages
- SDK Usage
- CLI
- MCP Integration
- Authentication
- API Endpoints
- Rate Limiting
- Webhooks
- Configuration
- Docker Deployment
- Development
- Troubleshooting
- Contributing
- License
Quick Start
1. Install dependencies
2. Run database migrations
3. Bootstrap (create admin API key)
Save the API key - it's shown once only! Set it in your environment:
4. Start the development environment
5. Run the demo
In a new terminal (with API key set):
6. Open the dashboard
Visit http://localhost:5173 to view and manage approval requests.
Architecture
Packages
SDK Usage
CLI
AgentGate includes a command-line interface for managing approval requests.
Installation
Configuration
Configure the CLI with your server URL and API key:
Configuration is stored in ~/.agentgate/config.json. You can also use environment variables:
Commands
Examples
MCP Integration
AgentGate includes a Model Context Protocol (MCP) server for integration with Claude Desktop and other MCP-compatible clients.
Claude Desktop Configuration
Add to your claude_desktop_config.json:
Available MCP Tools
Authentication
AgentGate uses API keys for authentication. All API requests (except /health) require a valid API key.
API Key Scopes
Using API Keys
HTTP Header:
SDK:
Creating Additional API Keys
API Endpoints
Rate Limiting
AgentGate supports per-API-key rate limiting to prevent abuse and ensure fair usage.
How It Works
- Rate limits use a sliding window algorithm (requests per minute)
- Limits are configured per API key
- When exceeded, requests return
429 Too Many Requests - Rate limit headers are included in all authenticated responses
Rate Limit Headers
Configuring Rate Limits
Set rate limits when creating or updating API keys:
Dashboard
Rate limits can also be managed from the web dashboard under Settings → API Keys.
Webhooks
AgentGate can notify external systems when request events occur.
Setting Up Webhooks
Webhook Events
Webhook Payload
Webhook Signatures
If you provide a secret, requests are signed with HMAC-SHA256:
Verify by computing HMAC-SHA256(secret, body) and comparing.
Webhook Retry
Failed webhook deliveries are retried automatically with exponential backoff. The server scans for pending deliveries and retries them with increasing delays (2^attempts * 1000ms) until successful or the maximum retry count is reached.
Configuration
Environment Variables
File-Based Secrets (_FILE suffix)
For Docker secrets or Kubernetes secret mounts, AgentGate supports a _FILE suffix convention. Instead of setting a secret directly in an environment variable, point to a file containing the value:
Behavior:
- File contents are trimmed of leading/trailing whitespace
- If both the env var and the
_FILEvariant are set, the explicit env var takes precedence - Missing or unreadable files produce a warning but do not crash the server
Example with Docker Compose:
Policy Configuration
Policies are stored in the database and can be managed via API:
Docker Deployment
AgentGate provides Docker images for easy self-hosted deployments.
Quick Start
- Copy the example environment file:
- Generate secure credentials:
- Start all services:
- Access the services:
- Dashboard: http://localhost:3003
- API Server: http://localhost:3002
- Health Check: http://localhost:3002/health
Host ports are configurable via
SERVER_PORT(default3002) andDASHBOARD_PORT(default3003); both map to the container's internal port 3000/80.
Services
* PostgreSQL and Redis are on an internal Docker network (
agentgate-internal) and are not exposed to the host by default. During development,docker-compose.override.ymlis auto-loaded and exposes them on ports 5432/6379. For production, rundocker-compose -f docker-compose.yml up -dto skip the override.
With Slack or Discord Bots
To include the bot services, use the bots profile:
Configuration
All configuration is done via environment variables. See .env.example for all options.
Required variables:
ADMIN_API_KEY— Admin API key (min 16 characters)
Recommended for production:
JWT_SECRET— JWT signing secret (min 32 characters)CORS_ALLOWED_ORIGINS— Restrict to your domain(s)POSTGRES_PASSWORD— Use a strong password
Building Images
Build all images locally:
Build a specific service:
Database Migrations
Migrations run automatically when the server starts. For manual control:
Viewing Logs
Stopping Services
Production Considerations
- Use a reverse proxy (nginx, Caddy, Traefik) for TLS termination
- Set strong passwords for PostgreSQL
- Restrict CORS origins to your domain
- Use Docker secrets for sensitive values in production
- Set up backups for PostgreSQL data volume
- Monitor health endpoints for uptime checks
Development
Testing
AgentGate uses Vitest for testing across all packages.
Coverage reports are generated per-package and include line, branch, and function coverage.
Code Quality
Project Structure
Contributing
Contributions are welcome! To get started:
- Fork the repository
- Clone and install dependencies (
pnpm install) - Follow the Development section above to set up your local environment
- Create a feature branch and make your changes
- Run
pnpm build && pnpm testto verify everything works - Open a pull request
Please make sure all tests pass and code is formatted (pnpm format:check && pnpm lint) before submitting.
🧰 AgentKit Ecosystem
License
MIT
来源:README.md,提交 abb46ee
工具
0版本历史
1- v0.0.3最新Sep 16, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分