MCP Integration

Topics in the source

• MCP Integration for Claude Code Plugins
• Overview
• MCP Server Configuration Methods
• Method 1: Dedicated .mcp.json (Recommended)
• Method 2: Inline in plugin.json
• MCP Server Types
• stdio (Local Process)
• SSE (Server-Sent Events)

Model Context Protocol (MCP) enables Claude Code plugins to integrate with external services and APIs by providing structured tool access. Use MCP integration to expose external service capabilities as tools within Claude Code. Key capabilities: Connect to external services (databases, APIs, file systems) Provide 10+ related tools from a single service Handle OAuth and complex authentication flows Bundle MCP servers with plugins for automatic setup Plugins can bundle MCP servers in two ways: Create .mcp.json at plugin root: Benefits: Clear separation of concerns Easier to maintain Better for multiple servers Add mcpServers field to plugin.json: Benefits: Single configuration file Good for simple single-server plugins Execute local MCP servers as child processes. Best for local tools and custom servers. Configuration: Use cases: File system access Local database connections Custom MCP servers NPM-packaged MCP servers Process management: Claude Code spawns and manages the process Communicates via stdin/stdout Terminates when Claude Code exits Connect to hosted MCP servers with OAuth support. Best for cloud services. Configuration: Use cases: Official hosted MCP servers (Asana, GitHub

This is an excerpt. Refer to the complete source and its current requirements.