What problem does it solve?
MCP Integration removes the complexity of exposing external services and tools to Claude Code plugins by standardizing connection methods, authentication, tool discovery, and lifecycle management so plugins can safely and reliably call external systems as MCP tools.
Core Features & Use Cases
- Multi-transport support: Configure stdio (local processes), SSE (hosted with OAuth), HTTP (REST/token), and WebSocket (real-time) MCP servers.
- Authentication patterns: Built-in guidance for OAuth flows, bearer/token headers, environment variable passing, and dynamic header helpers for rotating credentials.
- Configuration best practices: Use .mcp.json or plugin.json, prefer ${CLAUDE_PLUGIN_ROOT} for paths, and document required environment variables.
- Tool naming & security: Automatic MCP tool naming, pre-allow patterns for commands, and recommendations to avoid wildcards and hardcoded secrets.
- Lifecycle & debugging: Startup/shutdown behavior, lazy connection semantics, restart expectations, and debug tips (claude --debug, /mcp).
- Use cases: Expose local file systems, bundle custom stdio servers, connect to Asana/GitHub via SSE, integrate REST APIs, and enable real-time streams with WebSocket servers.
Quick Start
Create a .mcp.json at your plugin root with the server entry, set required environment variables in your shell or README, then run /mcp to verify the server and tools are available.