seedpod
OfficialProvides tools to manage Docker containers running inside LXD machines, including listing containers grouped by compose project, viewing logs and inspect output, and starting, stopping, or restarting containers and compose projects.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Seedpod
Your LXC machines, and the Docker running inside them, in one tree.
Seedpod is a VS Code sidebar and an MCP server for people who run their dev environments as LXD system containers: a machine per branch, per client, per experiment, each one with its own Docker Compose stack inside.
Why Seedpod
LXD system containers are a great way to run many full dev machines on one host. They boot in seconds, clone in seconds on btrfs or ZFS, and run systemd and Docker like a VM, at a fraction of the cost. But the tooling stops at the machine boundary:
Container Tools only sees the host's Docker. The compose stacks inside your LXD machines are invisible to it, so checking on them means
lxc exec <machine> -- docker ps, again and again, one machine at a time.lxcanddockerare two separate worlds. Iswebdown because the container stopped, or because the machine around it did? You end up asking both, by hand.Agents get a shell or nothing. Giving an AI assistant raw
lxcaccess means it can delete anything. Giving it none means it can't help.
Seedpod puts both layers in one place:
One tree. Machine → compose project → container, with live status, IPs and uptime, refreshed as LXD reports changes.
One right-click. Start, stop, open a shell, read logs or snapshot at whichever level is broken, with a confirmation that names the target before anything destructive.
The same model for AI clients. The MCP server gives assistants structured tools instead of a shell. Machines you list as protected can't be changed, there's a read-only mode, and there are no delete or restore tools at all.
Related MCP server: VPS-Guardian-MCP
The extension
Containers: LXD instances grouped by project, with status, OS, IP and uptime. Expanding a running machine lists the Docker containers inside it, grouped by compose project, plus its snapshots.
Images, Networks and Storage views (collapsed by default).
Right-click actions:
Machines: start / stop / restart / freeze, open a shell, show the log, inspect, snapshot / restore / delete, copy IP, open a Remote-SSH window, delete.
Docker containers: start / stop / restart / remove, view logs, attach a shell, inspect.
Compose groups: start / restart / stop all.
Refreshes live from
lxc monitor. Docker inside expanded machines is polled.
Every destructive action asks first, in a modal that names the target.
Settings
Setting | Default | |
|
| Path to the |
|
| Seconds between Docker refreshes for expanded machines. |
|
| Also list host bridges LXD does not manage (docker0, br-*). |
|
| User "Open in Remote-SSH Window" connects as. |
|
| Folder to open, e.g. |
|
| VS Code settings written into the machine's |
For example, to open ~/workspace and see git worktrees that live one folder deeper than the repos:
"seedpod.remoteSsh.folder": "~/workspace",
"seedpod.remoteSsh.machineSettings": {
"git.repositoryScanMaxDepth": 2,
"scm.alwaysShowRepositories": true
}Notes
Only the local daemon is supported. Remote LXD servers are not.
Docker is reached through
lxc exec <machine> -- docker …, so the host needs no Docker socket access."Open in Remote-SSH" connects as
ubuntu@<ip>(seeseedpod.remoteSsh.user). Keys come from your SSH config.
Build
npm install
npm test # parser and tree tests (node --test)
npm run build # esbuild → dist/extension.js
npm run package # → seedpod-<version>.vsix
code --install-extension seedpod-<version>.vsixMCP server
The same code also ships as a stdio MCP server (dist/mcp.js, built by npm run build). It lets an AI client see and manage
the machines and the Docker containers inside them.
Tool | Writes | |
| every instance: status, OS, IPv4, uptime, snapshots, protected flag | |
| expanded config + | |
| Docker containers inside a machine, grouped by compose project | |
| bounded logs (no follow), and | |
| images, managed networks, storage pools | |
| ✔ | start / stop (100 s clean timeout, never forced) / restart / freeze / unfreeze |
| ✔ | new snapshot (validated name) |
| ✔ | start / stop / restart a container or a whole compose project |
| ✔ | run an argv inside a machine as root and return the exit code and output |
There are deliberately no delete, restore or remove tools.
Env var | |
| path to |
| register the read-only tools only |
| machines no write tool (including |
To register it with Claude Code:
claude mcp add --scope user seedpod -e SEEDPOD_PROTECT=my-template -- node /path/to/seedpod/dist/mcp.jsTool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Provides capabilities that let LLM agents perform a range of infrastructure management tasks.
Linux VMs for AI agents: create VMs, run commands, edit files and open preview URLs.
Operate Linux, macOS and Windows from your LLM. Every action runs through an auditable allowlist.
Secure Linux sandboxes for AI agents, as MCP tools.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceProvides Docker management tools for AI agents, including inspecting containers, images, Dockerfiles, and Compose configurations.62 npm1MIT
- AlicenseAqualityBmaintenanceEnables AI agents to safely monitor Linux VPS health, inspect Docker containers, retrieve service logs, and execute whitelisted recovery actions via MCP.31158 npm93 PyPIMIT
- AlicenseAqualityCmaintenanceEnables AI agents to manage Proxmox VE clusters, LXC containers, snapshots, services, and Tailscale mesh status.71MIT
- AlicenseBqualityBmaintenanceNido is a local QEMU VM manager. Install it on your computer from https://github.com/Josepavese/nido and run nido mcp via stdio, or use npx -y nido-mcp@latest mcp with QEMU installed locally. It manages VMs on that same computer; a server hosted by Glama cannot access your local VM inventory.62MIT