MCP 服务器

benni-operator-gateway

An open-source MCP gateway for AI operators, connecting any LLM to a hot-reloadable connector registry with production-grade approval gates and a built-in control plane for session management.

README

Benni Operator Gateway

Open Source MCP Gateway for AI Operators — connect any LLM to your autonomous agent stack with production-grade approval gates, hot-reload connector registry, and a built-in Control Plane.

What is this?

Benni Operator Gateway is the open source core of the Benni OS autonomous AI operator stack. It implements the Model Context Protocol (MCP) as a production-grade HTTP gateway — letting any MCP-compatible AI client (Claude Desktop, Cursor, custom agents) connect to a unified, extensible set of tools and connectors.

Built for AI builders who want:

A self-hosted alternative to managed tool-calling APIs
Full control over what tools their agents can access
Human-in-the-loop approval gates before sensitive actions execute
A connector registry that hot-reloads without downtime

Architecture

graph TD
    A[AI Client\nClaude / Cursor / Agent] -->|MCP over HTTP| B[Benni Operator Gateway]
    B --> C[Connector Registry]
    C --> D[JARVAS-2 Connector]
    C --> E[GitHub Connector]
    C --> F[Custom Connectors]
    B --> G[Approval Gate Middleware]
    G -->|webhook| H[Human Operator]
    B --> I[Control Plane]
    I --> J[Session State]
    I --> K[Decision Ledger]
    I --> L[Atomic Checkpoints]

Quick Start

# 1. Clone
git clone https://github.com/benni-os/benni-operator-gateway
cd benni-operator-gateway

# 2. Install
npm install

# 3. Configure
cp .env.example .env
# Edit .env with your API keys

# 4. Run
npm run dev

Your MCP gateway is now live at http://localhost:3000.

Built-in Connectors

Connector	Status	Description
`jarvas2`	✅ Stable	JARVAS-2 autonomous agent — run tasks, queue jobs, set objectives
`github`	✅ Stable	Full GitHub API via MCP — issues, PRs, code, reviews
`control-plane`	🔧 Beta	Session state, atomic checkpoints, decision ledger

Project Structure

src/
├── app.ts               # Server bootstrap
├── index.ts             # Entrypoint
├── config/              # Environment & provider config
├── connectors/          # MCP connector modules
│   ├── jarvas2/         # JARVAS-2 connector
│   └── github/          # GitHub MCP connector
├── lib/                 # Core utilities
├── middleware/          # Auth, approval gate, rate limiting
├── registry/            # Hot-reload connector registry
├── routes/              # HTTP endpoints
├── services/            # LLM dispatch, session management
└── types/               # TypeScript contracts

Approval Gate

The gateway includes a built-in human approval middleware that intercepts sensitive tool calls before execution:

// Any tool marked requires_approval: true will pause and
// send a webhook to your configured APPROVAL_WEBHOOK_URL
// before proceeding. The agent waits for your response.

{
  "action": "delete_production_database",
  "reason": "Cleanup task requested by agent",
  "payload": { ... },
  "approve_url": "https://your-gateway/approve/req_abc123",
  "reject_url": "https://your-gateway/reject/req_abc123"
}