mcp-gateway MCP — Cas d'usage, Installer & Démo en direct

Pourquoi l'utiliser

Fonctionnalités clés

Proxies multiple upstream MCP servers with a unified interface
Plugins: basic secret-mask, Presidio PII, Lasso AI safety, Xetrack tracing, Security Scanner
Blocks or redacts instead of just logging — actually prevents leaks
Prompt injection detection on tool inputs
Drop-in via pip install mcp-gateway + mcp.json config

Démo en direct

Aperçu en pratique

gateway.replay ▶ prêt

0/0

Installer

Choisissez votre client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "gateway": {
      "command": "uvx",
      "args": [
        "mcp-gateway"
      ],
      "_inferred": true
    }
  }
}

Ouvrez Claude Desktop → Settings → Developer → Edit Config. Redémarrez après avoir enregistré.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "gateway": {
      "command": "uvx",
      "args": [
        "mcp-gateway"
      ],
      "_inferred": true
    }
  }
}

Cursor utilise le même schéma mcpServers que Claude Desktop. La config projet l'emporte sur la globale.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "gateway": {
      "command": "uvx",
      "args": [
        "mcp-gateway"
      ],
      "_inferred": true
    }
  }
}

Cliquez sur l'icône MCP Servers dans la barre latérale Cline, puis "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "gateway": {
      "command": "uvx",
      "args": [
        "mcp-gateway"
      ],
      "_inferred": true
    }
  }
}

Même format que Claude Desktop. Redémarrez Windsurf pour appliquer.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "gateway",
      "command": "uvx",
      "args": [
        "mcp-gateway"
      ]
    }
  ]
}

Continue utilise un tableau d'objets serveur plutôt qu'une map.

~/.config/zed/settings.json

{
  "context_servers": {
    "gateway": {
      "command": {
        "path": "uvx",
        "args": [
          "mcp-gateway"
        ]
      }
    }
  }
}

Ajoutez dans context_servers. Zed recharge à chaud à la sauvegarde.

claude mcp add gateway -- uvx mcp-gateway

Une seule ligne. Vérifiez avec claude mcp list. Supprimez avec claude mcp remove.

Cas d'usage

Usages concrets : mcp-gateway

Expose internal MCPs to Claude without leaking PII

👤 Enterprise security, platform teams ⏱ ~45 min advanced

Quand l'utiliser : Your internal tools (postgres, CRM) would leak customer names / emails / SSNs into LLM context if used directly.

Prérequis

pip install mcp-gateway[presidio] — presidio extra pulls spaCy models

Déroulement

Wire upstream MCPs through gateway

Configure mcp-gateway with upstream postgres MCP; enable the Presidio plugin with redaction for EMAIL, PHONE, US_SSN.✓ Copié

→ Config file with plugin chain
Test redaction

Run a query returning customer emails; confirm the gateway replaces them with <EMAIL> placeholders before reaching the LLM.✓ Copié

→ Claude sees only placeholders

Résultat : LLM-usable tool access without raw PII crossing the boundary.

Pièges

Over-redaction breaks downstream joins — Use consistent pseudonyms (Presidio supports hash-based) so the LLM can still reason across redacted fields

Combiner avec : postgres

Block prompt injection attacks from tool outputs

👤 Security-aware agent builders ⏱ ~30 min advanced

Quand l'utiliser : Your agent uses fetch/web-browsing MCPs — tool outputs can contain 'ignore previous instructions' payloads.

Prérequis

Lasso API key — lasso.security signup

Déroulement

Enable Lasso plugin

Turn on the Lasso plugin in gateway config with LASSO_API_KEY set. Put fetch MCP behind it.✓ Copié

→ Plugin active; outputs scanned
Test

Have Claude fetch a URL containing known prompt-injection test string; verify it's neutralized before reaching the model.✓ Copié

→ Injection blocked or flagged

Résultat : Defense against tool-output injection.

Pièges

False positives block legit content — Start with 'warn' mode, review logs before switching to 'block'

Combiner avec : fetch · firecrawl

Log every MCP tool call for compliance audit

👤 Compliance / security audit teams ⏱ ~20 min intermediate

Quand l'utiliser : You need SOC2-style evidence of what the LLM asked tools to do.

Déroulement

Enable Xetrack plugin

Turn on Xetrack with SQLite destination. Route all MCPs through the gateway.✓ Copié

→ mcp_calls.db being written
Query audit log

Show me all tool calls in the last 24h where the tool name contains 'delete' or 'drop'.✓ Copié

→ Destructive-op audit trail

Résultat : Queryable audit database for compliance.

Pièges

Log DB grows unbounded — Rotate and archive monthly

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

gateway + postgres + fetch

DB + web access with PII + injection guards

Put postgres and fetch behind mcp-gateway with presidio + lasso plugins; use normally from Claude.✓ Copié

Outils

Ce que ce MCP expose

Outil	Entrées	Quand appeler	Coût
<upstream tools>	Depends on upstream MCP	Gateway is transparent — you call upstream tools as usual	upstream cost + plugin overhead

Coût et limites

Coût d'exécution

Quota d'API: Lasso plugin requires Lasso API key (paid tier)
Tokens par appel: Plugin overhead ~50-200ms per call; redaction reduces tokens
Monétaire: Gateway itself free. Lasso plugin: see lasso.security pricing.
Astuce: Run basic + presidio plugins for free; only add Lasso if you need advanced injection detection.

Sécurité

Permissions, secrets, portée

Stockage des identifiants : Plugin API keys in env vars (LASSO_API_KEY, etc.)

Sortie de données : Varies by plugin: basic + presidio are local; Lasso sends samples to Lasso cloud for analysis

Plugins can false-positive; always test in 'warn' mode before 'block'.
Lasso sends tool inputs/outputs to their servers — assess against your data policy.

Dépannage

Erreurs courantes et correctifs

Presidio plugin fails to load

Install extra: pip install 'mcp-gateway[presidio]' and download spaCy model: python -m spacy download en_core_web_lg.

Upstream MCP not responding through gateway

Test the upstream directly first; then verify gateway mcp.json command/args match exactly.

Performance drop

Plugin chain order matters — put cheapest (basic mask) first, Lasso last.

Alternatives

mcp-gateway vs autres

Alternative	Quand l'utiliser	Compromis
Claude's built-in output filters	You only use Claude and trust its own redaction	No customization, no audit trail
Concierge SDK	You want a framework for writing MCPs, not a security proxy	Different problem space

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills