Provides 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."
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
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 |
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# 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.
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.
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.
# 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_patsrc/
├── 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# 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 startMCP HTTP gateway core
Project Benjamin connector
GitHub connector
Human approval gate
Built-in Control Plane (session state, ledger, checkpoints)
npm package @benni-os/operator-gateway
Docker image + one-click Railway / Render deploy
Web dashboard (runs · decisions · health)
Plugin SDK for custom connector development
OpenTelemetry tracing integration
Multi-tenant workspace isolation
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)
benni-operator-gateway is part of the Benni OS decentralized agentic architecture. The ecosystem is organized into modular Public Open-Source Infrastructure and Proprietary Core Autonomous Systems:
Layer / Domain | Repository | Maintainer | Description | Status |
Security & Defense |
| Tier-0 Zero-Trust runtime security shield, prompt injection firewall & secret redactor. | 🟢 Stable (Apache-2.0) | |
Execution & State |
| Resumable multi-step execution state machine, anti-loop circuit breaker & crash recovery. | 🟢 Stable (Apache-2.0) | |
Long-Term Memory |
| Sovereign bi-temporal knowledge graph & episodic memory with multi-tenant isolation. | 🟢 Stable (Apache-2.0) | |
Zero-Trust Verification |
| Cryptographic execution verification & signed SHA-256 evidence ledgers for side-effects. | 🟢 Stable (Apache-2.0) | |
Autonomous Web Perception |
| High-speed, zero-token-waste autonomous browser engine with semantic DOM-Delta compaction & native MCP. | 🟢 Stable (Apache-2.0) | |
MCP Tooling Matrix |
| Rapid developer toolchain for building, validating, and publishing Model Context Protocol servers. | 🟢 Public OSS | |
Local Hybrid Inference |
| GPU+CPU MoE expert offloading runtime with Skill 81 Ceiling Extraction on consumer hardware. | 🟢 Public OSS | |
Federated Execution |
| Unified policy-governed operator gateway for dispatching actions across local and cloud environments. | 🟢 Public OSS | |
Model Routing Hub |
| Intelligent LLM model router optimizing for latency, cost, and task-specific reasoning ceilings. | 🟢 Public OSS | |
Autonomous Community |
| Autonomous event-driven community management, issue triage, and repository telemetry. | 🟢 Public OSS |
The open-source stack serves as the decentralized foundation for the enterprise-grade Benni OS autonomous swarm kernel:
System | Role & Scope | Architecture Doctrine | Access |
Benni Master OS | Central operating system kernel v9.4 governing 43 canonical skills, runtime contracts, and swarm coordination. |
| 🔒 Private Core |
Project Benjamin | Sovereign autonomous execution orchestrator with typed handoff contracts and zero-human-in-the-loop loops. |
| 🔒 Private Core |
Project Adam | Agent synthesis, benchmark evaluation, and continuous recursive self-evolution engine. |
| 🔒 Private Core |
Benni Control Plane | Distributed state persistence, atomic snapshot restore protocols, and multi-tenant ledger governance. |
| 🔒 Enterprise |
Benni Social Hub | Multi-channel content authority distribution, attribution engine, and automated revenue funnels. |
| 🔒 Enterprise |
Benni Canvas | Autonomous UI engineering subsystem v14.0 delivering generative high-end motion and responsive dashboards. |
| 🔒 Enterprise |
Benni Nemesis | Federated integration gateway connecting cloud APIs, vector databases, and multi-cloud webhooks. |
| 🔒 Private Core |
Benni OS Genesis | Structured prompt engineering compilation and generative knowledge distillation engine. |
| 🔒 Private Core |
👉 Explore & Connect with the Benni OS Ecosystem:
Official Website: https://bennios.dev
Benni Operator Hub: https://hub.bennios.dev
GitHub Organization: https://github.com/benni-os
Maintainer Profile: https://github.com/BenniAlencar
Documentation & Blueprints: https://docs.bennios.dev
BENNI OPERATOR GATEWAY — Open-Source MCP Infrastructure by Benni OS
MIT_LICENSE • APPROVAL_GATE • HOT_RELOAD • DECISION_LEDGER • ZERO_VENDOR_LOCK
Engineered by Benni Alencar and the Benni OS Core Engineering Group
This server cannot be deployed
Zero-setup MCP gateway securely connecting AI to your tools with authentication and workflows
Zero-secret MCP gateway for AI agents: risk-scored, audited calls with human-in-the-loop approval.
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
Connect MCP clients to 2,000+ AI models without managing provider API keys.
