Secure MCP Gateway (secure-mcp-gateway-bba04718)

MCPAI代理

提供方 nik-kale

AI代理 未标注 Token 社区 / 第三方 Claude DesktopClaude

一个安全优先的模型上下文协议(MCP)网关,用于AI驱动的自主操作、SRE和支持代理,提供策略访问控制、人工审批和全面审计日志。

一句话选型结论

按资料字段整理

Secure MCP Gateway (secure-mcp-gateway-bba04718) 属于AI代理类 MCP 服务器,传输方式未标注,Token,可直接接入 Claude Desktop、Claude,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类AI代理 传输方式未标注 鉴权Token 部署方式未标注
GitHub 星标 0 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

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

能力标签

支持客户端

适用场景

AI安全TypeScript本地部署自主操作策略控制审计日志MCP协议

安装与配置

未标注 Token
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

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

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

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

值得选的地方

  • 已适配 Claude Desktop、Claude,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好Token对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

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

不太适合

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

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Secure MCP Gateway (secure-mcp-gateway-bba04718)当前 未标注 未标注 未标注 无 2026-05-17
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

AI代理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方nik-kale上游标注的维护方 nik-kale
分类AI代理本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式Token远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

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

Secure-MCP-Gateway

> A security-first Model Context Protocol (MCP) gateway for AI-powered autonomous operations, SRE, and support agents.

What is MCP?

The Model Context Protocol (MCP) is an open standard that enables AI applications to securely connect with external data sources and tools. It provides a uniform way for AI agents to interact with services like databases, APIs, and development tools.

Why a Secure Gateway?

While MCP enables powerful integrations, letting AI agents directly access production infrastructure introduces significant risks:

  • Uncontrolled writes: Agents could accidentally delete resources, close critical incidents, or corrupt data
  • Privilege escalation: Without proper controls, agents might perform actions beyond their intended scope
  • Audit gaps: Direct access makes it hard to track what agents did and why
  • Compliance risks: Regulatory requirements often mandate human oversight for certain operations

Secure-MCP-Gateway solves these problems by providing:

  • Policy-based access control: Define rules for what actions are allowed, denied, or require approval
  • Human-in-the-loop approvals: High-risk operations pause for human review before execution
  • Comprehensive audit logging: Every tool call and policy decision is logged for compliance and debugging
  • Safe integration with existing MCP ecosystems: Works with directories like PulseMCP and awesome-mcp-servers, adding security without replacing them

This is a reference architecture for enterprises deploying autonomous operations agents in production environments.

Architecture Overview```

┌─────────────────────────────────────────────────────────────────┐
│ AI Agents / Claude Desktop / Custom Clients │
└────────────────────────┬────────────────────────────────────────┘
│
▼
┌───────────────────────────────┐
│ Secure-MCP-Gateway │
│ ┌─────────────────────────┐ │
│ │ Policy Engine │ │ ← Evaluate: allow/deny/review
│ │ - Config-driven rules │ │
│ │ - Severity matching │ │
│ └─────────────────────────┘ │
│ │
│ ┌─────────────────────────┐ │
│ │ Approval Manager │ │ ← Human-in-the-loop
│ │ - Pending approvals │ │
│ │ - Token management │ │
│ └─────────────────────────┘ │
│ │
│ ┌─────────────────────────┐ │
│ │ Audit Logger │ │ ← Log everything
│ │ - JSON structured logs │ │
│ │ - File + console │ │
│ └─────────────────────────┘ │
└────────────┬──────────────────┘
│
┌────────────┼────────────┐
▼ ▼ ▼
┌────────┐ ┌─────────┐ ┌──────────┐
│ Jira │ │ K8s │ │ Splunk │ ... (MCP Servers)
│ MCP │ │ MCP │ │ MCP │
└────────┘ └─────────┘ └──────────┘
│ │ │
▼ ▼ ▼
┌────────────────────────────────────┐
│ Production Infrastructure │
│ - Jira / PagerDuty │
│ - Kubernetes / Cloud APIs │
│ - Observability (Splunk, Datadog) │
└────────────────────────────────────┘


**Data Flow:**

1. **Agent calls tool** → Gateway receives the request
2. **Policy evaluation** → Match against configured rules (allow/deny/review)
3. **Audit log** → Record the decision
4. **If ALLOW** → Execute immediately and log result
5. **If DENY** → Reject and return error
6. **If REVIEW** → Create approval token, pause execution, wait for human decision
7. **Human approves** → Execute tool call and log result
8. **Human denies** → Reject and log denial

## Quickstart

### Prerequisites

- Node.js 18+
- pnpm 8+

### Installation```bash
# Clone the repository
git clone https://github.com/nik-kale/Secure-MCP-Gateway.git
cd Secure-MCP-Gateway

