Mcp Integration

anthropics/claude-plugins-officialOfficial

This is your bridge between Claude Code plugins and external services through the Model Context Protocol. It handles four connection types: stdio for local processes, SSE for OAuth-enabled cloud services, HTTP for REST APIs, and WebSocket for real-time streams. The skill walks you through bundling MCP servers with your plugin, either in a dedicated .mcp.json or inline in plugin.json, complete with environment variable expansion using ${CLAUDE_PLUGIN_ROOT} for portability. Tools get auto-prefixed as mcp__plugin_name_server__tool_name, which matters when you're setting up allowed-tools in command frontmatter. The documentation is thorough on authentication patterns and lifecycle management, though you'll want to be careful with token handling and avoid wildcard tool permissions.

skills.sh installs: 7.5K
GitHub stars: 46.7K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add anthropics/claude-plugins-official --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: