MCP Integration

Integrate external services into Claude Code plugins as MCP tools.

6|Updated Dec 11, 2025
One-click install
npx skills add https://github.com/jawhnycooke/claude-plugins --skill mcp-integration-jawhnycooke
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: MCP Integration
Source: https://github.com/jawhnycooke/claude-plugins/tree/main/plugins/plugin-dev/skills/mcp-integration
Command: npx skills add https://github.com/jawhnycooke/claude-plugins --skill mcp-integration-jawhnycooke

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill simplifies the integration of Claude Code plugins with external services and APIs using the Model Context Protocol (MCP), enabling structured tool access without complex manual setup. It allows Claude to interact with the outside world autonomously.

Core Features & Use Cases

  • Multi-Protocol Support: Integrate external services via stdio (local processes), SSE (cloud services), HTTP (REST APIs), or WebSocket (real-time).
  • Automated Tool Discovery: External service capabilities are automatically exposed as pre-fixed tools within Claude Code, ready for use by agents and commands.
  • Secure Authentication: Supports various authentication patterns including OAuth (automatic), token-based (headers), and environment variables for robust security.
  • Use Case: Integrate a GitHub MCP server into your plugin to allow Claude to autonomously create issues, manage pull requests, or fetch repository data, streamlining development workflows.

Quick Start

Use the MCP Integration skill to configure a new stdio MCP server for local filesystem 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 services and APIs?

MCP Integration exposes external service capabilities as tools within Claude Code through the Model Context Protocol. Configure a stdio, SSE, HTTP, or WebSocket MCP server in your plugin's .mcp.json or plugin.json, and Claude automatically discovers and uses those tools.

What authentication methods does MCP support for external services?

MCP Integration supports OAuth (automatic), token-based authentication via headers, and environment variable expansion. Configure credentials in .mcp.json with the mcp__plugin naming scheme, and authentication is handled transparently across all protocol transports.

Can I use MCP to integrate local processes and cloud APIs in the same plugin?

Yes. MCP Integration supports multiple protocols simultaneously: stdio for local processes, SSE and HTTP for cloud services, and WebSocket for real-time connections. Configure each MCP server independently, and all tools are accessible within Claude Code.

How does tool discovery work when I add an MCP server?

Tool discovery is automated through the /mcp interface. Once an MCP server is configured, Claude Code queries it to expose available capabilities as pre-prefixed tools. External service functions become immediately available without manual tool definition.

What configuration formats does MCP Integration require?

MCP Integration uses dedicated .mcp.json configuration or inline plugin.json settings. Both support environment variable expansion, dynamic headers, lifecycle management, and cross-server configuration for managing multiple MCP servers across different protocols.

Do I need to write code to set up MCP server integration?

No. MCP Integration streamlines setup through declarative configuration in .mcp.json or plugin.json. Authentication patterns, protocol selection, and tool exposure are handled through configuration—no custom code required for basic integrations.