About this integration
Permission tiers, approval gates, and audit logging for MCP servers - the server is the gatekeeper
- Transport
- stdio
- Authentication
- none
- Initial setup
- none
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.2.0
- Package
- mcp-gatehouse
- Last compatibility test
- Not independently tested
Connect your agent
mcp-gatehousePublisher documentation was reviewed without installing or running the demo. This is an in-server authorization gate, not authentication, transport encryption, or a sandbox. The shipped demo uses a terminal approver; without a terminal, gated actions deny rather than silently proceed, and production approvers are expected to be out-of-band.
Capabilities: Apply permission tiers to MCP tools, Require approval for selected tool tiers, Write redacted append-only tool audit logs
Connected profiles
Additional details
io.github.nickgeorgeseo/gatehouse
Source ↗ · Checked 2026-09-170.2.0
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17pypi
Source ↗ · Checked 2026-09-17mcp-gatehouse
Source ↗ · Checked 2026-09-190.2.0
Source ↗ · Checked 2026-09-19The package ships an executable order-desk MCP demo over stdio. The server can remain client-managed, while approval-gated calls require the documented terminal or out-of-band approver and fail closed when none is available.
Source ↗ · Checked 2026-09-19The publisher explicitly states that gatehouse is not authentication. The reviewed local stdio demo has no separate connection-authentication configuration.
Source ↗ · Checked 2026-09-19Launch the packaged mcp-gatehouse-demo or mcp-gatehouse executable as a stdio MCP server; no remote endpoint is part of the existing catalog connection.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19