Build MCP

🚀 Docker Build MCP TypeScript Server

This project is a Docker Build MCP server that fully adheres to the MCP (model context protocol) standard, providing seamless integration with MCP clients and efficient Docker image management.

✨ Features

• Full MCP Standard Support: 100% compatible with tool discovery and execution in MCP clients such as Cursor and Claude.
• Automated Docker Image Management: Offers APIs for major Docker CLI functions like build, run, stop, rm, rmi, and push.
• SSE (Server-Sent Events) and Stdio Mode Support: Enables real - time event streaming and standard input/output operations.
• Highly Scalable Structure: Each Docker command is implemented as an independent tool, facilitating easy maintenance and expansion.
• Execution Commands and Result Logs: Prints commands and results to the console when executing Docker commands.

📁 Directory Structure

./
  ├── dist/                # Build artifacts
  ├── node_modules/        # Dependencies
  ├── src/
  │   ├── config/          # Server and tool configurations
  │   ├── models/          # Type/schema definitions
  │   ├── prompts/         # MCP prompt handlers
  │   ├── resources/       # Resource handlers
  │   ├── tools/           # Docker - related MCP tools (build, run, stop, rm, rmi, etc.)
  │   ├── utils/           # Utility functions
  │   ├── http-server.ts   # HTTP server entry point
  │   └── index.ts         # MCP server entry point
  ├── tests/               # Test code
  ├── package.json         # Project metadata/scripts
  ├── tsconfig.json        # TypeScript configuration
  └── vitest.config.ts     # Test configuration

🛠️ Main Functions and Supported Tools

• docker_build: Builds a Docker image with multiple files as context.
• docker_run: Creates and runs a container with desired options.
• docker_ps: Lists running/all containers (supports the all option).
• docker_stop, docker_stop_multi: Stops container(s).
• docker_rm, docker_rm_multi: Removes container(s) (automatically stops them before removal).
• docker_images: Lists local images.
• docker_rmi, docker_rmi_multi: Removes image(s).
• docker_push: Pushes a tagged image to the registry.
• docker_login: Logs in to the Docker registry.
• docker - inspect: Retrieves detailed information about a container/image.
• docker - container - prune, docker - image - prune, docker - network - prune, docker - volume - prune: Cleans up unnecessary resources in bulk.

📦 Installation and Execution

1. Install dependencies

npm install

2. Run the development server (SSE mode)

ENABLE_UNSAFE_SSE_TRANSPORT=1 npm run dev

3. Build and deploy

npm run build
npm start

💻 Usage Examples

Basic Usage

• MCP clients can automatically recognize and execute the above tools through tool discovery.
• Each tool directly calls the Docker CLI via child_process, ensuring the same behavior as the actual Docker environment.

🧪 Testing

• Test code for each tool is included in the tests/ directory.
• Supports testing based on Vitest.

🤝 Contribution and Inquiries

• This project welcomes expansion and contributions.
• For inquiries about the MCP standard, Docker automation, or additional features, please feel free to leave an issue or PR.

In fact, operations like build, push, and run call the Docker CLI via child_process.

🐳 Practical Deployment Guide for a Fully Isolated MCP Server with DinD (Docker - in - Docker)

1. Build the latest image and push it to Docker Hub

docker build -t ekdh600/build - mcp:latest .
docker push ekdh600/build - mcp:latest

2. Commit and push the latest code to Git

cd docker - build - mcp - ts
git add .
git commit -m "docs: Update DinD structure and Kubernetes compatibility"
git push

3. Run a fully isolated container based on DinD (Kubernetes - compatible)

• Use only the internal dockerd without mounting the host Docker socket
• Works the same in a Kubernetes environment.

docker run --privileged --name build - mcp -d -p 3000:3000 ekdh600/build - mcp:latest

• The internal dockerd starts automatically, and the MCP server listens on 0.0.0.0:3000.
• MCP tools (docker_ps, docker_run, etc.) control only the Docker environment inside the container (fully isolated from the host).
• Can be registered and used as an MCP server in Cursor/Cloud/Kubernetes environments.

4. Practical usage examples of MCP tools (Cursor/Cloud)

• MCP server address: http://<HostIP>:3000
• After registering the MCP server in Cursor, use tools like docker_ps and docker_run.
• All created and listed containers exist only in the DinD internal environment.