devcontainer-mcp server
io.github.aniongithub/devcontainer-mcp·v0.40·28 starsManage dev container environments via MCP (Docker, DevPod, Codespaces).
28 stars
Reviews
Write oneNobody has reviewed devcontainer-mcp yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
devcontainer-mcp tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-15 · same rubric, same numbers if you re-run it
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 38 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How devcontainer-mcp compares
Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 80/100
- higher than 55% of 1,119 Developer tools servers
- GitHub stars
- 28
- more than 89% of 855 Developer tools servers
Install devcontainer-mcp in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
What the publisher says
From the devcontainer-mcp repository's README, as published. We do not edit it. Read it on GitHub
devcontainer-mcp
Give your AI agent its own dev environment — not yours.
devcontainer-mcp is an MCP server that lets AI coding agents create, manage, and work inside dev containers across three backends: local Docker, DevPod, and GitHub Codespaces. The agent builds, tests, and ships code in an isolated container — your laptop stays clean.
Works with GitHub Copilot, Claude, Cursor, opencode, and any MCP-compatible client.
The Problem
When AI agents write code, they need to run it somewhere. Today that means your host machine:
- 🔴 Host contamination — agents install packages, modify PATH, leave behind build artifacts
- 🔴 "Works on my machine" — agents assume your local toolchain matches production
- 🔴 No isolation — one project's dependencies break another
- 🔴 Security risk — agents run arbitrary commands with your user privileges
- 🔴 Hardware constraints — you're limited to your local machine's resources
The Solution
The devcontainer spec already defines reproducible, container-based dev environments. Every major project ships a .devcontainer/devcontainer.json. But AI agents can't use them — until now.
devcontainer-mcp exposes 45 MCP tools that let any AI agent:
- Spin up a dev container from any repo — locally, on a cloud VM, or in Codespaces
- Run commands inside the container — builds, tests, linting, anything
- Manage the lifecycle — stop, restart, delete when done
- Authenticate against cloud providers — GitHub, AWS, Azure, GCP — without ever seeing a raw token
Agent: "Let me build this project..."
→ auth_status("github") → picks account
→ codespaces_create(auth: "github-you", repo: "your/repo")
→ codespaces_ssh(auth: "github-you", codespace: "...", command: "cargo build")
→ ✅ Built in the cloud. Your laptop did nothing.Quick Install
Linux / macOS
curl -fsSL https://raw.githubusercontent.com/aniongithub/devcontainer-mcp/main/install.sh | bashWindows (via WSL)
Invoke-RestMethod https://github.com/aniongithub/devcontainer-mcp/releases/latest/download/install.ps1 | Invoke-ExpressionHow it works: The binary runs inside WSL; MCP clients on Windows launch it via wsl ~/.local/bin/devcontainer-mcp serve. The stdio transport works transparently across the WSL boundary. WSL 2 is required — install it with wsl --install if you haven't already.
Backend CLIs (devpod, devcontainer, gh) are detected at runtime — if one is missing, the MCP server returns a helpful error with install instructions.
Binaries available for linux-x64, linux-arm64, darwin-x64, and darwin-arm64.
Host Protection & Opt-Out
The installer configures two agent hooks (Claude Code & GitHub Copilot CLI) that activate only in a directory containing .devcontainer/devcontainer.json:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Grade history
- 2026-10-15downgradeA → Bscore 80
devcontainer-mcp: common questions
- Is devcontainer-mcp server safe?
- Mostly: it is graded B (80/100). Read the devcontainer-mcp safety report
- Does devcontainer-mcp need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is devcontainer-mcp maintained?
- The last commit was 57 days ago (2026-09-08). The latest release is v0.40.
- What can I use instead of devcontainer-mcp?
- Servers from other publishers that do the same job: maintenant MCP server, Komodo MCP Server and Podman MCP server.
- How does devcontainer-mcp compare with other Developer tools MCP servers?
- safety score 80/100 (higher than 55% of 1,119 Developer tools servers); github stars 28 (more than 89% of 855 Developer tools servers). Full comparison.
Alternatives to devcontainer-mcp
Same job from other publishers: the closest match first, then the best rated.
- maintenantDocker monitoring for AI agents: logs, history, alerts. Can ack alerts; never touches containers.not reviewedEstablishedC
- Komodo MCP ServerMCP server for Komodo - manage Docker containers, servers, stacks, and deployments via AInot reviewedEstablishedB
- PodmanA Model Context Protocol (MCP) server for container runtimes (Podman and Docker)not reviewedGrowingA
- Docker MCP ServerManage Docker (containers, images, Compose, Swarm, registries) via the Docker SDK and CLI.not reviewedGrowingA
- HomebutlerTells an agent what changed on a server since it last looked - status, Docker, backups, Proxmox.not reviewedEstablishedC