mcp-integration SKILL.md skillA

mcp-integration from tylerjrbuell/reactive-agents-ts is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add tylerjrbuell/reactive-agents-ts/mcp-integration@git:20260410.eb63c8f

Pins git:20260410.eb63c8f in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

tylerjrbuell/reactive-agents-ts

Path

.agents/skills/mcp-integration/SKILL.md

Versions recorded

1

Latest version

git:20260410.eb63c8f, committed Apr 10, 2026

Size

4,948 bytes

Repository stars

31

License

MIT

MCP client integration patterns for packages/tools/src/mcp/. Docker container lifecycle, transport auto-detection, two-phase container naming, and cleanup. Use when working on MCP server configuration, docker-based MCP tools, or the mcp-client.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# MCP Integration Patterns

## The Critical Rule

```
docker rm -f <containerName> is the ONLY reliable container stop.
subprocess.kill() is NOT sufficient.
```

Killing the `docker run` process leaves the container alive in the Docker daemon. `docker rm -f` is the only operation that reliably terminates AND removes the container. This is non-negotiable.

## Two Docker MCP Patterns

| Pattern | Examples | Container behavior |
|---------|---------|-------------------|
| **stdio MCP** | GitHub MCP, filesystem MCP | Container reads JSON-RPC from stdin; responds on stdout |
| **HTTP-only MCP** | mcp/context7 | Container starts an HTTP server on a port; ignores stdin |

Both are handled transparently. The client auto-detects which pattern applies.

## Transport Auto-Detection

The MCP client races two connection methods when starting a docker container:

1. **stdio connect** — attempts to connect via stdin/stdout immediately
2. **HTTP URL detection** — watches container stderr for a URL pattern (e.g., `http://localhost:3000`)

When HTTP wins the race, the client switches to port-mapped HTTP mode automatically. No manual configuration needed.
…

Read the whole file at its exact version.

How to install

mdr add tylerjrbuell/reactive-agents-ts/mcp-integration@sha256:2e0899c7003b8934

[![mdr](https://markdownregistry.com/badge/art_w4bg4xjfzkmu4gxk.svg)](https://markdownregistry.com/a/art_w4bg4xjfzkmu4gxk)

Versions

The registry has recorded 1 version of this file, committed on Apr 10, 2026.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_w4bg4xjfzkmu4gxk
GET https://markdownregistry.com/api/v1/resolve?ref=tylerjrbuell/reactive-agents-ts/mcp-integration
GET https://markdownregistry.com/api/v1/blob/2e0899c7003b8934a5b1a498607d0d76d8e57d8bfa933b5a54b9633d4ab6c95b

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from tylerjrbuell/reactive-agents-ts

Every file in tylerjrbuell/reactive-agents-ts

Other files named mcp-integration

Browse by kind, by grade A, or by owner.