What problem does it solve?
This skill removes the complexity of exposing external services as tools inside Claude Code plugins by standardizing Model Context Protocol (MCP) server configuration, authentication, tool discovery, and lifecycle management so developers can integrate third-party APIs, databases, and local tools reliably.
Core Features & Use Cases
- Multi-transport support: Guidance for stdio (local processes), SSE, HTTP, and WebSocket MCP servers to support local tools, hosted services, REST APIs, and real-time streams.
- Authentication patterns: Clear instructions for OAuth flows, bearer tokens, dynamic header helpers, and environment-variable-based credentials for secure access.
- Lifecycle & tooling: Best practices for .mcp.json or plugin.json configuration, environment variable expansion (including ${CLAUDE_PLUGIN_ROOT}), tool naming conventions, pre-allowing tools in commands, startup/restart behavior, and error handling.
- Testing & debugging: Local testing checklist, use of /mcp for discovery, and recommendations for debug logging, batching, and performance considerations.
- Use case: Bundle a local database MCP server for data queries, add an Asana SSE integration for task management, or connect to a third-party REST MCP backend for automated workflows.
Quick Start
Add a .mcp.json to the plugin root with your server entry, document required environment variables, enable the plugin locally, and run /mcp to verify tool discovery and authentication.