benni-operator-gateway
OfficialProvides tools for interacting with GitHub's API, enabling AI agents to manage issues, pull requests, code, and reviews.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
"You need a gate, not a rubber stamp."
⭐ What Is Benni Operator Gateway?
Benni Operator Gateway is the open-source MCP infrastructure layer of the Benni OS ecosystem — a production-grade HTTP gateway implementing the Model Context Protocol, purpose-built for autonomous AI operators.
It gives any MCP-compatible client (Claude Desktop, Cursor, custom agents, CI pipelines) a single, secure, extensible interface to interact with your tools, services, and data — without surrendering control to third-party managed APIs.
INTENTION → AI CLIENT → MCP OVER HTTP → OPERATOR GATEWAY → APPROVAL GATE → EXECUTION → AUDIT LOGRelated MCP server: mcpgate
⚡ Core Doctrine
These are not settings. These are architecture laws.
☔ Principle | 🔧 Implementation |
Gate, Not Rubber Stamp | Every sensitive action is intercepted — agent pauses, human approves, then execution resumes |
Hot-Reload Registry | Add or remove connectors live — zero downtime, zero redeploy |
Decision Ledger | Every tool dispatch logged with full context — tamper-evident, append-only |
Provider-Agnostic | Route any LLM behind one interface — no lock-in, no vendor dependency |
Session Continuity | Built-in Control Plane persists state and atomic checkpoints across agent runs |
Open Core | Gateway is, and will remain, fully MIT — build on it, fork it, contribute back |
🏗️ Architecture
graph TD
style GW fill:#0D0D0D,color:#fff,stroke:#7000FF,stroke-width:2px
style CR fill:#1a1a2e,color:#fff,stroke:#00B0FF,stroke-width:1px
style AG fill:#1a1a2e,color:#fff,stroke:#FF007A,stroke-width:1px
style CP fill:#1a1a2e,color:#fff,stroke:#FF6D00,stroke-width:1px
A["AI Client\nClaude · Cursor · Agent · Pipeline"] -->|MCP over HTTP| GW["⚡ Benni Operator Gateway"]
subgraph CR ["🔌 Connector Registry (hot-reload)"]
D["jarvas2 ✅ Stable"]
E["github ✅ Stable"]
F["custom connectors"]
end
subgraph AG ["🛡️ Approval Gate Middleware"]
G["Intercept → Webhook → Human"]
H["approve_url / reject_url"]
end
subgraph CP ["🧠 Control Plane (built-in)"]
J["Session State"]
K["Decision Ledger"]
L["Atomic Checkpoints"]
end
GW --> CR
GW --> AG
GW --> CP🚀 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 — set GATEWAY_API_KEY, APPROVAL_WEBHOOK_URL, GITHUB_TOKEN
# 4. Run (development)
npm run dev
# 4b. Run (production)
npm run build && npm startYour MCP gateway is live at http://localhost:3000.
Point any MCP-compatible client to http://localhost:3000/mcp.
🔌 Built-in Connectors
Connector | Status | Description |
| ✅ Stable | JARVAS-2 agent runtime — dispatch tasks, queue jobs, set objectives, read operational memory |
| ✅ Stable | Full GitHub API surface — issues, PRs, code search, reviews, branch management, secret scanning |
| 🔧 Beta | Gateway-native session state, atomic checkpoints, decision ledger — no external dependency |
The gateway is fully functional as a standalone MCP gateway. JARVAS-2 and Benni Control Plane are optional — connect any agent backend or build your own connector.
🛡️ Approval Gate
The built-in human-in-the-loop middleware intercepts any tool call marked requires_approval: true. The agent pauses, your webhook fires, nothing executes until you approve or reject.
// Payload sent to APPROVAL_WEBHOOK_URL
{
"action": "deploy_to_production",
"reason": "Agent requested deployment after build passed",
"payload": { ... },
"approve_url": "https://your-gateway/approve/req_abc123",
"reject_url": "https://your-gateway/reject/req_abc123"
}Pause → Notify → Resume. The core safety primitive for running agents against real infrastructure.
⚙️ Configuration
# Server
PORT=3000
NODE_ENV=production
# Auth
GATEWAY_API_KEY=your_secret_key
# Approval Gate
APPROVAL_WEBHOOK_URL=https://your-endpoint/approval
APPROVAL_TIMEOUT_MS=300000 # 5 minutes
# Project Benjamin Connector (optional)
BENJAMIN_API_URL=https://your-benjamin-instance
BENJAMIN_API_KEY=your_benjamin_key
# Legacy fallback:
JARVAS2_API_URL=https://your-benjamin-instance
JARVAS2_API_KEY=your_benjamin_key
# GitHub Connector
GITHUB_TOKEN=your_github_pat📁 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
├── middleware/ # Auth, approval gate, rate limiting
├── registry/ # Hot-reload connector registry
├── routes/ # HTTP endpoints
├── services/ # LLM dispatch, session management
└── types/ # TypeScript contracts🚢 Deployment
# Docker
docker build -t benni-operator-gateway .
docker run -p 3000:3000 --env-file .env benni-operator-gateway
# Fly.io (fly.toml included)
fly deploy
# Any VPS / cloud VM
npm run build && npm start🗺️ Roadmap
MCP HTTP gateway core
Project Benjamin connector
GitHub connector
Human approval gate
Built-in Control Plane (session state, ledger, checkpoints)
npm package
@benni-os/operator-gatewayDocker image + one-click Railway / Render deploy
Web dashboard (runs · decisions · health)
Plugin SDK for custom connector development
OpenTelemetry tracing integration
Multi-tenant workspace isolation
🤝 Contributing
Contributions welcome — especially new connectors. See CONTRIBUTING.md.
Highest-value contributions right now:
New MCP connectors (Notion, Linear, Slack, Supabase, etc.)
Improved approval gate delivery (email, Telegram, SMS)
Docker Compose + one-click deploy configurations
Observability integrations (OpenTelemetry, Grafana)
🌐 The Benni OS Open-Source Ecosystem
benni-operator-gateway is part of the coordinated Benni Master OS v9.4 open-source infrastructure suite:
Repository | Focus & Architecture | Stars |
Zero-Dependency Spec-Driven Development, Static AST Drift Detector & MCP Guardrail | ||
High-Throughput Sovereign Local Inference for 8GB–16GB Consumer GPUs | ||
Deterministic Zero-Cloud Agent Evaluation, Red-Teaming & Benchmark Harness | ||
Micro-Second Zero-Dependency Code Sandbox & Execution Shield for AI Agents | ||
Autonomous Multi-Source Deep Research & Evidence Synthesis Engine | ||
Token-Saving Resilient Headless Browser Automation & A11y DOM Compiler | ||
Deterministic Intent Compiler & Typed DAG Execution Planner for AI Agents | ||
Sub-Millisecond Context Compression & Semantic Deduplication Engine | ||
Real-Time Biometric Swarm Governance & 120 FPS Resonant Kinetic Interface | ||
Zero-Trust Runtime Security, Prompt Injection Firewall & Secrets Redaction | ||
Deterministic Multi-Step Task Execution Ledger & Anti-Looping Engine | ||
Cryptographic State Verification & Invariant Proof Engine for Agents | ||
Hybrid Vector + BM25 Hierarchical Session Memory & Continuity Engine | ||
Human-in-the-Loop Approval & Policy Enforcement Gateway | ||
Rapid Model Context Protocol (MCP) Server Scaffolding & Dynamic Tooling | ||
Autonomous Multi-Agent Intent Routing & Swarm Coordination Hub | ||
Autonomous GitHub Community Triaging & PR Feedback Agent |
🏛️ Commercial & Sovereign Architecture
Need autonomous multi-agent swarm orchestration, private datacenter infrastructure, or enterprise governance?
Official Website: https://benni-os.net
Operator Mode Playbook: https://benni-os.net/blog/academy.html
GitHub Organization: https://github.com/Benni-OS
Maintainer: Benni Alencar
📄 License & Provenance
License: MIT License
Author: Benni Alencar (
bennialencar@benni-os.net)Architecture: Benni Master OS v9.4 Tier-0 Governance Standard
BENNI OPERATOR GATEWAY — Open-Source MCP Infrastructure by Benni OS • benni-os.net • MIT License
MIT_LICENSE • APPROVAL_GATE • HOT_RELOAD • DECISION_LEDGER • ZERO_VENDOR_LOCK
Engineered by Benni Alencar and the Benni OS Core Engineering Group
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
An MCP gateway for teams deploying AI tools at scale to employee-facing and headless agents.
Zero-setup MCP gateway securely connecting AI to your tools with authentication and workflows
MCP gateway: one connection for your AI apps, with tool policies, PII redaction and audit logs.
Open-source MCP gateway with per-agent tool permissions, call approvals and tool-change review.
Related MCP Servers
- FlicenseCqualityDmaintenanceA powerful gateway for the Model Context Protocol (MCP) that unifies AI toolchains by federating multiple MCP servers, wrapping REST APIs as MCP tools, and supporting multiple transport methods with an admin dashboard.1-

mcpgateofficial
FlicenseNot gradedqualityBmaintenanceSelf-hosted MCP gateway that connects Claude, ChatGPT, and other AI agents to 20+ enterprise tools (GitLab, Jira, Notion, Google Workspace, Slack, Grafana, …) with OAuth, audit logs, and zero data leaving your infrastructure3-- FlicenseNot gradedqualityBmaintenanceA production-ready MCP gateway and control plane that provides credential vault, policy engine, audit logging, and managed runtime for routing tool calls between AI agents and downstream MCP servers.59-
- AlicenseNot gradedqualityCmaintenanceA local-first control plane for AI agent tools, providing policy enforcement, spend caps, rate limiting, and audit trails for MCP servers.35 PyPI1Apache 2.0