generate_devcontainerLABSCO SUMMARY
The container config written by describing it.
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.
What it is
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.
What you get
- 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
Requirements
Node.js 18+, Docker or Podman, and the DevContainer CLI installed globally with npm install -g @devcontainers/cli. The server is not on npm despite the README's npm install -g line: clone and build it, then point your client at the built dist/index.js.
Setup effort
Build from source — git clone https://github.com/Siddhant-K-code/mcp-devcontainer.git
USE CASES
01
Getting a project containerised without learning the schema
Describe the stack, the ports and the tooling you want, and a valid devcontainer.json comes back rather than a template you then have to adapt.
02
Changing a container you already have
Say what should be different and the existing configuration is updated in place, so adding a service or a port does not mean rewriting the file by hand.
03
Finding out whether the container actually came up
Build and start run through the DevContainer CLI, and container health and configuration status come back as a status read instead of raw Docker output.
04
Starting from a known-good stack
The bundled templates cover Node.js, Python, Go, Rust, Java and more, so a conventional project begins from a working baseline instead of a blank file.
6 tools
Listed in project docs. Your client may show a different list.
build_devcontainertest_devcontainerlist_templatesmodify_devcontainerget_devcontainer_statusBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Requires
- Node.js 18+
- Docker or Podman
- DevContainer CLI (npm install -g @devcontainers/cli)
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/Siddhant-K-code/mcp-devcontainer.git
cd mcp-devcontainer
npm install
npm run buildMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"devcontainer": {
"command": "node",
"args": [
"<YOUR_PATH_TO_MCP_DEVCONTAINER>/dist/index.js"
]
}
}
}<YOUR_PATH_TO_MCP_DEVCONTAINER> is the full path of the folder the git clone created. Docker (or Podman) and the DevContainer CLI (npm install -g @devcontainers/cli) must be installed.
VS Code
VS CODE · JSON
{
"servers": {
"devcontainer": {
"type": "stdio",
"command": "node",
"args": [
"<YOUR_PATH_TO_MCP_DEVCONTAINER>/dist/index.js"
]
}
}
}<YOUR_PATH_TO_MCP_DEVCONTAINER> is the full path of the folder the git clone created. Docker (or Podman) and the DevContainer CLI (npm install -g @devcontainers/cli) must be installed.
