# Could This Be the Easiest Way to Run MCP Servers in Your Home Lab?

Brandon Lee (Virtualization Howto) walkthrough: use **Docker MCP Toolkit** in Docker Desktop to catalog, profile, and attach MCP servers to Cursor instead of running a pile of Node/Python/container processes. Official name: Docker MCP Catalog and Toolkit; gateway code lives in `docker/mcp-gateway`.

Tags: source, docker, mcp, homelab, docker-desktop, cursor, brandon-lee, virtualization-howto

## Who / what

| Field | Value |
|---|---|
| Author | Brandon Lee — owner / senior writer, Virtualizationhowto.com; 7-time VMware vExpert |
| Form | Blog walkthrough + screenshots |
| Title | Could This Be the Easiest Way to Run MCP Servers in Your Home Lab? |
| Published | 2026-08-15T11:31:34Z (7:31 AM ET). Page `<time>` 2026-08-15T06:31:34-05:00 |
| URL | https://www.virtualizationhowto.com/2026/08/could-this-be-the-easiest-way-to-run-mcp-servers-in-your-home-lab/ |
| Product recommended | **Docker MCP Toolkit** (Desktop UI) + Docker MCP Catalog + MCP Gateway |
| Official docs | https://docs.docker.com/ai/mcp-catalog-and-toolkit/ |
| Code | https://github.com/docker/mcp-gateway (Go, MIT; 1530★ / 261 forks as of 2026-08-15) |

Primary body: WebFetch of the public page → raw/`mcp-homelab-docker-mcp-toolkit-2026-08-15/article.md`.

## Summary

Lee's problem is not "how do I start one MCP server" — it is what happens after you have many: mixed Node/Python/container/remote runtimes, per-client config, tokens, and no inventory. Docker MCP Toolkit (a **beta** Docker Desktop feature) is his proposed organizer. You enable it, create a **profile** (servers + client), fill leftover auth fields, and the **MCP Gateway** presents the whole profile to the IDE as one `MCP_DOCKER` server. Catalog search replaces hunting GitHub READMEs. He still had to type Proxmox credentials by hand; Toolkit did not invent those tokens. He also shows **Push profile** to a registry and a `docker mcp` CLI.

Official docs (same-day fetch) match the three-part model (catalog / profile / client) and the `MCP_DOCKER` client name. They add: 300+ verified catalog images, OAuth for some SaaS servers, container isolation defaults, and a standalone CLI/image path that the article does not cover.

## Key points (article)

- **Why MCP at all:** abstraction over raw APIs. A specialized MCP (e.g. AWS) exposes current tools so the model is not stuck on its knowledge cutoff.
- **Home-lab mess:** one local process becomes many; each server has its own install and client JSON. Organization, not first install, is the bottleneck.
- **Flip the workflow:** build a profile, then attach the IDE — do not keep bolting servers onto the client.
- **Three Toolkit pieces:** Profiles (named server collections), Catalog (search/install), Clients (Cursor, etc.). Gateway exposes the profile as one logical MCP.
- **Enable:** latest Docker Desktop → Settings → Beta Features → Enable Docker MCP Toolkit. Left-nav item labeled BETA.
- **Auth caveat (author):** Proxmox VE showed **Configuration Required**. "This is still a piece the Toolkit doesn't do for you."
- **Cursor:** auto-connect created `MCP_DOCKER`. A separate manual Proxmox MCP entry coexisted.
- **Share:** Push profile to a registry (UI; not documented in the article beyond screenshots).
- **CLI shown:** `docker mcp --help`; `docker mcp catalog server ls mcp/docker-mcp-catalog`; `docker mcp profile server ls` (not re-run this ingest).

## Official product (do not flatten into the article)

Canonical product: **Docker MCP Catalog and Toolkit**.

```
Catalog (300+ verified mcp/ images)  -->  Profile (named toolbox)
                                              |
                                       MCP Gateway (proxy)
                                              |
                         Clients: Cursor / Claude / VS Code / Zed / …
                         typical config name: MCP_DOCKER
                         command: docker mcp gateway run --profile <name>
```

| Claim | Source | Note |
|---|---|---|
| Enable via Beta features | Article + get-started docs | Agree |
| Desktop UI described for **4.62+** | Toolkit / get-started docs | Earlier Desktop has a different UI |
| Toolkit auto-launch needs Desktop **4.48+** | docker.com product page | Not a contradiction of 4.62 UI note |
| Catalog size **300+** | Docs hub | Article does not quote a count |
| OAuth auto for GitHub / Notion / Linear | Toolkit docs | Complements author's Proxmox-token caveat |
| Isolation: 1 CPU, 2 GB, no host FS by default, signed `mcp/` images + SBOM | Toolkit docs | Not in article |
| Dynamic MCP (agent adds catalog servers mid-chat) | Toolkit docs | Not in article |
| AI Governance Gateway = invite-only | Gateway docs | **Not** the OSS Desktop/CLI gateway |
| Latest GitHub tag **v0.43.3** (prerelease, 2026-07-16) | GitHub API | `/releases/latest` 404; Desktop ships its own plugin |

Standalone / no-Desktop path (docs, not article): download `docker-mcp` to `~/.docker/cli-plugins/`, or run image `docker/mcp-gateway`.

## Caveats

- Author conclusion ("easiest") is after manual sprawl; not a bake-off vs `uvx`, Compose, or Hermes plugins.
- Author CLI subcommands may have drifted; official examples use `gateway run` / `client connect`.
- Toolkit is Desktop-centric. Headless Engine users need the plugin/image path.
- Self-hosted infra MCP still needs secrets. OAuth only covers some catalog SaaS.
- Related July 2026 listicle ("My Favorite MCP Servers for the Home Lab in 2026") is **not** ingested.

## Fit for Josh

Useful if Cursor MCP config is getting messy and the servers are in Docker's catalog. `MCP_DOCKER` is the documented one-line attach. Does not replace [[perseus-vault]] (memory), [[hermes-agent]] (runtime), or [[grok-bot]] (managed computer). Home-lab Proxmox-style servers still need tokens in the Toolkit UI.

## Related

- [[perseus-vault]]
- [[hermes-agent]]
- [[hermes-plugin-perseus-vault]]
- [[ia-local-casa]]
- [[grok-bot]]
- [[youtube-agentos-claude-sdk]]
- raw/`mcp-homelab-docker-mcp-toolkit-2026-08-15/`

## Sources

1. **Primary:** Brandon Lee, Virtualization Howto, 2026-08-15 — raw/`mcp-homelab-docker-mcp-toolkit-2026-08-15/article.md`
2. https://docs.docker.com/ai/mcp-catalog-and-toolkit/
3. https://docs.docker.com/ai/mcp-catalog-and-toolkit/toolkit/
4. https://docs.docker.com/ai/mcp-catalog-and-toolkit/get-started/
5. https://docs.docker.com/ai/mcp-catalog-and-toolkit/mcp-gateway/
6. https://www.docker.com/products/mcp-catalog-and-toolkit/
7. https://github.com/docker/mcp-gateway + GitHub API 2026-08-15