Code Execution MCP Server

Container Use

Name: Container Use
Author: dagger

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.

Not scanned by dagger3,618Apache-2.0GoIntermediatestdio

Safety Report

100% Not scanned

Scanned 5 months ago

4 passed

Security

Authentication

details

Runs locally via stdio; no network auth required. Agents access containerized environments only.

N/A

CORS Policy

details

stdio transport only; no HTTP server exposed.

N/A

Rate Limiting

details

Local process; no rate limiting applicable.

N/A

Known CVEs

details

Experimental project; no known CVEs at time of review.

Info

Code Quality

Dependency Audit

details

Go project with go.mod/go.sum lockfile. No public audit report available.

Info

Dangerous Patterns

details

No dangerous code patterns detected

Pass

License

details

Apache 2.0 license confirmed in repository.

Pass

Code Source

details

Fully open source on GitHub (dagger/container-use). Apache 2.0.

Pass

Community

Maintenance Status

details

Actively maintained by Dagger team. Marked experimental but under active development.

Pass

Compatibility

Claude CodePrimary target. Install via `brew install dagger/tap/container-use` then `container-use stdio` as MCP server command.

Not Tested

CursorSupports any MCP-compatible agent. Configure with `cu` or `container-use stdio`.

Not Tested

VS CodeCompatible with MCP-enabled VS Code extensions.

Not Tested

WindsurfShould work with any MCP-compatible client.

Not Tested

Claude DesktopConfigurable as stdio MCP server in claude_desktop_config.json.

Not Tested

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?

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?

We do not know. Container Use was never cloned or checked — 489 of the 2,805 servers listed here were not. Read the source before running it.

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.

Stay Updated on MCP Servers

New servers, safety alerts, and install guides — weekly.

Container Use

Install

Safety Report

Compatibility

Tools Provided (13)

Frequently Asked Questions

Similar MCP Servers

Serena

MCP Run Python

DesktopCommanderMCP

Free AI writing tools

Stay Updated on MCP Servers