Skip to main content
Glama
Krelborn

docker-compose-mcp

by Krelborn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
docker_compose_updateA

Update Docker Compose containers by stopping them, pulling latest images, and restarting.

This tool executes the standard update workflow:

  1. Stop running containers (docker compose down)

  2. Pull latest images (docker compose pull)

  3. Start containers with new images (docker compose up -d)

Args:

  • compose_file (string): Absolute path to the docker-compose.yml file

  • detached (boolean): Run containers in detached mode (default: true)

Returns: A summary of each step's output, including:

  • Which containers were stopped

  • Which images were pulled/updated

  • Which containers are now running

  • Any errors encountered during the process

Examples:

  • Use when: "Update my chemdraw containers"

  • Use when: "Pull latest images and restart docker compose"

Error Handling:

  • If 'down' fails, continues to 'pull' (containers may not be running)

  • If 'pull' fails, does not proceed to 'up'

  • If 'up' fails, reports error details

docker_compose_commandA

Execute any docker compose command for a specific compose file.

This tool allows running arbitrary docker compose commands like:

  • ps: List containers

  • logs: View container logs

  • restart: Restart services

  • stop/start: Stop or start services

  • exec: Execute commands in running containers

Args:

  • compose_file (string): Absolute path to the docker-compose.yml file

  • command (string): Docker compose command to run (everything after 'docker compose -f file.yml')

Returns: The stdout and stderr output from the docker compose command

Examples:

  • Use when: "Show me the logs for my docker containers"

  • Use when: "List running docker compose services"

  • Use when: "Restart the web service"

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.1/5.0

Scored across 2 tools

Disambiguation4/5

docker_compose_update is a specialized workflow while docker_compose_command is a general executor. They overlap because the update workflow can also be run via the generic command, but the distinction is clear enough for an agent to choose correctly.

Naming Consistency4/5

Both tools use snake_case with a consistent docker_compose_ prefix. The only minor inconsistency is that 'update' is a verb while 'command' is a noun, but the pattern is still predictable and readable.

Tool Count3/5

Two tools is borderline thin for a server. While the generic command covers many operations, the specialized update tool means each tool earns its place, but more structured tools for common operations could improve usability.

Completeness5/5

The generic docker_compose_command can execute any docker compose command, covering the full lifecycle (up, down, logs, ps, exec, etc.). The update tool handles a common workflow, so there are no obvious gaps.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources