devcontainer.json is a file most people copy from somewhere and then edit nervously. Here the description is the input and the file is the output, and the same server builds the container and tells you whether it came up.
A server that turns a plain-English description into a valid devcontainer.json, then builds, starts, stops and monitors the container through the DevContainer CLI. It also updates an existing configuration when you describe the change, and ships templates for common stacks including Node.js, Python, Go, Rust and Java.
- A devcontainer.json generated from a description such as a React TypeScript project with Tailwind CSS on the port you name
- Prebuilt templates for popular development stacks, including Node.js, Python, Go, Rust and Java
- Container lifecycle through the DevContainer CLI: build, test, start, stop and monitor
- Live modification of an existing configuration from a described change
- Real-time container health and configuration status
- The same operations available as a standalone command-line tool
- One server that works from VS Code, Cursor, Claude Desktop and other MCP clients
Node.js 18+, Docker or Podman, and the DevContainer CLI installed globally with npm install -g @devcontainers/cli. The server itself installs globally as devcontainer-mcp-server and takes the same config shape in every editor.
Run a container — pull the image and point your client at it