mcp-tool-integration

Connect Reactive Agents to MCP servers with automatic transport detection and Docker lifecycle management.

21|4|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/tylerjrbuell/reactive-agents-ts --skill mcp-tool-integration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-tool-integration
Source: https://github.com/tylerjrbuell/reactive-agents-ts/tree/main/apps/docs/skills/mcp-tool-integration
Command: npx skills add https://github.com/tylerjrbuell/reactive-agents-ts --skill mcp-tool-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about mcp-tool-integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I connect an agent to an MCP server using stdio or HTTP?

To connect an agent to an MCP server, use the framework to auto-detect transport by racing a stdio probe against HTTP endpoints, ensuring reliable tool discovery for stdio or streamable-http connections.

How does Docker lifecycle management work for local MCP servers?

Docker lifecycle management for MCP servers uses PID-scoped container naming and explicit container removal during teardown to start and reliably shut down servers, preventing orphaned containers from persisting in your environment.

Can I use environment variables and headers for MCP server authentication?

Yes, you can use environment variables and headers for MCP server authentication, allowing you to securely pass credentials like a GitHub personal access token to Docker-hosted or remote streamable-http MCP endpoints.

Does MCP tool integration support npx-launched servers and local processes?

MCP tool integration supports npx-launched servers and local processes alongside Docker-hosted and remote endpoints, allowing agents to discover and transparently call external tools across various transport mechanisms.

What is the best way to avoid orphaned Docker containers when running MCP tools?

The best way to avoid orphaned Docker containers when running MCP tools is to use a framework that applies PID-scoped container naming and explicit container removal to manage the Docker lifecycle and ensure reliable teardown.