dockerbro

dockerbro

MCP server for managing Docker containers, images, and Compose services via natural language, with configurable tool permissions and safety annotations.

Category
Visit Server

README

DockerBro

DockerBro is a proper MCP-compliant Docker management server. Speaks JSON-RPC 2.0 over stdin/stdout and talks to your local Docker daemon.

Works with Zed, Claude, Cursor, VS Code, and any other MCP-compatible AI editor.

Runs on macOS, Linux, and Windows.

pip install dockerbro

Features

Tool What it does Safety
list_containers List all containers with status, image, ports Read-only
inspect_container Detailed container info (network, mounts, env) Read-only
start_container Start a stopped container Reversible
stop_container Stop a running container Reversible
restart_container Restart a container Reversible
remove_container Remove a container (with optional force) ⚠️ Destructive
logs_container Get recent log output Read-only
exec_container Run a command inside a running container ⚠️ Destructive
list_images List local Docker images Read-only
pull_image Pull an image from a registry Reversible
run_container Run a new container with ports, env, etc. Reversible
remove_image Remove a local image ⚠️ Destructive
docker_compose_ps List Compose services Read-only
docker_compose_up Start Compose services Reversible
docker_compose_down Stop and remove Compose services ⚠️ Destructive
docker_compose_logs Get Compose service logs Read-only

Pre-approving tools

Each tool is annotated with MCP spec annotations (readOnlyHint, destructiveHint, idempotentHint) so spec-aware clients (Claude Code, Cursor, etc.) can auto-approve read-only tools without prompting.

You can also restrict tools at the server level via environment variables, enforced before anything reaches the client:

Env var Effect
DOCKER_MCP_ALLOW_TOOLS Comma-separated allowlist — only these tools are exposed and callable
DOCKER_MCP_DENY_TOOLS Comma-separated denylist — always blocked (deny wins over allow)

Example: only safe read-only tools

Pass the env var in your Zed config (add to the env object):

"env": {
  "DOCKER_MCP_ALLOW_TOOLS": "list_containers,inspect_container,logs_container,list_images,docker_compose_ps,docker_compose_logs"
}

If a tool is not pre-approved, the server returns an error:

Tool 'remove_container' is not pre-approved (blocked by server allow/deny config).

Note: Client-side approval (e.g. Zed's agent.tool_permissions) and server-side pre-approval are independent. The server-side list controls which tools are visible and callable at all; the client controls which of those require a confirmation prompt.


Requirements

  • Python 3.9+
  • Docker installed and running

Install

Option A: From PyPI (recommended — all platforms)

Platform Command
macOS / Linux pip3 install dockerbro
Windows pip install dockerbro
Any (if pip isn't on PATH) python3 -m pip install dockerbro

command not found: pip? On macOS and many Linux distros, Python 3 installs it as pip3. On Windows it's usually pip or py -m pip. When in doubt, python3 -m pip install dockerbro works everywhere.

This puts a dockerbro command on your PATH, so your editor config needs no file paths at all.

Verify it works:

dockerbro --version 2>/dev/null; echo '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"test","version":"1.0"}}}' | dockerbro

Option B: Run from source

git clone https://github.com/ramanailearning-cpu/dockerbro.git
cd dockerbro
pip install -e .

Option C: Run in a Docker container

Build it:

docker build -t dockerbro .

Run it — the socket mount differs per platform:

macOS / Linux:

docker run --rm -i -v /var/run/docker.sock:/var/run/docker.sock dockerbro

Windows (PowerShell):

docker run --rm -i -v //./pipe/docker_engine://./pipe/docker_engine dockerbro

Connecting to the Docker daemon

DockerBro auto-detects your daemon, so this usually needs zero configuration:

Platform Default endpoint
Linux /var/run/docker.sock
macOS (Docker Desktop) /var/run/docker.sock, or ~/.docker/run/docker.sock on 4.13+
Windows Named pipe //./pipe/docker_engine

To point at a different or remote daemon, set DOCKER_HOST in your config's env block:

"env": { "DOCKER_HOST": "tcp://192.168.1.50:2375" }

macOS Docker Desktop note: if you get a connection error, enable Settings → Advanced → Allow the default Docker socket, or set DOCKER_HOST to unix:///Users/YOUR_NAME/.docker/run/docker.sock.


Zed Configuration

Add this to your Zed settings file (Cmd-Shift-P → Open Settings on macOS, Ctrl-Shift-P on Linux/Windows):

"context_servers": {
  "dockerbro": {
    "command": "dockerbro",
    "env": {
      "DOCKER_MCP_LOG": "/tmp/dockerbro.log"
    }
  }
}

Restricting tools server-side

Optionally, add env vars to limit which tools are exposed:

"env": {
  "DOCKER_MCP_LOG": "/tmp/dockerbro.log",
  "DOCKER_MCP_DENY_TOOLS": "remove_container,remove_image,exec_container,docker_compose_down"
}

Reload Zed (Cmd-Shift-P on macOS / Ctrl-Shift-P on Linux or Windows → Reload Window). The agent will have 16 Docker tools available.

Windows note: If the dockerbro command isn't found by Zed, use the full path shown by where dockerbro in your terminal.


Claude Desktop Configuration

macOS

Edit ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "dockerbro": {
      "command": "dockerbro",
      "env": {
        "DOCKER_MCP_LOG": "/tmp/dockerbro.log"
      }
    }
  }
}

Linux

Edit ~/.config/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "dockerbro": {
      "command": "dockerbro",
      "env": {
        "DOCKER_MCP_LOG": "/tmp/dockerbro.log"
      }
    }
  }
}

Windows

Edit %APPDATA%\Claude\claude_desktop_config.json (paste the path into Explorer's address bar):

{
  "mcpServers": {
    "dockerbro": {
      "command": "dockerbro",
      "env": {
        "DOCKER_MCP_LOG": "C:\\Users\\YOU\\dockerbro.log"
      }
    }
  }
}

Testing

Via terminal (pipe JSON-RPC)

# Initialize
echo '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"test","version":"1.0"}}}' | dockerbro

# List tools
echo '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}' | dockerbro

# Call a tool
echo '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"list_containers","arguments":{"all":true}}}' | dockerbro

Via MCP Inspector

npx @modelcontextprotocol/inspector dockerbro

Architecture

AI Editor (Zed / Claude / Cursor / VS Code)
    |  (stdin/stdout: JSON-RPC 2.0)
    v
dockerbro  (Python)
    |  (Docker SDK)
    v
Docker Daemon

License

MIT

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured