Server facts
MCP Gateway
Project
- Author
- lasso-security
- Repository
- github.com/lasso-security/mcp-gateway
- Website
- www.lasso.security/
- License
- MIT
- Category
- MCP Gateways & Proxies
Tech
- Runtime / language
- pythonPython
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 396
- Last commit
- Data as of
Tags
- Mcp Proxy
- Pii
- Secret Masking
- Security Guardrails
- Tracing
Overview
MCP Gateway from Lasso Security sits between an agent and its configured MCP servers. It reads client configuration, manages the underlying server lifecycles, and exposes a common discovery and execution interface. Its two named proxy tools let agents inspect available server metadata and invoke downstream capabilities. Requests and responses pass through enabled plugins, allowing the gateway to apply security processing independently of each backend's own implementation. The README presents this as a way to centralize sensitive-data controls and visibility rather than configuring equivalent safeguards separately for every server. Server definitions are nested beneath the gateway entry in the client configuration.
Plugin choice determines the protection provided. The basic plugin masks supported credential patterns, Presidio handles personal information, and the Lasso plugin adds API-backed checks for secrets, PII, prompt injection, harmful content, and custom policies. Presidio requires an extra installation, while Lasso requires an API key. Xetrack is an optional tracing integration with configurable database and log locations. A scanner can inspect server reputation and tool descriptions before loading backends, block risky entries, and write results into configuration. Its states include manual skipping, so scan results are controls to review rather than universal guarantees of safety. Installation is through pip, and the documented local command points to the MCP configuration and selects plugins. Docker setup is also described.
Install & configure
Requirements
- Python and pip
- The mcp-gateway package
- Xetrack installed for this example
- An MCP configuration containing nested server definitions
mcp-gateway --mcp-json-path '~/.cursor/mcp.json' -p basic -p xetrackInstall with pip install mcp-gateway and pip install xetrack. Replace the configuration path if needed. This example enables basic masking and tracing; Lasso API credentials and Presidio extras are needed only for those plugins.
Examples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.
Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Use Settings → Developer → Edit Config when available. Do not assume a Linux configuration path; check the client documentation for your platform. Remote servers use the app’s connector flow when supported, not the local stdio file shown here. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"mcp-gateway-lasso-security": {
"command": "mcp-gateway",
"args": [
"--mcp-json-path",
"~/.cursor/mcp.json",
"-p",
"basic",
"-p",
"xetrack"
],
"env": {}
}
}
}Config file · Project: .cursor/mcp.json
User: ~/.cursor/mcp.json
The project path is relative to the workspace root. The tilde denotes your user home directory. Use Cursor’s MCP settings to confirm which configuration and scope your installed version is reading. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"mcp-gateway-lasso-security": {
"command": "mcp-gateway",
"args": [
"--mcp-json-path",
"~/.cursor/mcp.json",
"-p",
"basic",
"-p",
"xetrack"
],
"env": {}
}
}
}Config file · Workspace: .vscode/mcp.json
For user scope, use the “MCP: Open User Configuration” command if available. Do not guess a user configuration path across operating systems, profiles, containers, or remote workspaces; check the client documentation. Merge this example with existing settings; do not overwrite unrelated servers.
{
"servers": {
"mcp-gateway-lasso-security": {
"type": "stdio",
"command": "mcp-gateway",
"args": [
"--mcp-json-path",
"~/.cursor/mcp.json",
"-p",
"basic",
"-p",
"xetrack"
],
"env": {}
}
}
}Config file · macOS/Linux: ~/.codeium/windsurf/mcp_config.json
Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json
Open the MCP configuration through Windsurf’s settings when possible to confirm the active file. Paths can differ in managed or future releases; check the client documentation if this location is not present. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"mcp-gateway-lasso-security": {
"command": "mcp-gateway",
"args": [
"--mcp-json-path",
"~/.cursor/mcp.json",
"-p",
"basic",
"-p",
"xetrack"
],
"env": {}
}
}
}Config file · Project scope: .mcp.json at the repository root
The project file uses mcpServers. For user scope, use claude mcp add --scope user rather than assuming .mcp.json in your home directory is the user configuration. Check the client documentation for managed settings and storage details. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"mcp-gateway-lasso-security": {
"type": "stdio",
"command": "mcp-gateway",
"args": [
"--mcp-json-path",
"~/.cursor/mcp.json",
"-p",
"basic",
"-p",
"xetrack"
],
"env": {}
}
}
}Examples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.
Tools
Source: repository README. Tool descriptions are a documented snapshot, not a live capability check.
| Tool | What it does |
|---|---|
| get_metadata | Inspect available proxied servers and their capabilities. |
| run_tool | Invoke a downstream capability with configured request and response filtering. |
Names, permissions, and defaults can change. Check the current upstream documentation before granting access.
Use cases
- Mask supported credentials in proxied tool exchanges
- Apply PII filtering to connected server responses
- Trace tool calls through the optional Xetrack plugin
- Scan server reputation and tool descriptions before loading
Strengths
- Applies request and response filtering across different MCP backends
- Separates basic masking, PII, and API-backed policy plugins
- Includes optional pre-load scanning and tracing
Limitations
- Presidio and Xetrack require additional dependencies
- Advanced Lasso guardrails need an API key and external API checks
- Scanner results can be manually overridden
Frequently asked questions
Independent listing, not an affiliation or security review. Grant the least access needed and verify the upstream instructions before running code.
