mcp-builder

To consolidate multiple MCPs into a single Docker image, you need to build a domain MCP server using a monorepo structure with a domains/ directory, shared utilities, and a tool registration API via register_tools. This approach packages several services into one pre-built image to simplify deployment and ongoing management.

A domain MCP server is a consolidated server that merges multiple individual MCPs into a single domain-specific image. You need one when managing several LLM-enabled external service integrations becomes operationally complex and you want to reduce overhead.

Yes, you can create new domain MCPs from scratch using Python FastMCP or Node MCP SDK patterns. The process requires a standardized monorepo structure including a Dockerfile, pyproject.toml, and Kubernetes manifests to ensure reliable rollout.

Yes, building a domain MCP server requires Kubernetes manifests to provide standardized deployment. Along with Docker packaging and health tooling, these manifests ensure consistent and reliable rollout for your consolidated domain images.

You can merge external services like plex and arr-suite by applying the domain consolidation pattern to build a domain MCP from existing services. This involves structuring your monorepo with a domains/ directory and utilizing the register_tools API for tool registration.

Consolidating MCPs into a single domain server requires maintaining a strict monorepo structure with shared utilities and specific build files like pyproject.toml. This approach may introduce deployment bottlenecks if one service within the consolidated image requires frequent updates.