What problem does it solve?
Connect Reactive Agents to external MCP servers reliably by selecting the correct transport, managing Docker container lifecycle, and ensuring tools are discovered and authenticated so agents can call MCP tools transparently.
Core Features & Use Cases
- Automatic Transport Detection: Infers stdio versus HTTP-based transports and races stdio probe against detected HTTP endpoints to choose the correct mode.
- Docker Lifecycle Management: Starts and reliably tears down Docker-hosted MCP servers with PID-scoped container naming and explicit container removal to avoid orphaned containers.
- Flexible Connectivity: Supports stdio MCPs (GitHub, filesystem), HTTP or streamable endpoints (context7, remote MCPs), local processes, and npx-launched servers, plus environment and header-based auth handling.
- Use Case: Run a local GitHub MCP in Docker with a personal access token, let the framework auto-detect transport, and have the agent discover and call repository tools without manual wiring.
Quick Start
Start an agent configured with a Docker MCP server by calling withMCP to run the container, build the agent, and verify the agent discovered the MCP tools.