David Karlsson
19b44c2f42
Remove the E2B workflow and integration documentation and both Ollama application guides. Remove E2B navigation and promotional links. Redirect former E2B URLs to Docker Sandboxes and former Ollama guide URLs to Docker Model Runner.
4.0 KiB
url, title, linkTitle, params, weight, description, keywords, grid
| url | title | linkTitle | params | weight | description | keywords | grid | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| /ai/mcp-catalog-and-toolkit/ | Docker MCP Catalog and Toolkit | MCP Catalog and Toolkit |
|
20 | Learn about Docker's MCP catalog on Docker Hub | Docker, ai, mcp servers, ai agents, extension, docker desktop, llm, docker hub |
|
{{< summary-bar feature_name="Docker MCP Catalog and Toolkit" >}}
Model Context Protocol (MCP) is an open protocol that standardizes how AI applications access external tools and data sources. By connecting LLMs to local development tools, databases, APIs, and other resources, MCP extends their capabilities beyond their base training.
The challenge is that running MCP servers locally creates operational friction. Each server requires separate installation and configuration for every application you use. You run untrusted code directly on your machine, manage updates manually, and troubleshoot dependency conflicts yourself. Configure a GitHub server for Claude, then configure it again for Cursor, and so on. Each time you manage credentials, permissions, and environment setup.
Docker MCP features
The MCP Toolkit and MCP Gateway solve these challenges through centralized management. Instead of configuring each server for every AI application separately, you set things up once and connect all your clients to it. The workflow centers on three concepts: catalogs, profiles, and clients.
Catalogs are curated collections of MCP servers. The Docker MCP Catalog provides 300+ verified servers packaged as container images with versioning, provenance, and security updates. Organizations can create custom catalogs with approved servers for their teams.
Profiles organize servers into named collections for different projects. Your "web-dev" profile might use GitHub and Playwright; your "backend" profile, database tools. Profiles support both containerized servers from catalogs and remote MCP servers. Configure a profile once, then share it across clients or with your team.
Clients are the AI applications that connect to your profiles. Claude Code, Cursor, Zed, and others connect through the MCP Gateway, which routes requests to the right server and handles authentication and lifecycle management.
Note
MCP Gateway as part of Docker AI Governance is an invite-only feature. Contact Docker Sales to learn more.
Learn more
{{< grid >}}