MCP Integration

Integrate external service tools into Claude Code plugins via MCP.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/kgadek/kgadek-claude-plugin --skill mcp-integration-kgadek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: MCP Integration
Source: https://github.com/kgadek/kgadek-claude-plugin/tree/main/ai-spec/2026-01-21-sdd-inspirations/references/anthropics-claude-plugins-official/plugins/plugin-dev/skills/mcp-integration
Command: npx skills add https://github.com/kgadek/kgadek-claude-plugin --skill mcp-integration-kgadek

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

MCP integration enables Claude Code plugins to securely expose external services as MCP tools, unifying access and management.

Core Features & Use Cases

  • Expose tools across multiple server types (stdio, SSE, HTTP, ws) for plugin audiences.
  • Support configuration via .mcp.json at plugin root or plugin.json (mcpServers) for flexibility.
  • Include lifecycle, authentication, and security guidelines to simplify adoption.

Quick Start

Create an MCP configuration at the plugin root (.mcp.json) or in plugin.json (mcpServers) and verify tool availability with the /mcp command.

Frequently Asked Questions about MCP Integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I integrate external service tools into Claude Code plugins using MCP?

To integrate external service tools into Claude Code plugins using MCP, create an MCP configuration at the plugin root (.mcp.json) or within plugin.json (mcpServers), then verify tool availability with the /mcp command.

What server types can I bundle when configuring MCP tools for plugin development?

When configuring MCP tools for plugin development, you can bundle multiple server types including stdio, SSE, HTTP, and WebSocket to expose external service capabilities as standardized tools.

How does MCP integration handle authentication and security for external services?

MCP integration handles authentication and security for external services by applying specific guidelines for lifecycle, authorization, and security best practices to simplify adoption for plugin developers.

Do I need environment variable expansion for MCP server configuration?

Yes, environment variable expansion is a required standard for MCP server configuration, alongside tool naming conventions and server configuration practices to ensure secure and flexible tool exposure.

What is the best way to manage the lifecycle of MCP servers in a plugin?

The best way to manage the lifecycle of MCP servers in a plugin is to follow the established MCP integration guidelines, which cover lifecycle management, authentication, and security best practices for bundled server types.

Can I use .mcp.json instead of plugin.json for MCP server configuration?

Yes, you can use a .mcp.json file at the plugin root instead of plugin.json for MCP server configuration, providing flexibility in how you define and expose external service tools.