Docker MCP Catalog and Toolkit vs MCP Everything Server

A side-by-side look at pricing, capabilities, pros, cons, and our editorial scores.

	Docker MCP Catalog and Toolkit MCP Servers	MCP Everything Server MCP Servers
Tagline	Discover, run, and manage MCP servers as Docker containers.	The kitchen-sink reference MCP server that exercises every corner of the Model Context Protocol
Category	MCP Servers	MCP Servers
Pricing	Freemium· Docker Personal: $0 · Docker Pro: $11 · Docker Team: $16 · Docker Business: $24	Free· Free and open source (MIT License). No cloud service or paid tier — you run it locally via npx, Docker, or your MCP client of choice.
Model	—	—
Editorial score	—	—
Use cases	Wiring Claude Desktop into Postgres, GitHub, and StripeGiving Cursor sandboxed shell and filesystem accessRunning a private team catalog of internal MCP serversAggregating many MCP servers behind one Gateway endpointCentralised secret management for AI tool credentialsOAuth-authenticated MCP servers for SaaS APIsPublishing a company's own MCP server to Docker HubLocal agent development with logging and call tracingEnterprise governance over which MCP tools developers can enable	MCP client conformance testingRegression testing of stdio and Streamable HTTP transportsVerifying sampling round-trip behavior in a new agent hostDebugging elicitation UI in an IDE integrationReference reading for authoring a new MCP serverDemoing MCP primitives in workshops and talksSmoke-testing cancellation and progress-notification handlingValidating resource-subscription update delivery
Pros	Largest curated catalog of containerised MCP servers, with images from major vendors (GitHub, Stripe, MongoDB, Elastic, Grafana, Neo4j and more). Every server runs sandboxed in a container with least-privilege defaults, avoiding the security foot-guns of running raw npx/uvx MCP processes. One-click enable/disable in Docker Desktop's MCP Toolkit UI, no hand-editing JSON config for each AI client. MCP Gateway multiplexes many servers behind a single endpoint with built-in logging, call tracing, and OAuth helpers. Central Docker Desktop secret store means credentials are entered once and reused across Claude, Cursor, VS Code, Windsurf, and others. Gateway and registry are open source under MIT, so teams can self-host or customise the plumbing. Enterprise controls through Docker Business (image access policies, registry access management) make it viable for regulated shops.	Only server that exercises the full MCP feature matrix in one place — tools, resources, prompts, sampling, elicitation, roots, logging, subscriptions, and Tasks Maintained by the Model Context Protocol project itself, so behavior tracks the spec as it evolves (SEP-1686 Tasks, Streamable HTTP, etc.) Runs anywhere an MCP client runs — npx, Docker, Claude Desktop, VS Code, Cursor, Windsurf — with stdio or HTTP transports TypeScript source is short and readable, making it a de-facto reference for how each handler should be shaped MIT-licensed, no telemetry, no signup, no cloud dependency Includes progress notifications and cancellation flows that most tutorial servers skip, so client cancel/timeout logic can be exercised properly
Cons	Requires Docker Desktop (or at minimum a Docker Engine) — extra weight if you only wanted a single Python MCP server. Container cold-starts add noticeable latency versus running an MCP server directly on the host. Catalog quality is uneven: some third-party servers are thin wrappers or lag behind their upstream projects. Advanced enterprise features (private catalogs, RBAC, image access management) sit behind Docker Business pricing. Windows and Linux workflows are less polished than macOS; some Toolkit features assume Docker Desktop UI, not headless engines. Still a moving target — MCP itself is young and the Toolkit's UX, config format, and CLI flags change between Docker Desktop releases.	Explicitly not useful for end users — it does not do anything a human would actually want done Feature drift means some primitives (SEP-1686 Tasks, elicitation) may not yet be implemented in every client, producing red herrings during testing Documentation is a single features.md; there is no guided tour that maps each tool to the spec section it exercises TypeScript-only reference — Python or Rust client authors have to translate patterns themselves Sampling and elicitation flows depend on the client honoring them, so a silent client makes it hard to tell whether the server or the client is at fault
Website	www.docker.com	github.com

Pick Docker MCP Catalog and Toolkit if

✅ Largest curated catalog of containerised MCP servers, with images from major vendors (GitHub, Stripe, MongoDB, Elastic, Grafana, Neo4j and more).
✅ Every server runs sandboxed in a container with least-privilege defaults, avoiding the security foot-guns of running raw npx/uvx MCP processes.
✅ One-click enable/disable in Docker Desktop's MCP Toolkit UI, no hand-editing JSON config for each AI client.
✅ MCP Gateway multiplexes many servers behind a single endpoint with built-in logging, call tracing, and OAuth helpers.

Pick MCP Everything Server if

✅ Only server that exercises the full MCP feature matrix in one place — tools, resources, prompts, sampling, elicitation, roots, logging, subscriptions, and Tasks
✅ Maintained by the Model Context Protocol project itself, so behavior tracks the spec as it evolves (SEP-1686 Tasks, Streamable HTTP, etc.)
✅ Runs anywhere an MCP client runs — npx, Docker, Claude Desktop, VS Code, Cursor, Windsurf — with stdio or HTTP transports
✅ TypeScript source is short and readable, making it a de-facto reference for how each handler should be shaped

Compare a different pair →