MCP Integration

Configure MCP servers with stdio, SSE, HTTP, and WebSocket transports.

2|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Clay-HHK/claude-config --skill mcp-integration-clay-hhk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: MCP Integration
Source: https://github.com/Clay-HHK/claude-config/tree/main/skills/mcp-integration
Command: npx skills add https://github.com/Clay-HHK/claude-config --skill mcp-integration-clay-hhk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

MCP Integration removes the complexity of exposing external services and tools to Claude Code plugins by standardizing connection methods, authentication, tool discovery, and lifecycle management so plugins can safely and reliably call external systems as MCP tools.

Core Features & Use Cases

  • Multi-transport support: Configure stdio (local processes), SSE (hosted with OAuth), HTTP (REST/token), and WebSocket (real-time) MCP servers.
  • Authentication patterns: Built-in guidance for OAuth flows, bearer/token headers, environment variable passing, and dynamic header helpers for rotating credentials.
  • Configuration best practices: Use .mcp.json or plugin.json, prefer ${CLAUDE_PLUGIN_ROOT} for paths, and document required environment variables.
  • Tool naming & security: Automatic MCP tool naming, pre-allow patterns for commands, and recommendations to avoid wildcards and hardcoded secrets.
  • Lifecycle & debugging: Startup/shutdown behavior, lazy connection semantics, restart expectations, and debug tips (claude --debug, /mcp).
  • Use cases: Expose local file systems, bundle custom stdio servers, connect to Asana/GitHub via SSE, integrate REST APIs, and enable real-time streams with WebSocket servers.

Quick Start

Create a .mcp.json at your plugin root with the server entry, set required environment variables in your shell or README, then run /mcp to verify the server and tools are available.

Frequently Asked Questions about MCP Integration

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

FAQPage Schema
How do I integrate an external MCP server into a Claude Code plugin?

Configure an MCP server by creating a .mcp.json file at your plugin root with the server entry and setting required environment variables. Run /mcp to verify the server connection and confirm that the external tools are available.

What transport protocols can I use to connect external services as MCP tools?

MCP integration supports multiple transport protocols including stdio for local processes, SSE for hosted services with OAuth, HTTP for REST endpoints with token authentication, and WebSocket for real-time integrations. Choose the protocol that matches your external service architecture.

How do I handle OAuth and token-based authentication for MCP servers?

MCP integration provides built-in authentication patterns for OAuth flows, bearer token headers, and environment variable passing. Use dynamic header helpers for rotating credentials and avoid hardcoding secrets directly in your configuration files.

Does MCP integration work with local stdio servers and hosted SSE services?

Yes, MCP integration supports both local stdio servers and hosted SSE services. You can bundle custom stdio servers for local file systems or connect to hosted services like Asana and GitHub via SSE with OAuth authentication.

Why are my MCP tools not showing up after configuring the server?

If MCP tools are missing, use the claude --debug command or the /mcp command to check server startup behavior and connection status. Verify your .mcp.json configuration, environment variable expansion, and ensure lazy connection semantics are properly initialized.

What environment variables and path configurations do I need for MCP server setup?

Use ${CLAUDE_PLUGIN_ROOT} for path configurations in your .mcp.json or plugin.json files. Document all required environment variables in your README and set them in your shell, applying pre-allow patterns for commands while avoiding wildcards.