# Install dependencies
pnpm install

# Build all packages
pnpm build

Running the Local Ops Demo Server

The mcp-local-ops server simulates incident management operations and is perfect for testing the gateway without external dependencies.```bash

Run the local ops server

node packages/mcp-local-ops/dist/server.js


This server provides tools like:

- `list_services` (SAFE) - List all services and their status
- `get_service` (SAFE) - Get details about a specific service
- `simulate_incident` (MEDIUM) - Simulate an incident (requires approval)
- `scale_service` (MEDIUM) - Scale a service (requires approval)
- `restart_service` (HIGH) - Restart a service (requires approval)

### Using with Claude Desktop

Add this to your Claude Desktop MCP settings (`~/Library/Application Support/Claude/claude_desktop_config.json` on macOS):```json
{
  "mcpServers": {
    "local-ops": {
      "command": "node",
      "args": ["/path/to/Secure-MCP-Gateway/packages/mcp-local-ops/dist/server.js"]
    }
  }
}

Example: Policy in Action

When you try a safe read operation:```
Tool: list_services
Policy Decision: ALLOW (safe read-only operation)
Execution: Immediate
Audit: Logged to console/file


When you try a **medium-risk operation**:```
Tool: scale_service (replicas=10)
Policy Decision: REVIEW (medium-risk operation requires approval)
Execution: Paused
Response: { approvalToken: "abc-123-def", message: "Awaiting approval..." }

A human operator can then approve or deny:```typescript
gateway.grantApprovalAndExecute(approvalToken, approver, executor);
// OR
gateway.denyApproval(approvalToken, denier);


## Packages

### 1. `@secure-mcp-gateway/core`

Core security engine with policy evaluation, audit logging, and approval flow.

**Key exports:**

- `SecureMCPGateway` - Main orchestrator
- `PolicyEngine` - Rule-based policy evaluation
- `AuditLogger` - Structured logging
- `ApprovalManager` - Human-in-the-loop flow

### 2. `@secure-mcp-gateway/mcp-local-ops`

Demo MCP server for incident simulations. Self-contained, safe for testing.

### 3. `@secure-mcp-gateway/mcp-jira-ops`

Jira integration with read operations (search, get issue) and write operations requiring approval (add comment, transition issue).

**Configuration:**```bash
export JIRA_URL=https://yourcompany.atlassian.net
export JIRA_EMAIL=your-email@company.com
export JIRA_TOKEN=your-api-token

4. @secure-mcp-gateway/mcp-pulsemcp-discovery

Discovery tool that queries external MCP directories (PulseMCP, awesome-mcp-servers) to find ops-related MCP servers.

Example:```typescript
// Discover all ops-related servers
const servers = await discoveryClient.discoverOpsServers();

// Filter by tags
const k8sServers = await discoveryClient.discoverAll(['kubernetes', 'cloud']);


This package demonstrates that **Secure-MCP-Gateway integrates with and consumes existing MCP directories** rather than competing with them.

## Integration with MCP Directories

Secure-MCP-Gateway is designed to work **alongside** existing MCP ecosystems:

- **PulseMCP**: Directory of production-ready MCP servers
- **awesome-mcp-servers**: Curated list of community MCP servers

We provide `mcp-pulsemcp-discovery` as a reference for discovering and filtering servers from these directories. The gateway then adds security policies and approval workflows on top of those servers.

**We do not replace these directories. We make them safer for autonomous agent use in production.**

## How This Fits Into an Autonomous Ops Stack

Secure-MCP-Gateway is a foundational component for AI-powered SRE and support systems:```
┌─────────────────────────────────────────────────────────────┐
│  AutoRCA-Core (ADAPT-RCA)                                   │
│  Graph-based root cause analysis engine                     │
└────────────────┬────────────────────────────────────────────┘
                 │
                 ▼
