zenmcp

ZenMCP is a minimalist, high-performance MCP server built with Go. It emphasizes a single binary deployment with zero external dependencies, making it ideal for lightweight game context polling and protocol handling. Use the included MCP framework to define your server behavior, register models, and respond to context requests quickly. With ZenMCP you can run a dedicated MCP server instance inside a container or as a standalone binary, taking advantage of Go’s efficiency and simplicity. The server exposes the Model Context Protocol endpoints and can be extended with custom handlers to manage context data, provide defaults, or override specific model fields as needed. Typical workflows involve starting the server, configuring model contexts, and then using MCP clients to query, subscribe, or push updates to model data managed by ZenMCP.

Prerequisites:

• Docker installed on your system (recommended for ease of use) or Go toolchain if you prefer building from source.
• Basic familiarity with MCP concepts (models, contexts, and requests).

Option A: Run via Docker (recommended for quick start)

1. Pull and run the ZenMCP image: docker pull hyperleex/zenmcp docker run -d --name zenmcp -p 8080:8080 -i hyperleex/zenmcp
2. Optional: provide a configuration file via environment or mounted volume if the image supports it (see env vars in README or image docs).

Option B: Build from source (Go)

1. Install Go from https://go.dev/dl/
2. Clone the repository: git clone https://github.com/slug/zenmcp.git cd zenmcp
3. Build the binary: go build -o zenmcp-server ./...
4. Run the server: ./zenmcp-server
5. Optional: provide a config file or env vars to customize MCP behavior.

Notes:

• If using Docker, check the image documentation for available ports, config files, and environment variables.
• For Go builds, ensure your GOPATH and module mode are correctly configured if you’re not using Go modules by default.

Tips:

• Since ZenMCP aims for zero external dependencies, keep your model definitions lightweight to maintain performance.
• Consider configuring environment variables to tune MCP protocol handlers, timeouts, and logging levels.
• If you encounter connection issues with MCP clients, verify the exposed port and ensure firewall rules allow traffic on that port.
• Use Docker for predictable deployments and easier distribution across environments. When building manually, compile for your target OS/architecture.
• Common issues include misconfigured models or mismatched MCP versions between client and server; ensure both sides agree on the model contexts you expose.