MCP.so
登录

MCP Compose Proxy Shim

@phildougherty

基本信息

分类

其他

传输方式

stdio

作者

phildougherty

关于 MCP Compose Proxy Shim

Trick claude desktop into using remote mcp servers with mcp-compose

MCP Compose Proxy Shim 配置

暂无标准配置

该服务器的 README 中没有可解析的 MCP 配置块,请前往代码仓库查看安装说明。

代码仓库

MCP Compose Proxy Shim 工具

工具列表暂未提供

当前收录暂时没有可展示的工具列表,不代表服务没有工具。请查阅项目文档了解支持的能力。

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is MCP-Compose-Proxy-Shim?

MCP-Compose-Proxy-Shim is a bridge that connects local LLM clients (such as Claude Desktop) to remote MCP-Compose servers running in Docker containers. It intercepts local MCP server calls and redirects them to a remote MCP-Compose proxy, acting as a transparent bridge.

How to use MCP-Compose-Proxy-Shim?

Clone the repository, run npm install, and make scripts executable with chmod +x bin/npx lib/mcp-shim.js. Ensure MCP-Compose is running (mcp-compose up and mcp-compose proxy). Edit Claude Desktop’s configuration file (claude_desktop_config.json) to point to the bin/npx script with your desired MCP server arguments. Set environment variables such as MCP_PROXY_URL (default http://localhost:9876) and MCP_API_KEY before launching Claude Desktop, then restart the client.

Key features of MCP-Compose-Proxy-Shim

  • Use Claude Desktop with MCP servers running in Docker containers
  • Avoid limitations and costs of paid remote MCP servers
  • Leverage all power and flexibility of Docker-based MCP servers
  • Works with filesystem, memory, weather and other MCP servers
  • Includes security features: path sanitization, rate limiting, API key authentication
  • Supports response caching, retry logic, and configurable logging

Use cases of MCP-Compose-Proxy-Shim

  • Run containerized filesystem, memory, or weather MCP servers with Claude Desktop
  • Use local LLM clients with Docker-based MCP servers without requiring a Claude Max plan
  • Combine multiple containerized MCP servers behind a single proxy for a local client
  • Securely expose remote MCP servers to desktop clients with authentication and rate limiting

常见问题

1

What are the system requirements?

Node.js v14 or later, Claude Desktop or another MCP-compatible LLM client, and a running MCP-Compose instance with its proxy.

2

How does the shim communicate with MCP-Compose?

The shim talks to Claude via stdin/stdout as expected, then forwards all requests to the MCP-Compose proxy behind the scenes. Results flow back through the proxy to the shim and then to Claude.

3

What environment variables can I configure?

Key variables include `MCP_PROXY_URL` (proxy address), `MCP_API_KEY`, `MCP_DEBUG`, `MCP_LOG_LEVEL`, `MCP_CACHE`, `MCP_CACHE_TTL_MS`, `MCP_MAX_RETRIES`, and `MCP_LOG_FILE`. Defaults are documented in the README.

4

Where are logs written?

Logs go to stderr when `MCP_DEBUG=true`, or to a file at `/tmp/mcp-shim-[server].log` when `MCP_LOG_FILE=true`.

5

What security features are included?

Path sanitization to prevent directory traversal, rate limiting to prevent abuse, request size limiting, API key authentication, and secure error handling.

评论

其他 分类下的更多 MCP 服务器