What problem does it solve?
Claude Code plugins often need to connect to external services via MCP servers. This skill provides a structured approach to configure, discover MCP-backed tools, and securely authenticate and manage tool access.
Core Features & Use Cases
- MCP configuration guidance for stdio, SSE, HTTP, and WebSocket MCP servers at plugin roots.
- Tool discovery and naming conventions to expose external tools as mcp__plugin_<plugin>_<server>__<tool>.
- Authentication patterns including OAuth and token-based schemes, with guidance on secure storage and best practices.
- Use case examples such as integrating a database or cloud service into a Claude Code plugin, and managing multiple MCP servers within a plugin.
Quick Start
Start by adding an MCP configuration at the plugin root, verify available MCP servers with the /mcp command, and call an MCP tool to perform a test operation. Example config at plugin root:
{
"my-plugin": {
"type": "stdio",
"command": "node",
"args": ["server.js"]
}
}
Then run: claude --debug and use /mcp to validate.