mcp-gatekeeper
Secure MCP server with JSON plugin configuration, multiple sandbox modes, glob-based policy control, and MCP Apps UI support
Install / Use
claude mcp add takeshy -- npx -y github:takeshy/mcp-gatekeeperIf the server publishes to npm under a different name, use that package instead — check the repo README.
MCP Server
Model Context Protocol server
Quality Score
Category
Customer SupportSupported Platforms
Tags
Our assessment of mcp-gatekeeper
mcp-gatekeeper scores 83/100 on our quality scale, 267th of 329 Customer Support skills we index.
Its MCP Server is 30 KB long, well organised into 58 sections with 34 code examples: a thorough specification that gives an agent plenty to work with.
It has 3 GitHub stars, so there is little community track record yet; judge it on its content.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so mcp-gatekeeper is actively maintained.
- Our last check on 2026-08-12 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 80/100, with 2 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
mcp-gatekeeper compared with similar skills
All 4 of these similar skills score higher than mcp-gatekeeper; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| mcp-gatekeeper (this skill)by takeshy | 83 | 3 | 53d ago | MCP Server |
| Agent-Reachby Panniantong | 100 | 106.6k | 5d ago | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 78.3k | today | CLAUDE.md |
| CowAgentby zhayujie | 100 | 47.7k | today | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 90.4k | 1d ago | MCP Server |
Frequently asked questions
- How do I install mcp-gatekeeper?
- Run
claude mcp add takeshy -- npx -y github:takeshy/mcp-gatekeeper. The install tabs above show the steps for each supported agent. - Which AI agents does mcp-gatekeeper work with?
- It is written for Claude Code and Claude Desktop, as a MCP Server file. Other agents that read the same format can often use it too.
- Is mcp-gatekeeper safe to use?
- It declares no license and scores 80/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is mcp-gatekeeper still maintained?
- The repository was last updated about 2 months ago, so mcp-gatekeeper is actively maintained.
Skill content
View source on GitHubMCP Gatekeeper
A security-focused MCP (Model Context Protocol) gateway that enables AI assistants to safely execute shell commands with fine-grained access control.
Why MCP Gatekeeper?
- Security First: Multi-layer protection with policy-based argument validation, environment variable filtering, and sandboxing (bubblewrap/WASM)
- Flexible Deployment: Run as stdio server for Claude Desktop, HTTP API for web services, or bridge proxy for existing MCP servers
- Bridge Mode: Expose any stdio-based MCP server (Playwright, filesystem, etc.) over HTTP with authentication, rate limiting, and large response handling
- OAuth 2.0 Ready: Authorization Code flow with PKCE for MCP clients
- Plugin Architecture: Define tools via simple JSON files with glob-based argument patterns
- Rich UI Support: Generate interactive HTML interfaces via MCP Apps for command outputs
Architecture
┌─────────────────────────────────────────────────────────────────────────────┐
│ MCP Gatekeeper │
├─────────────────────────────────────────────────────────────────────────────┤
│ │
│ ┌─────────────────────────────────────────────────────────────────────┐ │
│ │ Protocol Layer │ │
│ │ ├─ Stdio Mode: Direct MCP client integration │ │
│ │ ├─ HTTP Mode: JSON-RPC 2.0 with Bearer token auth │ │
│ │ └─ Bridge Mode: HTTP proxy to stdio MCP servers │ │
│ └─────────────────────────────────────────────────────────────────────┘ │
│ ↓ │
│ ┌─────────────────────────────────────────────────────────────────────┐ │
│ │ Authentication & Rate Limiting │ │
│ │ ├─ API Key: Simple Bearer token authentication │ │
│ │ └─ OAuth 2.0: Authorization Code + PKCE │ │
│ └─────────────────────────────────────────────────────────────────────┘ │
│ ↓ │
│ ┌─────────────────────────────────────────────────────────────────────┐ │
│ │ Plugin Configuration │ │
│ ├─────────────────────────────────────────────────────────────────────┤ │
│ │ │ │
│ │ Allowed Env Variables: ["PATH", "HOME", "LANG", "GIT_*"] │ │
│ │ │ │
│ │ ┌─────────────────────────────────────────────────────────────┐ │ │
│ │ │ Tool: "git-status" │ │ │
│ │ │ ├─ Command: git │ │ │
│ │ │ ├─ Args Prefix: ["status"] │ │ │
│ │ │ ├─ Allowed Args: ["", "--short"] │ │ │
│ │ │ ├─ Sandbox: none │ │ │
│ │ │ └─ UI Type: log │ │ │
│ │ └─────────────────────────────────────────────────────────────┘ │ │
│ │ │ │
│ │ ┌─────────────────────────────────────────────────────────────┐ │ │
│ │ │ Tool: "ls" │ │ │
│ │ │ ├─ Command: ls │ │ │
│ │ │ ├─ Allowed Args: ["-la", "*"] │ │ │
│ │ │ ├─ Sandbox: bubblewrap │ │ │
│ │ │ └─ UI Type: log │ │ │
│ │ └─────────────────────────────────────────────────────────────┘ │ │
│ │ │ │
│ │ ┌─────────────────────────────────────────────────────────────┐ │ │
│ │ │ Tool: "ruby" │ │ │
│ │ │ ├─ Allowed Args: ["-e **", "*.rb"] │ │ │
│ │ │ ├─ Sandbox: wasm │ │ │
│ │ │ └─ WASM Binary: /opt/ruby-wasm/usr/local/bin/ruby │ │ │
│ │ └─────────────────────────────────────────────────────────────┘ │ │
│ │ │ │
│ └─────────────────────────────────────────────────────────────────────┘ │
│ ↓ │
│ ┌─────────────────────────────────────────────────────────────────────┐ │
│ │ Policy Evaluation (glob pattern matching on arguments) │ │
│ └─────────────────────────────────────────────────────────────────────┘ │
│ ↓ │
│ ┌─────────────────────────────────────────────────────────────────────┐ │
│ │ Command Execution with Sandboxing │ │
│ │ ├─ None: Path validation only │ │
│ │ ├─ Bubblewrap: Linux namespace isolation (bwrap) │ │
│ │ └─ WASM: WebAssembly sandbox (wazero runtime) │ │
│ └─────────────────────────────────────────────────────────────────────┘ │
│ ↓ │
│ ┌─────────────────────────────────────────────────────────────────────┐ │
│ │ Audit Logging (SQLite) & MCP Apps UI Rendering │ │
│ └─────────────────────────────────────────────────────────────────────┘ │
│ │
└─────────────────────────────────────────────────────────────────────────────┘
Features
- Three Operating Modes: stdio, http, bridge
- JSON Plugin Configuration: Define tools via simple JSON files
- Flexible Sandboxing: none, bubblewrap, or WASM isolation
- Policy-Based Access Control: Glob patterns for argument validation
- OAuth 2.0 Authentication: Authorization Code flow with mandatory PKCE
- MCP HTTP: Stateless MCP 2026-07-28 with automatic legacy session compatibility
- TUI Admin Tool: Manage OAuth clients via terminal UI
- Optional Audit Logging: SQLite-based logging for all modes
- Large Response Handling: Automatic file externalization in bridge mode
- MCP Apps UI Support: Rich HTML interfaces for tool outputs
Operating Modes
| Mode | Use Case | |------|----------| | stdio | Direct integration with MCP clients (Claude Desktop, etc.) | | http | Expose shell commands as HTTP API | | bridge | Proxy existing stdio MCP servers over HTTP |
Mode is auto-detected: --addr implies http mode, --upstream implies bridge mode.
Installation
go install github.com/takeshy/mcp-gatekeeper/cmd/server@latest
Or download from Releases.
Quick Start
1. Create a Plugin Directory
Create a directory with plugin.json and optional templates:
my-plugin/
├── plugin.json
└── templates/
└── custom.html
plugin.json:
{
"tools": [
{
"name": "git-status",
"description": "Show git repository status",
"command": "git",
"args_prefix": ["status"],
"allowed_arg_globs": ["", "--short", "--branch"],
"sandbox": "none",
"ui_type": "log"
},
{
"name": "ls",
"description": "List directory contents",
"command": "ls",
"args_prefix": ["-la"],
"allowed_arg_globs": ["", "**"],
"sandbox": "bubblewrap",
"ui_type": "log"
}
],
"allowed_env_keys": ["PATH", "HOME", "LANG"]
}
Note: args_prefix defines fixed arguments that are automatically prepended. With args_prefix: ["-la"], calling ls with args: ["/tmp"] executes ls -la /tmp. The allowed_arg_globs validates user-provided args only (not the prefix).
2. Start the Server
Stdio Mode (for MCP clients like Claude Desktop):
./mcp-gatekeeper --mode=stdio \
--root-dir=/home/user/projects \
--plugin-file=my-plugin/plugin.json \
--api-key=your-secret-key
Claude Code Configuration (~/.claude/settings.json):
{
"mcpServers": {
"gatekeeper": {
"command": "/path/to/mcp-gatekeeper",
"args": [
"--root-dir", "/home/user/projects",
"--plugins-dir", "/path/to/plugins"
]
}
}
}
HTTP Mode:
./mcp-gatekeeper --mode=http \
--root-dir=/home/user/projects \
--plugins-dir=plugins/ \
--api-key=your-secret-key \
--addr=:8080
Bridge Mode (proxy existing MCP servers):
./mcp-gatekeeper --mode=bridge \
--upstream='npx @playwright/mcp --headless' \
--api-key=your-secret-key \
--addr=:8080
3. Test It
# List available tools
curl -X POST http://localhost:8080/mcp \
-H "Authorization: Bearer your-secret-key" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
# Execute a tool
curl -X POST http://localhost:8080/mcp \
-H "Authorization: Bearer your-secret-key" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"ls","arguments":{"args":["-la"]}}}'
Plugin Configuration
Single Plugin File
./mcp-gatekeeper --plugin-file=my-plugin/plugin.json ...
Plugin Directory (Multiple Plugins)
./mcp-gatekeeper --plugins-dir=plugins/ ...
Supports two formats:
- Flat files:
plugins/*.jsonfiles are loaded directly - Subdirectories:
plugins/*/plugin.jsondirectories are loaded
plugins/
├── git/
│ ├── plugin.json
│ └── templates/
│ ├── log.html
│ └── diff.html
├── shell/
│ ├── plugin.json
│ └── templates/
│ └── table.html
└── simple.json # Flat file also supported
Tool names must be unique across all plugins.
Plugin File Format
{
"tools": [
{
"name": "tool-name",
"description": "Tool description",
"command": "/path/to/executable",
"args_prefix": ["subcommand"],
"allowed_arg_globs": ["pattern1", "pattern2"],
"sandbox": "none|bubblewrap|wasm",
"wasm_binary": "/path/to/binary.wasm",
"ui_type": "log|table|json",
"ui_template": "templates/custom.html",
"input_schema": {"oneOf": [{"required": ["args"]}]}
}
],
"allowed_env_keys": ["PATH", "HOME", "CUSTOM_*"]
}
| Field | Required | Description |
|-------|----------|-------------|
| name | Yes | Unique tool name |
| description | No | Tool description |
| command | Yes* | Executable path (*not required for wasm) |
| args_prefix | No | Fixed arguments prepended to user args (e.g., ["-la"]
Truncated for display — read the full file on GitHub.
Related Skills
Agent-Reach
106.6kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
headroom
78.3kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
CowAgent
47.7kOpen-source personal AI assistant & Agent Harness. Plans tasks, runs tools and skills, self-evolves with memory and knowledge. Multi-agent, multi-model, multi-channel. Lightweight, extensible, one-line install.
Scrapling
90.4k🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
