mcp-integration

To integrate MCP servers, create a .mcp.json file at your plugin root or add an mcpServers entry to plugin.json. You then reference tools using the mcp__plugin_<plugin>_<server>__<tool> naming convention within your commands.

MCP integration supports four server types: local stdio, hosted SSE, HTTP, and WebSocket servers. Each type handles secure configurations, environment-variable expansion, and automatic credential management across the server lifecycle.

Authentication for MCP tools uses either OAuth or token-based authentication depending on the server type. The integration handles automatic credential passing and environment-variable expansion to securely connect external services without bespoke wiring.

Yes, MCP integration supports multi-server plugin architectures and enterprise setups. You can orchestrate automated tools across multiple services simultaneously by configuring multiple server definitions within your .mcp.json or plugin.json file.

The mcp__ prefix is required for tool naming so Claude Code can correctly route commands to the appropriate plugin and server. The full format is mcp__plugin_<plugin>_<server>__<tool>, ensuring unique identification across multi-server architectures.

Yes, configuring MCP integration requires documenting required environment variables and scopes for secure plugin operation. This ensures proper credential handling and lifecycle management across the chosen stdio, SSE, HTTP, or WebSocket server types.