Practical overview
When it fits
Use it when an MCP deployment needs an administrative gateway layer for authentication, tool selection or configurable request and response checks.
Who it is for
- Teams integrating MCP servers with AI clients
- Operators who want a configurable intermediary for MCP authentication, tool access and guardrails
Documented uses
- Place a gateway between an MCP client and one or more MCP servers.
- Authenticate access to the gateway.
- Discover server tools and limit which tools are exposed.
- Configure input and output guardrails for MCP server interactions.
Requirements & limits
The project is publicly available under the Apache-2.0 license. The README documents pip installation and a Docker image. Enkrypt cloud configuration requires an Enkrypt API key.
- The gateway acts as both an MCP server toward its client and an MCP client toward connected servers.
- Tool restrictions and guardrails are configured; the listed protections are not necessarily active by default.
- Local and Enkrypt cloud configuration are both documented.
- Optional sandbox isolation is documented for Docker, Podman or microVMs.
- The README describes forwarding logs to Enkrypt for monitoring as coming soon.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Install the package and generate a local configuration
Prepare a local Secure MCP Gateway installation and create its initial configuration file.
Before you start
- Python environment capable of creating a virtual environment
- pip
Steps
Create and activate a virtual environment.
Install the package with pip install secure-mcp-gateway.
Run secure-mcp-gateway generate-config to create the configuration file.
Expected outcome
The package is installed in the virtual environment and a local gateway configuration file is generated.
Guide limitations
- This covers installation and configuration generation, not running or connecting the gateway.
- The generate command does not overwrite an existing configuration by default.
Generate a cloud-backed configuration
Create a configuration that sources gateway server, project and user settings from Enkrypt cloud.
Before you start
- Secure MCP Gateway installed
- Enkrypt cloud API key
Steps
Run secure-mcp-gateway generate-config --provider enkrypt.
Fill in the Enkrypt API key in the generated configuration.
Expected outcome
A minimal cloud-provider configuration is generated with an Enkrypt API key and base URL fields, plus Enkrypt authentication and guardrail provider settings.
Guide limitations
- The guide covers generating and filling in the configuration, not connecting to or operating the gateway.
- The Enkrypt cloud API key must be supplied by the user.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 15 October 2026
- Original website title
- enkryptai/secure-mcp-gateway · Official homepage title · retained in its source language