┌─────────────────────────────────────────────────────────────┐
│  Ops-Agent-Desktop                                          │
│  Visual mission control for autonomous ops agents           │
└────────────────┬────────────────────────────────────────────┘
                 │
                 ▼
┌─────────────────────────────────────────────────────────────┐
│  Secure-MCP-Gateway  ◄── YOU ARE HERE                       │
│  Security-first access to production tools                  │
└────────────────┬────────────────────────────────────────────┘
                 │
      ┌──────────┼──────────┐
      ▼          ▼          ▼
   Jira      Kubernetes   Splunk   ... (via MCP servers)
  • AutoRCA-Core performs root cause analysis and suggests remediation
  • Ops-Agent-Desktop orchestrates missions and displays live progress
  • Secure-MCP-Gateway ensures agents can only perform approved actions on real infrastructure
  • MCP Servers (Jira, K8s, Splunk, etc.) provide the actual integrations

Together, these form a reference stack for autonomous reliability engineering.

Security and Safety Considerations

  1. Least Privilege: Default policy requires review for anything beyond safe reads
  2. Defense in Depth: Multiple layers: policy engine, approval flow, audit trail
  3. Fail Secure: If policy evaluation fails, default is to deny or require review
  4. Audit Everything: All decisions, approvals, and executions are logged
  5. Time-Limited Approvals: Approval tokens expire after a configurable TTL
  6. No Hardcoded Secrets: Credentials come from environment variables

See SECURITY_MODEL.md for full details.

Example Policy Configuration```json

{
"rules": [
{
"id": "deny-critical-delete",
"match": { "action": "delete_*", "minSeverity": "critical" },
"effect": "deny"
},
{
"id": "review-high-risk",
"match": { "minSeverity": "high" },
"effect": "review"
},
{
"id": "allow-safe-reads",
"match": { "minSeverity": "safe" },
"effect": "allow"
}
],
"defaultEffect": "review"
}
```

See examples/policy-config.json for a complete example.

Roadmap

  • [ ] HTTP API for approval UI (integrate with Slack, Teams, Ops-Agent-Desktop)
  • [ ] Support for external policy engines (OPA, Cedar)
  • [ ] Pre-built MCP servers for Kubernetes, Prometheus, Datadog
  • [ ] Integration with AutoRCA-Core for automated RCA + remediation
  • [ ] Fine-grained RBAC with team/user permissions
  • [ ] Webhook notifications for approval requests

Contributing

Contributions are welcome! This project aims to be a reference architecture for secure autonomous operations.

Please open issues for bugs, feature requests, or questions.

License

MIT

Related Projects

  • AutoRCA-Core - Agentic root cause analysis engine
  • Ops-Agent-Desktop - Visual mission control for ops agents
  • awesome-autonomous-ops - Curated list of autonomous ops tools
  • Model Context Protocol - Official MCP specification
  • PulseMCP - Directory of production MCP servers
  • awesome-mcp-servers - Community MCP server list

Built by Nik Kale as part of the autonomous operations and AI-powered reliability ecosystem.

常见问题

6 问
答案由本站依据条目字段整理,不引用上游原文
Secure MCP Gateway (secure-mcp-gateway-bba04718) 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Secure MCP Gateway (secure-mcp-gateway-bba04718) 怎么在 Claude Desktop、Claude 里配置?

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

Secure MCP Gateway (secure-mcp-gateway-bba04718) 收费吗?

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

Secure MCP Gateway (secure-mcp-gateway-bba04718) 需要 API Key 吗?

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

Secure MCP Gateway (secure-mcp-gateway-bba04718) 支持哪些客户端?

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

Secure MCP Gateway (secure-mcp-gateway-bba04718) 能提供哪些能力?

资料显示能力标签包括 安全、TypeScript、Claude、审计日志。具体工具清单以官方文档为准。

热门专题

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

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