mcp-integration

Connect MCP servers to Claude Code plugins by creating a .mcp.json configuration file or adding MCP settings to plugin.json. Define the server type (stdio, HTTP, SSE, or WebSocket), authentication credentials, and environment variables, then verify the connection using /mcp commands to expose external service capabilities as tools.

Claude Code supports stdio, HTTP, SSE, and WebSocket MCP server deployments. Each type enables different communication patterns for integrating external services; stdio and HTTP work for local or remote servers, while SSE and WebSocket provide streaming and persistent connections for real-time tool access.

Manage credentials securely by storing authentication tokens and API keys in environment variables, then referencing them in .mcp.json or plugin.json using variable expansion. Use HTTPS for HTTP servers and WSS for WebSocket to ensure encrypted communications during external service integration.

Yes, make MCP configurations portable by using environment variables and the CLAUDE_PLUGIN_ROOT variable in your .mcp.json or plugin.json. This approach allows the same configuration to work across development, testing, and deployment environments without hardcoding paths or credentials.

Document explicit tool permissions, required environment variables, and local testing procedures via /mcp commands in your MCP configuration. This ensures users understand which external services each tool accesses and can verify connectivity before deploying the plugin to production.

Use a dedicated .mcp.json for centralized MCP server configuration and easier maintenance. Configure MCP inline in plugin.json only when portability within a single plugin definition is prioritized; the dedicated file approach scales better for multiple or complex server setups.