What problem does it solve?
This Skill helps you integrate Model Context Protocol (MCP) servers so Claude Code plugins can access external services as structured tools, without fragile ad-hoc API wiring.
Core Features & Use Cases
- Configure MCP server transports: Set up
stdio, sse, http, and ws connections based on where the MCP server runs (local or hosted) and how it communicates.
- Secure authentication handling: Use OAuth (typically for SSE/HTTP) or token/header/env-based auth patterns with safe practices and clear guidance.
- Ship and auto-wire servers: Bundle MCP servers for a plugin using a recommended
.mcp.json workflow, while keeping setup portable via ${CLAUDE_PLUGIN_ROOT}.
- Control tool access safely: Pre-allow specific tool names with
allowed-tools, including understanding tool naming like mcp__plugin_<plugin>_<server>__<tool>.
- Operate reliably: Plan for lifecycle behavior, discovery via
/mcp, and debugging with claude --debug when connections or tool discovery fail.
Quick Start
Tell your AI: "I need to integrate an MCP server into my Claude Code plugin using SSE—give me a .mcp.json example, explain how OAuth works, and list the exact steps to verify tool availability with /mcp."