MCP Integration

Integrate MCP servers by creating a .mcp.json configuration file at your plugin root that maps tools to server commands and specifies connection types (stdio, SSE, HTTP, WebSocket). Set required environment variables and the plugin will expose 10+ external tools securely within Claude Code.

MCP integration supports OAuth and token-based authentication patterns. Configure credentials through environment variables in your .mcp.json or plugin.json mcpServers configuration, enabling secure access to external services without exposing secrets.

Yes, you can bundle MCP servers with plugins for automatic setup and consistent deployments. Reference local server binaries in your .mcp.json using relative paths like "${CLAUDE_PLUGIN_ROOT}/servers/example-server" alongside environment-variable configuration.

MCP supports stdio, SSE, HTTP, and WebSocket connection types. Choose based on your server deployment model—stdio for local processes, HTTP or WebSocket for hosted services, and SSE for server-sent event streams.

Define environment variables in your .mcp.json or plugin.json mcpServers block using standard expansion syntax. Claude Code plugins read these variables at runtime to authenticate with external services and pass credentials securely to MCP servers.

Pre-allowlists are supported for explicit MCP tool naming and security control. Define which tools from your MCP server are exposed to Claude Code, ensuring only approved tools are available and reducing attack surface.