Summary
Add Model Context Protocol (MCP) client capabilities to DocsClaw so agents can connect to external MCP tool servers.
Motivation
MCP provides a standardized way to expose tools to LLM agents. Rather than building every tool into DocsClaw, agents could connect to MCP servers for capabilities like database access, browser automation, or domain-specific APIs.
Design considerations
- Support stdio transport for MCP servers bundled in the same container image
- Support SSE/streamable HTTP transport for remote MCP servers
- MCP server configuration via
agent-config.yaml
- Tool definitions from MCP servers should integrate with the existing tool registry
Related
- See #N (specialized Dockerfiles) — some flavors will bundle MCP servers invoked via stdio
- Evaluate whether Playwright MCP server is preferable to CLI-based web tools for interactive browsing
From roadmap: docs/slides/docsclaw-intro.html, slide 6
Summary
Add Model Context Protocol (MCP) client capabilities to DocsClaw so agents can connect to external MCP tool servers.
Motivation
MCP provides a standardized way to expose tools to LLM agents. Rather than building every tool into DocsClaw, agents could connect to MCP servers for capabilities like database access, browser automation, or domain-specific APIs.
Design considerations
agent-config.yamlRelated
From roadmap: docs/slides/docsclaw-intro.html, slide 6