What problem does it solve?
Integrating Model Context Protocol (MCP) servers into Claude Code plugins can be confusing because you must correctly configure transports, authentication, tool naming, and secure access controls. This Skill turns that setup into a clear, repeatable process so external services become usable tools inside your plugin.
Core Features & Use Cases
- Configure MCP server transport (stdio, SSE, HTTP, WebSocket): Select the correct connection method and required fields for local servers or hosted cloud services.
- Implement plugin-level MCP configuration: Add
.mcp.json at the plugin root or configure mcpServers in plugin.json to bundle servers with your plugin.
- Handle authentication safely (OAuth, bearer tokens, env vars, dynamic headers): Use the right auth pattern per transport and document required environment variables.
- Secure tool access with allowed-tools: Pre-allow specific MCP tool names (or carefully scoped wildcards) for command security.
- Troubleshoot and validate: Use
/mcp and debug logs to ensure servers appear and tools work reliably.
Quick Start
Use this Skill to configure a plugin’s MCP connection by adding a .mcp.json at the plugin root for your MCP server (including URL/command, transport type, and authentication details), then verify tool availability with the /mcp command.