MCP Integration

MCP server integration with Claude Code plugins requires configuring .mcp.json or plugin.json at your plugin root with server details (stdio, SSE, HTTP, or WebSocket), then verifying tool discovery via the /mcp command to expose external service tools.

MCP integration supports OAuth-based, token-based, and environment-driven credential handling. Environment variables expand automatically within configuration, enabling secure credential management across stdio, SSE, HTTP, and WebSocket server types.

Yes, .mcp.json and plugin.json support multiple server configurations. Each server type (stdio, SSE, HTTP, WebSocket) connects independently with automatic lifecycle management, tool naming conventions, and unified tool discovery through the /mcp command.

Create a .mcp.json file at your plugin root with your MCP server configuration, run the /mcp command to verify tool discovery, then begin calling the exposed tools directly within your plugin commands.

Configuration differs by server type—stdio uses process spawning, while HTTP and WebSocket use network endpoints. Both .mcp.json and plugin.json support all types with environment variable expansion and automatic lifecycle management for each.

Use environment variables for credentials, avoid hardcoding tokens, apply OAuth and token-based authentication patterns, validate external service endpoints, and manage server lifecycle automatically to prevent credential exposure and unauthorized access.