devcontainer-mcp

Manage dev container environments across Docker, DevPod, and GitHub Codespaces via MCP tools.

26|3|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/aniongithub/devcontainer-mcp --skill devcontainer-mcp-aniongithub
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: devcontainer-mcp
Source: https://github.com/aniongithub/devcontainer-mcp
Command: npx skills add https://github.com/aniongithub/devcontainer-mcp --skill devcontainer-mcp-aniongithub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding agents typically run builds, tests, and installs directly on your host machine, contaminating your environment, breaking isolation between projects, and creating security risks. This Skill routes all agent work into isolated dev containers defined by the standard devcontainer spec, keeping your host clean. ## Core Features & Use Cases - Three backends, one interface: Create, manage, and execute commands in dev containers via local Docker (devcontainer CLI), DevPod (multi-cloud: Docker, K8s, AWS, Azure, GCP), or GitHub Codespaces. - Token-safe authentication: An auth broker issues opaque handles for GitHub, AWS, Azure, GCP, and Kubernetes so the agent never sees raw credentials. - Built-in file operations: Read, write, edit, and list files inside any container without constructing shell commands, plus self-healing workflows that let the agent fix a failing Dockerfile or devcontainer.json and retry. - Use Case: Ask your agent to build a Rust project — it spins up a Codespace with your GitHub account, runs cargo build inside it, and stops the environment when done, all without touching your laptop. ## Quick Start Ask your AI agent to start a dev container for the current project and run the test suite inside it using the devcontainer-mcp tools.

Frequently Asked Questions about devcontainer-mcp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run builds inside a dev container with an AI agent?▼

Use the devcontainer_up tool with your workspace folder to start the container, then devcontainer_exec to run commands like npm test or cargo build inside it. The agent never installs or runs anything on the host.

What is the difference between the DevPod, devcontainer CLI, and Codespaces backends?▼

The devcontainer CLI backend runs local Docker containers with no auth needed. DevPod supports multi-cloud providers including Docker, Kubernetes, AWS, Azure, and GCP. Codespaces provides GitHub-hosted cloud environments and requires a GitHub auth handle.

Does devcontainer-mcp work with Claude Code and GitHub Copilot?▼

Yes, it works with any MCP-compatible client including Claude Code, GitHub Copilot CLI, Cursor, VS Code, and opencode. The installer auto-configures MCP server entries and host-protection hooks for supported clients.

How does authentication work for GitHub Codespaces tools?▼

Call auth_status to list accounts, then auth_login if needed to trigger a browser-based device code flow. The tools receive an opaque handle like github-username, and the MCP server resolves the real token via the CLI keyring, so the agent never sees it.

Can I disable the host-protection guard for a specific repo?▼

Yes, create a .devcontainer-mcp-disable marker file at the repo root to opt out. For a single command, include USER_CONFIRMED_HOST_OPERATION=1 in the command to bypass the guard once.

What happens when devcontainer_up or codespaces_create fails?▼

The full build output including errors is returned to the agent. The agent reads the error, fixes the Dockerfile or devcontainer.json, and retries, making the dev environment a self-healing, agent-managed asset.