devcontainer-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEVCONTAINER_CLI | No | CLI invocation; shell-split, so npx @devcontainers/cli works. | devcontainer |
| DEVCONTAINER_WORKSPACE_FOLDER | No | Default host workspace folder when the workspaceFolder arg is omitted. | current dir |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bashA | Run a shell command inside the project's devcontainer and return its combined stdout/stderr and exit status. Mirrors Claude Code's built-in Bash tool, but every command executes inside the devcontainer (via The command string is interpreted by bash inside the container, so pipes, &&, ||, globs, redirects, env expansion and quoting all behave as in a normal shell. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no ambiguity between tools. The single 'bash' tool is clearly defined for running commands inside a devcontainer.
With only one tool named 'bash', naming is trivially consistent. The name is simple and lowercase, which is fine for a single tool.
The server has only one tool, which feels thin for a server named 'devcontainer-mcp'. Most devcontainer workflows involve more than just running commands, so the count is borderline low.
The server covers only shell execution inside a devcontainer. While this is core functionality, it lacks tools for container lifecycle management (start, stop, config), leaving notable gaps for typical devcontainer use.