Oriel runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 28 Jun 2026.
Safety-gated AI control of Docker and Colima: containers, images, volumes, networks, Compose.
What the code does
We read the source, 4 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
_, err := os.Stat("/.dockerenv")
cache := userdata.Path(filepath.Join("i18n", name))
Name: "docker.env", Title: "Docker connection env", Description: "DOCKER_HOST + Testcontainers socket override for this machine's docker socket, fixes tools that default to /var/run/docker.sock and miss colima",
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to Oriel
same job, measured the same wayMCP server for managing Docker containers, images, networks, volumes, and registries
MCP server for Docker — manage containers, images, volumes, and compose services from your IDE
Security audit for docker-compose.yml — 25 checks: secrets, privileges, network, volumes, images.
Run core Docker container operations: list, run, inspect, logs, images and volumes.
Manage Docker (containers, images, Compose, Swarm, registries) via the Docker SDK and CLI.
Docker for AI agents — containers, compose stacks, logs and databases, locally or over SSH.
MCP server for Docker — containers, health checks, Compose, logs, monitoring for AI agents
MCP server for Komodo - manage Docker containers, servers, stacks, and deployments via AI
Oriel — questions
Answers built from our own checks of this server.