MCP Devcontainers
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| devcontainer_upC | Start or initialize a devcontainer environment in the specified workspace folder.Use this to ensure the devcontainer is running and ready for development tasks. |
| devcontainer_run_user_commandsB | Run the user-defined postCreateCommand and postStartCommand scripts in the devcontainerfor the specified workspace folder. Use this to execute setup or initialization commandsafter the devcontainer starts. |
| devcontainer_execC | Execute an arbitrary shell command inside the devcontainer for the specified workspace folder.Use this to run custom commands or scripts within the devcontainer context. |
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 3 tools
Each tool has a clearly distinct purpose: starting the devcontainer, executing arbitrary commands, and running user-defined lifecycle scripts. No overlapping functionality.
All tools follow the 'devcontainer_verb' pattern in snake_case (exec, run_user_commands, up). Naming is consistent and predictable.
With 3 tools, the server is lean but covers core devcontainer operations. Could be slightly more comprehensive but appropriate for a focused utility.
The tool set covers starting, executing commands, and running lifecycle scripts, but misses common operations like stopping, rebuilding, or checking status, which are notable gaps.