mcp-everything -docker-image

This MCP server image provides access to the MCP Everything server with multiple transports. The default configuration exposes the server in streamableHttp mode, and the image also supports STDIO and SSE transports via explicit invocation. You can run the server inside a container and connect clients using the appropriate transport protocol. For example, you can start the server in its default mode, or explicitly run the STDIO or SSE transports to integrate with clients that communicate over those streams. The server is based on the MCP Everything codebase and is exposed through a Node.js entry point (dist/index.js) inside the container.

To use the available tools, run the container with the desired transport. STDIO mode uses the container's standard input/output streams, SSE mode serves events over Server-Sent Events, and the default mode supports the Streamable HTTP transport. Refer to the following concrete runs to connect clients:

• Default (StreamableHttp): docker run -p 3001:3001 --rm -it tzolov/mcp-everything-server:v3
• STDIO: docker run -p 3001:3001 --rm -it tzolov/mcp-everything-server:v3 node dist/index.js stdio
• SSE: docker run -p 3001:3001 --rm -it tzolov/mcp-everything-server:v3 node dist/index.js sse

Each run maps port 3001 in the container to port 3001 on the host, enabling clients to connect via the chosen transport.

Prerequisites:

• Docker (and Docker Buildx for multi-arch images if needed)

Installation steps:

1. Pull the Docker image: docker pull tzolov/mcp-everything-server:v3

2. Run the image in default StreamableHttp mode: docker run -p 3001:3001 --rm -it tzolov/mcp-everything-server:v3

3. Optional: run STDIO transport (connect via the container's stdio handle): docker run -p 3001:3001 --rm -it tzolov/mcp-everything-server:v3 node dist/index.js stdio

4. Optional: run SSE transport (Server-Sent Events): docker run -p 3001:3001 --rm -it tzolov/mcp-everything-server:v3 node dist/index.js sse

Notes:

• Ensure port 3001 is available on the host if you plan to expose the service externally.
• The image defaults to the Streamable Http transport unless a specific transport is requested (stdio or sse).
• If you need multi-arch builds, you can follow Docker Buildx guidance to build and push the image for multiple architectures.

Tips and troubleshooting:

• If the container fails to start, check logs for missing dependencies or initialization errors from dist/index.js.
• When using STDIO, the host process must remain attached to the container's stdio streams for real-time communication.
• If you encounter port binding issues, ensure no other service on the host is using port 3001.
• The image name and tag shown (tzolov/mcp-everything-server:v3) reflect the published multi-arch image; use exactly that tag when pulling.
• This setup is based on the MCP Everything codebase; differences in upstream configurations may affect transport capabilities or protocol expectations.