Bundle MCP servers in container images for stdio transport

[pavelanni]

Summary

Include select MCP servers in the specialized Docker images so agents can invoke them via stdio transport without external infrastructure.

Motivation

Some capabilities are better served by MCP servers than raw CLI tools — particularly interactive/stateful tools like browser automation. Bundling MCP servers in the image and invoking them via stdio keeps the deployment self-contained.

Candidates

MCP Server	Image flavor	Why MCP over CLI
Playwright	media, content	JavaScript rendering, structured page interaction, navigation state
SQLite	data	Structured queries, schema introspection
Filesystem	docs	Already have read/write tools, but MCP version adds watch/search

When CLI tools are better

Stateless transformations (pandoc, imagemagick, ffmpeg) work fine as CLI tools invoked via exec. MCP adds value only when the tool needs state between calls or structured output beyond what stdout provides.

Design considerations

• MCP servers installed as npm packages or standalone binaries in the image
• DocsClaw spawns MCP server as a child process, communicates via stdio
• Depends on MCP client integration for external tool servers #2 (MCP client integration in DocsClaw)
• Configuration in agent-config.yaml specifies which MCP servers to start

Related

• MCP client integration for external tool servers #2 — MCP client integration
• Specialized Dockerfiles for agent flavors (docs, media, data, presentations, content) #7 — Specialized Dockerfiles