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 allows users to utilize containerized MCP servers with LLM clients that expect to run MCP servers locally.
How to use MCP-Compose-Proxy-Shim?
To use MCP-Compose-Proxy-Shim, first ensure that MCP-Compose is installed and running. Then, clone the repository, install dependencies, and configure Claude Desktop to point to the MCP-Compose proxy. Finally, set the necessary environment variables before running Claude Desktop.
Key features of MCP-Compose-Proxy-Shim?
- Acts as a transparent bridge for local LLM clients to access remote MCP servers.
- Supports various MCP servers including filesystem and memory.
- Avoids limitations and costs associated with paid remote MCP servers.
- Leverages the flexibility of Docker-based MCP servers.
Use cases of MCP-Compose-Proxy-Shim?
- Connecting Claude Desktop to remote MCP servers for enhanced functionality.
- Running multiple MCP servers in Docker containers without local installation.
- Facilitating development and testing of LLM applications with remote resources.
FAQ from MCP-Compose-Proxy-Shim?
-
What are the requirements to use MCP-Compose-Proxy-Shim?
You need Node.js v14 or later, Claude Desktop or another MCP-compatible LLM client, and MCP-Compose running with a proxy.
-
Is there any cost associated with using MCP-Compose-Proxy-Shim?
No, it is free to use as it connects to your own Docker containers.
-
Can I use it with other LLM clients?
Yes, as long as they are compatible with the Model Context Protocol (MCP).