MCP Integration

Integrate external services into Claude Code plugins via MCP.

33.3k|3.8k|Updated Nov 20, 2025
One-click install
npx skills add https://github.com/anthropics/claude-plugins-official --skill mcp-integration-anthropics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: MCP Integration
Source: https://github.com/anthropics/claude-plugins-official/tree/main/plugins/plugin-dev/skills/mcp-integration
Command: npx skills add https://github.com/anthropics/claude-plugins-official --skill mcp-integration-anthropics

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill simplifies the integration of external services and APIs with Claude Code plugins using the Model Context Protocol (MCP), enabling Claude to interact with databases, cloud services, and custom tools. It removes the complexity of setting up external tool access.

Core Features & Use Cases

  • Multi-Protocol Support: Integrate servers via stdio (local processes), SSE (hosted services with OAuth), HTTP (REST APIs), or WebSocket (real-time).
  • Secure Authentication: Guidance on OAuth, token-based, and environment variable authentication patterns.
  • Portable Configuration: Use ${CLAUDE_PLUGIN_ROOT} for robust, portable server definitions.
  • Use Case: Integrate a project management tool like Asana by configuring an SSE MCP server, allowing Claude to create tasks, update statuses, and query project details directly from user prompts.

Quick Start

Use the MCP Integration skill to configure a new stdio MCP server for local file system access in your plugin.

Frequently Asked Questions about MCP Integration

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

FAQPage Schema
How do I connect Claude to external APIs and services?

MCP Integration connects Claude to external services through the Model Context Protocol, supporting stdio, SSE, HTTP, and WebSocket server types. Configure servers via .mcp.json or plugin.json with authentication details, and Claude automatically discovers and manages available tools.

What authentication methods does MCP support?

MCP Integration supports OAuth, token-based authentication, and environment variable expansion for secure credential handling. Environment variables can be referenced portably using ${CLAUDE_PLUGIN_ROOT} in server configurations.

Can I use MCP to integrate local tools and remote APIs together?

Yes. MCP Integration handles both local processes via stdio and remote services via SSE, HTTP, or WebSocket in the same plugin. Mix connection types by configuring multiple servers with their respective protocols and authentication.

How does MCP server configuration work in Claude Code plugins?

MCP servers are configured through dedicated .mcp.json files or inline within plugin.json. Specify the protocol type, server endpoint or command, authentication credentials, and JSON schemas for tool calls. Claude Code automatically starts and reconciles servers on plugin load.

What's the difference between stdio and SSE MCP servers?

Stdio MCP servers run as local processes spawned by the plugin, ideal for file system or local tool access. SSE servers are hosted services accessed over HTTP with server-sent events, better suited for cloud APIs and services requiring OAuth authentication.

Do I need to write custom code to add MCP tools to Claude?

No. MCP Integration handles tool discovery and lifecycle automatically. Define JSON schemas for tool parameters and responses in your server configuration, and Claude discovers them without additional plugin code.