MCP Integration

MCP Integration exposes MCP servers as tools within Claude Code plugins, enabling seamless connections to external services like APIs, databases, file systems, and cloud services through stdio, SSE, HTTP, or WebSocket protocols. Configure servers in .mcp.json with automatic authentication and tool discovery.

Yes, MCP Integration supports multi-server setup with OAuth and token-based authentication. Configure each server separately in .mcp.json with environment variable expansion and dynamic headers, enabling secure token storage and automatic MCP server startup across stdio, SSE, HTTP, and WebSocket transports.

Create a .mcp.json file in your plugin root with server definitions including command, arguments, and environment variables. MCP Integration handles automatic startup, tool discovery, and authentication configuration, exposing 10+ tools per server immediately upon plugin load.

No, MCP Integration uses declarative configuration via .mcp.json or inline plugin.json. Define server connection details, authentication credentials, and environment variables; the Skill automates tool exposure, OAuth flows, and secure token handling without custom integration code.

Yes, MCP Integration supports OAuth and token-based authentication flows with secure token storage. Configure OAuth parameters in .mcp.json with environment variable expansion, and the Skill manages credential exchange, refresh, and dynamic header injection across all server types.

MCP Integration supports stdio, SSE (Server-Sent Events), HTTP, and WebSocket transports for MCP server connections. Each protocol is configured in .mcp.json with automatic server startup, enabling connectivity across synchronous and streaming communication patterns.