What problem does it solve?
Integrating external services into Claude Code can be blocked by unclear setup steps, mismatched transport/auth expectations, and tool-naming constraints that prevent safe command/agent usage.
Core Features & Use Cases
- Connect and configure MCP servers using
.mcp.json or plugin.json so tools are discovered and usable.
- Support multiple transports (stdio, SSE, HTTP, WebSocket) and map each to the right use case such as local tooling, hosted OAuth services, REST APIs, or real-time streaming.
- Enable secure authentication patterns including OAuth for SSE/HTTP and token/env-based auth for HTTP/stdio, with guidance for required environment variable documentation.
- Control tool access safely by using
allowed-tools to restrict exactly which MCP tools commands can call.
Use this when you need to add or configure an MCP server (e.g., “add MCP server”, “integrate MCP”, “use .mcp.json”, “set up Model Context Protocol”, or “connect external service”) so that Claude Code plugins can expose external capabilities as structured tools.
Quick Start
Add a .mcp.json file at your plugin root that defines your MCP server transport (stdio/SSE/HTTP/ws) and then verify the server and tool names by running the /mcp command in Claude Code.