Docker Docs, verified

MCP server by Docker · Verified

Fetch the official Docker documentation as Markdown, covering Engine, Compose, Hub and more.

No sign-in (No account or key needed)Streamable HTTP

Connect to Docker Docs

No sign-in needed. Connect with Docker Docs’s own URL:

https://mcp-docs.docker.com/mcp

Paste it into any client that supports remote MCP servers. Your client talks to Docker directly, not through mcp.tc.

Share this server

Opens this page, with the URL and setup steps.

mcp.tc/i/docker-docs

About

Connects to the official Docker documentation at docs.docker.com. Its single tool fetches the documentation index (llms.txt) and returns it as Markdown, so an assistant can answer questions about Docker from the current source instead of memory.

It runs as a hosted streamable HTTP endpoint at mcp-docs.docker.com. No sign-in or API key is needed.

What you can do

  • Fetch Docker documentation as Markdown
  • Read the docs.docker.com llms.txt index
  • Ground answers about Docker in current official docs

Tools 1

  • fetch_docker_docs

    Fetches Docker documentation from docs.docker.com/llms.txt and returns it as Markdown.

Read from the live server on 3 Oct 2026.

Example prompts

  • Fetch the Docker docs and explain how to containerize a Node app.

  • Look up the Docker documentation on Compose file syntax.

  • What do the Docker docs say about Docker Build Cloud?

  • Find the Docker docs section on Docker Hardened Images.

Set up

Every client connects to mcp-docs.docker.com. Pick yours; the page remembers your choice.

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport http docker-docs https://mcp-docs.docker.com/mcp
  1. Start Claude Code and type /mcp. docker-docs should show as connected.

Add --scope user to make it available in every project, not just this one.

Claude Desktop

  1. Open Settings → Connectors and click Add custom connector.
  2. Name it Docker Docs and paste this URL:
https://mcp-docs.docker.com/mcp
  1. Click Add. Its tools appear in the chat’s tools menu.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

claude.ai

  1. Open the connector form on claude.ai. This button fills in the name and URL for you:
  1. Check that the URL reads https://mcp-docs.docker.com/mcp and click Add.
  2. Turn it on in a chat from the tools menu.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.

ChatGPT

  1. On chatgpt.com, open Settings → Security and login and turn on Developer mode.
  2. Go to chatgpt.com/plugins and click + to create an app for a remote MCP server.
  3. Paste https://mcp-docs.docker.com/mcp as the server URL and choose No authentication.

Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.

Cursor

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.json
{
  "mcpServers": {
    "docker-docs": {
      "url": "https://mcp-docs.docker.com/mcp"
    }
  }
}

VS Code

Or from a terminal:

code --add-mcp '{"name":"docker-docs","type":"http","url":"https://mcp-docs.docker.com/mcp"}'

Or commit it to the repo in .vscode/mcp.json:

.vscode/mcp.json
{
  "servers": {
    "docker-docs": {
      "type": "http",
      "url": "https://mcp-docs.docker.com/mcp"
    }
  }
}

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "docker-docs": {
      "serverUrl": "https://mcp-docs.docker.com/mcp"
    }
  }
}
  1. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.

Codex

codex mcp add docker-docs --url https://mcp-docs.docker.com/mcp

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.docker-docs]
url = "https://mcp-docs.docker.com/mcp"

Gemini CLI

gemini mcp add --transport http docker-docs https://mcp-docs.docker.com/mcp

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI’s settings file.

{
  "mcpServers": {
    "docker-docs": {
      "type": "http",
      "url": "https://mcp-docs.docker.com/mcp"
    }
  }
}

Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.

Client only starts local servers? Bridge it with npx -y mcp-remote https://mcp-docs.docker.com/mcp.

FAQ

Can I paste mcp.tc/i/docker-docs into my MCP client?

No. mcp.tc links are pages, not server addresses. Connect with https://mcp-docs.docker.com/mcp, so your client talks to Docker Docs directly. The quick link is for sharing: it opens this page, with setup steps for every client.

Does Docker Docs need an API key or a sign-in?

No. Docker Docs doesn’t ask for an account or key.

Is Docker Docs a remote or a local server?

Remote. Docker hosts it at https://mcp-docs.docker.com/mcp, and it speaks Streamable HTTP. There’s nothing to install.

What can Docker Docs do?

It has 1 tool: fetch_docker_docs. You can fetch Docker documentation as Markdown, read the docs.docker.com llms.txt index and ground answers about Docker in current official docs.

Which clients can use it?

Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT in developer mode, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.

Who wrote this page?

mcp.tc’s robot read Docker Docs’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

Embed

Show Docker Docs in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work

README badge

Badge preview, lightBadge preview, dark
Markdown
[![Docker Docs on mcp.tc](https://mcp.tc/i/docker-docs/badge.svg)](https://mcp.tc/i/docker-docs)
HTML
<a href="https://mcp.tc/i/docker-docs"><img src="https://mcp.tc/i/docker-docs/badge.svg" alt="Docker Docs on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

HTML
<script src="https://mcp.tc/w/docker-docs.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

HTML
<iframe src="https://mcp.tc/embed/docker-docs" title="Docker Docs on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/docker-docs.json

What each field means

mcp.tc isn’t affiliated with Docker. This page was built from Docker Docs’s public metadata, last checked on 3 Oct 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.