Mcp Integration

This handles Model Context Protocol server integration for Claude Code plugins, letting you expose external services as tools. You get four connection types: stdio for local processes, SSE for OAuth-enabled cloud services, HTTP for REST APIs, and WebSocket for real-time stuff. The configuration lives in either a dedicated .mcp.json or inline in plugin.json, with automatic environment variable expansion using ${CLAUDE_PLUGIN_ROOT} for portability. Tools get prefixed as mcp__plugin_name_server__tool_name and can be pre-allowed in command frontmatter. The documentation is thorough on lifecycle management and auth patterns, which matters because you're dealing with credentials and external connections. Use this when you need more than 10 related tools from a single service or complex OAuth flows that regular plugin tools can't handle cleanly.

skills.sh installs: 173
GitHub stars: 476
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add aiskillstore/marketplace --skill mcp-integration --agent claude-code

Installs into .claude/skills of the current project.

Files

MCP Integration for Claude Code Plugins

Overview

Model Context Protocol (MCP) enables Claude Code plugins to integrate with external services and APIs by providing structured tool access. Use MCP integration to expose external service capabilities as tools within Claude Code.

Key capabilities:

Connect to external services (databases, APIs, file systems)
Provide 10+ related tools from a single service
Handle OAuth and complex authentication flows
Bundle MCP servers with plugins for automatic setup

MCP Server Configuration Methods

Plugins can bundle MCP servers in two ways:

Method 1: Dedicated .mcp.json (Recommended)

Create .mcp.json at plugin root:

{
  "database-tools": {
    "command": "${CLAUDE_PLUGIN_ROOT}/servers/db-server",
    "args": ["--config", "${CLAUDE_PLUGIN_ROOT}/config.json"],
    "env": {
      "DB_URL": "${DB_URL}"
    }
  }
}

Benefits: