MCP server for Contree container management system
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"contree-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# ConTree MCP Server [](https://pypi.org/project/contree-mcp/) [](https://github.com/nebius/contree-mcp/actions/workflows/tests.yml) [](LICENSE) Run code in isolated cloud containers. ConTree gives AI agents secure sandboxed execution environments with full root access, network, and persistent images. ## Why ConTree? **Fearless experimentation.** Agents can: - Run destructive commands (`rm -rf /`, `dd`, kernel exploits) - nothing escapes the sandbox - Make mistakes freely - revert to any previous image UUID at zero cost - Execute potentially dangerous user requests - ConTree IS the safe runtime for risky operations - Break things on purpose - corrupt filesystems, crash kernels, test failure modes Every container is isolated. Every image is immutable. Branching is cheap. Mistakes are free. ## Quick Setup ### 1. Get an API Token Contree is in **Early Access**. To get an API token, fill out the request form at [contree.dev](https://contree.dev). ### 2. Create Config File `contree-mcp` reads the same `auth.ini` that [`contree-cli`](https://docs.contree.dev/cli/tutorial/installation.html) writes, so a single login covers all contree-related tools. **Recommended:** install `contree-cli` (see [installation guide](https://docs.contree.dev/cli/tutorial/installation.html)) and manage credentials with it rather than editing the file by hand: ```bash contree auth --help # add, switch, list, remove profiles ``` Default location: `$XDG_CONFIG_HOME/contree/auth.ini` (typically `~/.config/contree/auth.ini`). Override the directory with `CONTREE_HOME`. If you really need to write it by hand: ```ini [DEFAULT] profile = default [profile:default] type = iam url = https://api.tokenfactory.nebius.com/sandboxes token = <TOKEN HERE> project = <NEBIUS PROJECT ID> ``` …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.