mcp-integration

Configure MCP servers as callable tools in Claude Code plugins.

1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/Leap0920/Clean-Portfolio --skill mcp-integration-leap0920
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-integration
Source: https://github.com/Leap0920/Clean-Portfolio/tree/main/%25USERPROFILE%25/.openclaude/plugins/marketplaces/claude-plugins-official/plugins/plugin-dev/skills/mcp-integration
Command: npx skills add https://github.com/Leap0920/Clean-Portfolio --skill mcp-integration-leap0920

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you integrate Model Context Protocol (MCP) servers so Claude Code plugins can access external services as structured tools, without fragile ad-hoc API wiring.

Core Features & Use Cases

  • Configure MCP server transports: Set up stdio, sse, http, and ws connections based on where the MCP server runs (local or hosted) and how it communicates.
  • Secure authentication handling: Use OAuth (typically for SSE/HTTP) or token/header/env-based auth patterns with safe practices and clear guidance.
  • Ship and auto-wire servers: Bundle MCP servers for a plugin using a recommended .mcp.json workflow, while keeping setup portable via ${CLAUDE_PLUGIN_ROOT}.
  • Control tool access safely: Pre-allow specific tool names with allowed-tools, including understanding tool naming like mcp__plugin_<plugin>_<server>__<tool>.
  • Operate reliably: Plan for lifecycle behavior, discovery via /mcp, and debugging with claude --debug when connections or tool discovery fail.

Quick Start

Tell your AI: "I need to integrate an MCP server into my Claude Code plugin using SSE—give me a .mcp.json example, explain how OAuth works, and list the exact steps to verify tool availability with /mcp."

Frequently Asked Questions about mcp-integration

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

FAQPage Schema
How do I configure an MCP server in a Claude Code plugin?

To configure an MCP server, define the connection settings in a `.mcp.json` or `plugin.json` file, specifying the transport type (`stdio`, `sse`, `http`, or `ws`) and using `${CLAUDE_PLUGIN_ROOT}` for portable environment variable expansion.

How does OAuth work with hosted MCP servers using SSE or HTTP?

OAuth for hosted MCP servers secures tool access by authenticating external services before they are exposed as callable tools, typically applying to SSE or HTTP transports within your Claude Code plugin configuration.

What is the best way to pre-allow specific MCP tools in Claude Code?

Pre-allow specific MCP tools by adding their full naming patterns, such as `mcp__plugin_<plugin>_<server>__<tool>`, to the `allowed-tools` configuration, ensuring safe and controlled tool access during discovery.

Why does my MCP server connection fail during tool discovery?

If MCP server connections or tool discovery fail, run `claude --debug` to inspect lifecycle behavior, and use the `/mcp` command to verify tool availability and troubleshoot transport-specific settings.

Can I use stdio to connect local MCP servers to Claude Code?

Yes, you can connect local MCP servers using the `stdio` transport, allowing external services to become structured tools within Claude Code plugins without requiring fragile ad-hoc API wiring.

What is the purpose of the .mcp.json file in Claude Code plugins?

The `.mcp.json` file bundles and auto-wires MCP servers into a Claude Code plugin, providing a structured workflow to define transports, secure authentication, and control tool access for external services.