Skip to main content
📖 The AI Tool Bible

Docker MCP Catalog and Toolkit vs Linear MCP Server

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

 Docker MCP Catalog and Toolkit logo
Docker MCP Catalog and Toolkit
MCP Servers
Linear MCP Server logo
Linear MCP Server
MCP Servers
TaglineDiscover, run, and manage MCP servers as Docker containers.Open-source MCP server bridging LLM agents to Linear's issue tracker (now deprecated in favour of Linear's official remote MCP)
CategoryMCP ServersMCP Servers
PricingFreemium· Docker Personal: $0 · Docker Pro: $11 · Docker Team: $16 · Docker Business: $24Free· Free and open source (MIT). Requires a Linear account and personal API key; Linear itself is free for small teams, $8/user/mo Standard, $14/user/mo Plus.
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
Filing bugs from Claude Desktop or Cursor without leaving the editorAgent-driven triage of the inbox projectBulk relabeling or reprioritising issues via natural languageStandup summaries of a user's assigned Linear workAdding comments to tickets from a coding agent's PR reviewReference implementation for building a custom Linear MCP server
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.
  • Open source (MIT) and small enough to read end-to-end in an afternoon
  • One-line install via Smithery or straight npx in Claude Desktop config
  • Covers the create / update / search / comment loop that 90% of ticket workflows need
  • Works with any MCP client, not just Claude Desktop (Cursor, Zed, Continue, custom agents)
  • Clear tool schemas make it a good reference implementation for building your own MCP servers
  • Uses Linear's official GraphQL API, so permissions and audit trails stay intact
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.
  • Officially deprecated by its author in favour of Linear's own remote MCP server at mcp.linear.app/sse
  • Runs as a local stdio process, so it has to be installed on every workstation and cannot be shared across a team
  • Uses a personal API key, meaning every action shows up as the key owner rather than the actual LLM user
  • Tool coverage is narrower than the official server: no cycles, projects, roadmaps, or workflow state management
  • Error handling and rate-limit backoff are minimal; heavy agent loops can trip Linear's API limits
Websitewww.docker.comgithub.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 Linear MCP Server if
  • ✅ Open source (MIT) and small enough to read end-to-end in an afternoon
  • ✅ One-line install via Smithery or straight npx in Claude Desktop config
  • ✅ Covers the create / update / search / comment loop that 90% of ticket workflows need
  • ✅ Works with any MCP client, not just Claude Desktop (Cursor, Zed, Continue, custom agents)
Compare a different pair →