Allows executing commands in ephemeral containers with any combination of Nix packages from the NixOS/nixpkgs repository.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@zeughaus-mcp run python3 and curl to fetch https://example.com"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Server - Agentic Workbench backed by Nixery.
Execute commands in ephemeral containers with any combination of Nix packages.
Docker is the recommended installation method because it provides workspace isolation - the MCP server itself runs in a container with access only to your specified workspace directory.
docker run --rm -i \
-v /var/run/docker.sock:/var/run/docker.sock \
-v /path/to/workspace:/workspace \
-e NIXERY_REGISTRY_URL=nixery.zeughaus.dev \
-e HOST_WORKSPACE_ROOT=/path/to/workspace \
ghcr.io/gtarkin/zeughaus_mcp:latestNote: When running via uvx, the MCP server has full access to the host system. Use Docker for better isolation.
uvx zeughaus-mcpRelated MCP server: mcp-omnienv-nix
Environment variables:
Variable | Required | Default | Description |
| Yes | - | Nixery registry URL (see below) |
| Yes | - | Workspace path to mount into containers |
| No |
| Docker network mode |
| No |
| Container execution timeout |
Nixery is a Docker-compatible registry that builds container images on-the-fly from Nix packages.
Registry | Channel | Description |
| nixos-25.11 | Self-hosted instance for zeughaus-mcp (recommended) |
| nixos-unstable | Public Nixery instance by Google |
The default registry for zeughaus-mcp. This is a self-hosted Nixery instance with:
Nix Channel: nixos-25.11 (stable packages)
Source: github.com/NixOS/nixpkgs
Build timeout: 600 seconds
The public Nixery instance maintained by Google. Use this if you prefer:
Nix Channel: nixos-unstable (latest packages)
No dependency on third-party infrastructure
To use the public registry, set:
NIXERY_REGISTRY_URL=nixery.dev{
"mcpServers": {
"zeughaus": {
"command": "docker",
"args": [
"run", "--rm", "-i",
"-v", "/var/run/docker.sock:/var/run/docker.sock",
"-v", "/path/to/workspace:/workspace",
"-e", "NIXERY_REGISTRY_URL=nixery.zeughaus.dev",
"-e", "HOST_WORKSPACE_ROOT=/path/to/workspace",
"ghcr.io/gtarkin/zeughaus_mcp:latest"
]
}
}
}{
"mcpServers": {
"zeughaus": {
"command": "uvx",
"args": ["zeughaus-mcp"],
"env": {
"NIXERY_REGISTRY_URL": "nixery.zeughaus.dev",
"HOST_WORKSPACE_ROOT": "/path/to/workspace"
}
}
}
}MIT
This server cannot be deployed
Manage Sprites: sandboxed compute environments with exec, services, and checkpoints.
Run Python code in a secure sandbox without local setup. Declare inline dependencies and execute s…
Hosted Python sandbox for package runtime verification: pip install and usable-import evidence.
Execute code in 8 languages (Python, JS, TS, Go, Java, C++, C, Bash) in gVisor sandboxes.
