A plugin-based gateway that orchestrates other MCPs and allows developers to build upon it enterprise-grade agents.
If you already use MCP Gateway, the mcp gateway mcp server is the piece that lets your assistant work with it directly. A plugin-based gateway that orchestrates other MCPs and allows developers to build upon it enterprise-grade agents.
MCP Gateway is an advanced intermediary solution for Model Context Protocol (MCP) servers that centralizes and enhances your AI infrastructure.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Usage — This example enables the basic guardrail for token masking and xetrack tracing plugin for filesystem MCP:Basic — The Basic tool exposed by this serverPresidio — The Presidio tool exposed by this serverLasso — The Lasso tool exposed by this serverPrerequisites — To use Lasso Security's advanced AI safety guardrails, update your mcp.json configuration as follows:Features — 🔍 Full visibility into MCP interactions with an Always-on monitoringXetrack — xetrack is a lightweight package to track ml experiments, benchmarks, and monitor stractured dataParams — The Params tool exposed by this serverQuickstart — Let's say you use the filesystem list_directory tool on path ".", you can find the call parameters under logs/.logInstallation goes through your MCP client rather than a global install: point it at mcp-gateway on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Configuration is passed through the environment: LASSO_API_KEY, XETRACK_DB_PATH, XETRACK_LOGS_PATH, PYTHON_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
mcp.json configuration as follows: 1. Add the LASSO_API_KEY=<YOUR-API-KEY> to your environment variable or in the "env" section. 2. Insert other MCP servers configuration under key servers Example:Among the monitoring and observability options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP Gateway's toolset — Usage, Basic, Presidio and 6 more — is a fair guide to whether it matches your workflow. It is maintained by lasso-security; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Usage | This example enables the basic guardrail for token masking and xetrack tracing plugin for filesystem MCP: |
| Basic | The Basic tool exposed by this server. |
| Presidio | The Presidio tool exposed by this server. |
| Lasso | The Lasso tool exposed by this server. |
| Prerequisites | To use Lasso Security's advanced AI safety guardrails, update your mcp.json configuration as follows: |
| Features | 🔍 Full visibility into MCP interactions with an Always-on monitoring. |
| Xetrack | [xetrack](https://github.com/xdssio/xetrack) is a lightweight package to track ml experiments, benchmarks, and monitor stractured data. |
| Params | The Params tool exposed by this server. |
| Quickstart | Let's say you use the filesystem *list_directory* tool on path *"."*, you can find the call parameters under logs/<date>.log. |
```json
{
"mcpServers": {
"mcp-gateway": {
"command": "<python path>",
"args": [
"-m",
"mcp_gateway.server",
"--mcp-json-path",
"<path to claude_desktop_config>",
"--plugin",
"basic"
],
"servers": {
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem",
"."
]
}
}
}
}
}Configuration as documented by the project. Restart the client after saving.
mcp.json configuration as follows: 1. Add the LASSO_API_KEY=<YOUR-API-KEY> to your environment variable or in the "env" section. 2. Insert other MCP servers configuration under key servers Example:| Variable | Description | Required |
|---|---|---|
| LASSO_API_KEY | Credential the server authenticates with. | Yes |
| XETRACK_DB_PATH | Filesystem location the server is allowed to use. | Optional |
| XETRACK_LOGS_PATH | Filesystem location the server is allowed to use. | Optional |
| PYTHON_PATH | Filesystem location the server is allowed to use. | Optional |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.