Build FAQs

Question 1

What is Build and what is its primary purpose?

Accepted Answer

Build is an MCP-compliant server designed to automate comprehensive Docker image and container management. It provides API access to common Docker CLI commands, streamlining DevOps workflows for developers.

Question 2

How does Build integrate with existing Docker environments?

Accepted Answer

Build integrates by directly calling Docker CLI commands via `child_process`, acting as an intelligent API layer over your Docker daemon. It supports both host-mounted Docker sockets and isolated Docker-in-Docker (DinD) environments.

Question 3

What is MCP (Model Context Protocol) and why is it important for Build?

Accepted Answer

MCP (Model Context Protocol) is a standard for tool discovery and execution, especially for AI clients. Build's full MCP compliance enables seamless integration with tools like Cursor and Claude, allowing them to automatically discover and execute Docker operations.

Question 4

Does Build support isolated Docker environments like Docker-in-Docker (DinD)?

Accepted Answer

Yes, Build fully supports Docker-in-Docker (DinD). This enables completely isolated and portable Docker environments, making it ideal for containerized deployments like Kubernetes where host Docker access isn't preferred or available.

Question 5

What specific Docker operations can Build automate?

Accepted Answer

Build automates a wide array of Docker operations, including `docker_build`, `docker_run`, `docker_stop`, `docker_rm`, `docker_ps`, `docker_images`, `docker_rmi`, `docker_push`, `docker_login`, `docker-inspect`, and various resource pruning commands like `docker-container-prune`.

Build

Build

Key Features

Use Cases

Key Features

Use Cases