New:Introducing Socket Scanning for VS Code Marketplace Extensions.Learn more →
Get Started

@nano-step/shared-mcp-proxy

Package Overview
Dependencies
Maintainers
1
Versions
12
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@nano-step/shared-mcp-proxy

Shared MCP proxy infrastructure - run MCP servers once, share across tools

latest
npmnpm
Version
1.4.4
Version published
Weekly downloads
4
-69.23%
Maintainers
1
Weekly downloads
 
Created
Source

shared-mcp-proxy

Shared MCP proxy infrastructure that runs MCP servers once on the host machine and exposes them via SSE to multiple Docker containers and AI CLI tools. Eliminates memory-wasteful duplication (N containers × M CLIs × K MCPs).

Architecture

  • mcp-proxy runs on host (port 9902), manages stdio MCP servers
  • Containers connect via SSE over host.docker.internal:9902
  • nano-brain runs separately on host (port 3100)
  • playwright stays container-local (needs container Chromium)
  • Memory savings: ~3.4GB → ~330MB for typical setup (3 containers × 2 CLIs × 4 MCPs)

Quick Start

One command does everything (install + generate configs + start proxy):

npx @nano-step/shared-mcp-proxy

Or use individual commands:

npx @nano-step/shared-mcp-proxy install    # Install mcp-proxy + MCP packages
npx @nano-step/shared-mcp-proxy generate   # Generate configs for all tools
npx @nano-step/shared-mcp-proxy start      # Start mcp-proxy (auto-restarts on crash)
npx @nano-step/shared-mcp-proxy stop       # Stop mcp-proxy
npx @nano-step/shared-mcp-proxy status     # Check status + per-process memory usage
npx @nano-step/shared-mcp-proxy restart    # Restart after config changes

Server Management

npx @nano-step/shared-mcp-proxy list              # List all servers with enabled/disabled status
npx @nano-step/shared-mcp-proxy enable <name>     # Enable a server
npx @nano-step/shared-mcp-proxy disable <name>    # Disable a server

Logging

Debug logging is off by default. Enable it to see all MCP requests flowing through the proxy.

npx @nano-step/shared-mcp-proxy logs --enable     # Turn on debug logging
npx @nano-step/shared-mcp-proxy restart            # Apply the change
npx @nano-step/shared-mcp-proxy logs               # Tail the log (Ctrl+C to stop)
npx @nano-step/shared-mcp-proxy logs --status      # Check logging status + log file size
npx @nano-step/shared-mcp-proxy logs --disable     # Turn off (warnings only)
npx @nano-step/shared-mcp-proxy logs --clear       # Clear the log file

Or run the bash scripts directly:

./install.sh && ./generate.sh && ./start.sh

MCP Servers

ServerLocationDescription
Sequential-ThinkinghostDynamic problem-solving through chain-of-thought reasoning
graphql-toolshostGraphQL schema inspection and query execution
database-inspectorhostDatabase schema exploration and query tools
playwrightcontainerBrowser automation (requires container Chromium)
nano-brainexternalPersistent memory and code intelligence (port 3100)
linearhostLinear issue tracking integration
amplitudehostAmplitude analytics integration
figmahostFigma design file inspection

Supported Tools

ToolFormatConfig FileTop Key
opencodeopencodeconfig/opencode.mcp.jsonmcp
ampampconfig/amp.mcp.jsonmcpServers
claudeclaudeconfig/claude.mcp.jsonmcpServers
geminigeminiconfig/gemini.mcp.jsonmcpServers
codexcodexconfig/codex.mcp.tomlmcp_servers
qwenqwenconfig/qwen.mcp.jsonmcpServers
vscodevscodeconfig/vscode.mcp.jsonservers
clineclineconfig/cline.mcp.jsonmcpServers
roocoderoocodeconfig/roocode.mcp.jsonmcpServers
antigravityantigravityconfig/antigravity.mcp.jsonmcpServers

Configuration

  • mcp-config.json — master config, edit this to add/remove servers or tools
  • generate.sh — regenerate after editing mcp-config.json
  • Each server has "enabled": true/false to toggle without removing
  • Each server has "tools": [...] array to control which tools see it
  • Environment variables for secrets: set LINEAR_API_KEY, AMPLITUDE_API_KEY, AMPLITUDE_SECRET_KEY, FIGMA_API_KEY on host before starting mcp-proxy

Adding a New MCP Server

  • Add server entry to servers section in mcp-config.json:
    "my-server": {
      "command": "my-mcp-server",
      "args": [],
      "env": {},
      "location": "host",
      "tools": ["opencode", "amp", "claude"],
      "enabled": true
    }
    
  • If the server needs a new npm package, add install command to install.sh
  • Run ./generate.sh to regenerate all tool configs
  • Restart mcp-proxy: ./stop.sh && ./start.sh

Adding a New Tool

  • Add tool entry to tools section in mcp-config.json:
    "mytool": {
      "format": "mytool",
      "mcpKey": "mcpServers",
      "defaultPath": "config/mytool.mcp.json"
    }
    
  • Add generation block in generate.sh (copy existing tool block and modify)
  • Run ./generate.sh to create the config file

Custom Output Paths

Override default config paths with flags:

./generate.sh --opencode-out ~/custom/opencode.json \
              --amp-out ~/custom/amp.json \
              --claude-out ~/custom/claude.json \
              --gemini-out ~/custom/gemini.json \
              --codex-out ~/custom/codex.toml \
              --qwen-out ~/custom/qwen.json \
              --vscode-out ~/custom/vscode.json \
              --cline-out ~/custom/cline.json \
              --roocode-out ~/custom/roocode.json \
              --antigravity-out ~/custom/antigravity.json

FAQs

Package last updated on 09 Mar 2026

Related posts