MCP Integration

MCP Integration enables Claude Code plugins to access external services by configuring Model Context Protocol servers. Support includes stdio, SSE, HTTP, and WebSocket protocols, with built-in authentication handling, environment variable expansion, and tool discovery for databases, cloud services, and custom APIs.

MCP Integration handles OAuth flows, token authentication, and environment variable-based credentials. It manages dynamic headers and secure credential passing across stdio, SSE, HTTP, and WebSocket server configurations for seamless plugin authentication.

Yes. MCP Integration lets you configure multiple servers—stdio, SSE, HTTP, WebSocket—in a single plugin. This supports concurrent access to databases, cloud platforms, and custom APIs with independent authentication and lifecycle management for each service.

MCP Integration automatically expands environment variables in server configurations and manages credential injection across all protocol types. This enables secure, externalized credential management without embedding secrets in plugin code.

MCP server configuration requires specifying the protocol type (stdio, SSE, HTTP, WebSocket), server endpoint URL, authentication credentials or tokens, and environment variables. MCP Integration handles tool discovery, naming conventions, lifecycle management, and error handling automatically.

No. MCP Integration automates tool discovery, naming conventions, and lifecycle management. It exposes all available tools from configured servers—whether external APIs like Asana or custom endpoints—without manual enumeration or wrapper code.