Esta página se muestra en inglés. Una traducción al español está en curso.
MCP ConfigsMay 12, 2026·2 min de lectura

MCPProxy — Secure MCP Tool Router + Quarantine

MCPProxy is a desktop/CLI proxy for MCP servers: manage upstreams, list tools to save context, and add safety via quarantine and optional Docker isolation.

Listo para agents

Staging seguro para este activo

Este activo primero queda en staging. El prompt copiado pide inspeccionar los archivos staged antes de activar scripts, config MCP o config global.

Stage only · 17/100Política: staging
Superficie agent
Cualquier agent MCP/CLI
Tipo
Mcp Config
Instalación
Stage only
Confianza
Confianza: Established
Entrada
Asset
Comando de staging seguro
npx -y tokrepo@latest install b723a04f-b034-5da6-84ed-68513d8ae950 --target codex

Primero deja archivos en staging; la activación requiere revisar el README y el plan staged.

Introducción

If you run many MCP servers, MCPProxy gives you one control plane: start/stop upstreams, inspect tool lists, and add isolation so “tool supply chain” risk is manageable.

Best for: Power users running multiple MCP servers across clients who want safer routing and easier debugging

Works with: macOS/Windows/Linux; upstream stdio MCP servers; optional Docker isolation (per README)

Setup time: 5–15 minutes

Key facts (verified)

  • README shows minimal config at ~/.mcpproxy/mcp_config.json and default data dir ~/.mcpproxy.
  • CLI includes upstream management commands like mcpproxy upstream list/restart/logs (per README command list).
  • Starts an HTTP server on :8080 by default (per README quickstart/usage).
  • GitHub: 213 stars · 24 forks; pushed 2026-05-12 (GitHub API verified).

Main

Treat MCPProxy like an “MCP firewall”:

  1. Keep a curated upstream list and disable anything you don’t use.
  2. Use mcpproxy tools list --server=NAME to validate what tools an upstream actually exposes before trusting it.
  3. Turn on Docker isolation for risky stdio servers so they can’t touch your host filesystem by default.
  4. Use doctor and upstream logs during incidents—debugging is faster when the proxy is the single chokepoint.

This is especially useful when you share MCP setups across multiple clients and machines.

FAQ

Q: Is it only a GUI? A: No. The README includes a full CLI (mcpproxy ...) plus an optional tray UI.

Q: Where is configuration stored? A: The README shows ~/.mcpproxy/mcp_config.json as the minimal config path.

Q: Does it help with safety? A: Yes. The README describes quarantine and Docker isolation modes for upstream servers.

🙏

Fuente y agradecimientos

Source: https://github.com/smart-mcp-proxy/mcpproxy-go > License: MIT > GitHub stars: 213 · forks: 24

Discusión

Inicia sesión para unirte a la discusión.
Aún no hay comentarios. Sé el primero en compartir tus ideas.

Activos relacionados