Container Use
UntestedContainerized environments for coding agents. Multiple agents can work independently, isolated in fresh containers and git branches. No conflicts, many experiments. Full execution history, terminal access to agent environments, git workflow. Any agent/model/infra stack.
Install
No auto-install command available for this server.
Check the GitHub repository for setup instructionsSafety Report
details
Runs locally via stdio; no network auth required. Agents access containerized environments only.
details
stdio transport only; no HTTP server exposed.
details
Local process; no rate limiting applicable.
details
Experimental project; no known CVEs at time of review.
details
Go project with go.mod/go.sum lockfile. No public audit report available.
details
No dangerous code patterns detected
details
Apache 2.0 license confirmed in repository.
details
Fully open source on GitHub (dagger/container-use). Apache 2.0.
details
Actively maintained by Dagger team. Marked experimental but under active development.
Compatibility
Tools Provided (13)
environment_create Creates a new isolated development environment with setup commands on top of a base container image.
environment_open Opens an existing environment. Return format is same as environment_create.
environment_list List available environments.
environment_update_metadata Updates descriptive information like title about work being done in an environment.
environment_config Makes environment configuration changes such as base image, setup commands, and environment variables.
environment_run_cmd Executes a terminal command inside a new container within the environment.
environment_file_read Reads file contents from the environment, allowing specification of line ranges or entire files.
environment_file_list List the contents of a directory in the environment.
environment_file_write Writes complete file contents to a specified path in the environment.
environment_file_edit Performs find-and-replace text operations within files in the environment.
environment_file_delete Deletes a file at the specified path in the environment.
environment_add_service Adds services like databases or caches to the environment.
environment_checkpoint Checkpoints an environment in its current state as a container image.
Frequently Asked Questions
What is Container Use?
Containerized environments for coding agents. Multiple agents can work independently, isolated in fresh containers and git branches. No conflicts, many experiments. Full execution history, terminal access to agent environments, git workflow. Any agent/model/infra stack.
What tools does Container Use provide?
Container Use provides 13 tools including environment_create, environment_open, environment_list, environment_update_metadata. Each tool can be called by AI agents to perform specific operations.
Is Container Use safe to use?
Container Use has not yet been security scanned. We recommend reviewing the source code and safety report before use.
What are alternatives to Container Use?
Similar MCP servers include Serena, MCP Run Python, DesktopCommanderMCP. Each serves a similar purpose but may differ in features, language, and compatibility.
Similar MCP Servers
Serena
CautionA fully-featured coding agent that relies on symbolic code operations by using language servers.
MCP Run Python
CautionRun Python code in a secure sandbox via MCP tool calls
DesktopCommanderMCP
CautionA swiss-army-knife that can manage/execute programs and read/write/search/edit code and text files.