Practical overview
When it fits
Use it when an agent client needs a configured intermediary to manage and expose multiple MCP servers, particularly when you want to select gateway plugins for sanitization or tracing.
Who it is for
- Developers connecting an LLM or AI agent to multiple MCP servers.
- Teams configuring a gateway layer for MCP tools in a client such as Cursor or Claude Desktop.
- Python-based deployments that want selectable gateway plugins for sanitization or tracing.
Documented uses
- Configure multiple MCP servers behind one gateway.
- Manage the lifecycle of configured MCP servers.
- Discover proxied server tools and resources through a shared interface.
- Route tool calls through request and response sanitization.
- Enable plugins such as token masking or tracing.
Requirements & limits
The project is presented as a public GitHub repository with an MIT license. The README documents Python package installation and Docker build instructions.
- Requires an MCP client configuration file and server definitions under the servers key.
- Plugins are selected at launch; some may require optional dependencies.
- The documented gateway tools are get_metadata and run_tool.
- The security scanner is described as checking server reputation and risks before loading, but its detailed behavior is not specified.
- The README includes both Cursor and Claude Desktop configuration examples.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Install and configure MCP Gateway in a client
Install the Python package and add the gateway plus a configured MCP server to a client configuration.
Before you start
- Python environment with pip
- An MCP client configuration file such as mcp.json or claude_desktop_config.json
- The command and arguments for each MCP server to proxy
Steps
Install the package with pip install mcp-gateway.
Set --mcp-json-path to the relevant MCP configuration file.
Add the gateway under the client's mcpServers configuration and list the proxied MCP server under its servers key.
Select plugins with repeated --plugin or -p arguments when needed; the README's Cursor example uses basic and xetrack.
Expected outcome
A client configuration that points to MCP Gateway and declares a proxied server.
Guide limitations
- This describes installation and configuration; it does not verify that the gateway or configured server starts successfully.
- Some plugins may require optional dependencies.
Build the documented Docker image
Build a Docker image for MCP Gateway, with optional plugin dependencies specified during the build.
Before you start
- A cloned copy of the repository
- Docker
- The desired optional plugin dependencies, if any
Steps
Build the image with docker build -t mcp/gateway ..
If plugin extras are needed, use the INSTALL_EXTRAS build argument with a comma-separated value such as presidio,xetrack.
Use the documented Docker client configuration pattern to mount the MCP configuration and pass gateway arguments.
Expected outcome
A locally built image and a documented pattern for invoking it through a client configuration.
Guide limitations
- The README's invocation example contains environment-specific paths and a LASSO_API_KEY placeholder; adapt these to the local setup.
- The documented recipe does not verify a successful build or runtime.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 17 October 2026
- Original website title
- lasso-security/mcp-gateway · Official homepage title · retained in its source language