devcontainer_exec
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.
Bring a workspace folder's devcontainer up, run the postCreateCommand and postStartCommand it defines, and execute commands inside the container without leaving the client.
LABSCO SUMMARY
devcontainer_up comes first and exists to guarantee the container is running before anything executes inside it; devcontainer_run_user_commands then plays the setup scripts the configuration defines; devcontainer_exec covers everything after that. Because workspaceFolder is a per-call argument rather than server configuration, one client can drive several checkouts at once. Output redirection is built into each tool through outputFilePath, which is what keeps a long build from arriving as one enormous message.
A three-tool wrapper over the devcontainer lifecycle for a workspace folder on disk.
A workspace folder on disk with a devcontainer configuration, named per call as workspaceFolder.
One command — npx -y @crunchloop/mcp-devcontainers
USE CASES
Bring the devcontainer up for the workspace folder, then run the setup scripts the configuration defines rather than reconstructing them by hand.
Execute the build, test or script inside the container that the project defines, with output written to a file when it is long.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
devcontainer_execExecute an arbitrary shell command inside the devcontainer for the specified workspace folder.Use this to run custom commands or scripts within the devcontainer context.
devcontainer_run_user_commandsRun 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_upStart or initialize a devcontainer environment in the specified workspace folder.Use this to ensure the devcontainer is running and ready for development tasks.
BEFORE YOU INSTALL
3 tools when we connected.
npx on PATH
CONTEXT COST
Rated by the size of the 3 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Add the block to your client, or run the command directly.
{
"mcpServers": {
"mcp-devcontainers": {
"command": "npx",
"args": [
"-y",
"@crunchloop/mcp-devcontainers"
]
}
}
}npx -y @crunchloop/mcp-devcontainers