MCP ConfigsMay 12, 2026·2 min read

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.

Agent ready

Safe staging for this asset

This asset is staged first. The copied prompt tells the agent to inspect the staged files and ask before activating scripts, MCP config, or global config.

Stage only · 17/100Policy: stage
Agent surface
Any MCP/CLI agent
Kind
Mcp Config
Install
Stage only
Trust
Trust: Established
Entrypoint
Asset
Safe staging command
npx -y tokrepo@latest install b723a04f-b034-5da6-84ed-68513d8ae950 --target codex

Stages files first; activation requires review of the staged README and plan.

Intro

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.

🙏

Source & Thanks

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

Discussion

Sign in to join the discussion.
No comments yet. Be the first to share your thoughts.

Related Assets