mcp-integration

Define .mcp.json configurations to link MCP servers with Claude Code plugins.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/LounisBou/claude-code --skill mcp-integration-lounisbou
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-integration
Source: https://github.com/LounisBou/claude-code/tree/main/skills-available/mcp/mcp-integration
Command: npx skills add https://github.com/LounisBou/claude-code --skill mcp-integration-lounisbou

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Integrate MCP servers with Claude Code plugins by defining standardized .mcp.json configurations, enabling tool exposure and secure transport for external services.

Core Features & Use Cases

  • Supports local stdio MCP servers and hosted MCP servers via SSE, HTTP, and WS
  • Handles authentication patterns, environment-variable expansion, and transport configuration
  • Enables tool discovery and usage through the /mcp interface for cross-service automation

Quick Start

Create a .mcp.json at your plugin root to define MCP servers and enable tool discovery via /mcp.

Frequently Asked Questions about mcp-integration

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

FAQPage Schema
How do I connect an MCP server to a Claude Code plugin?

To connect an MCP server to a Claude Code plugin, you define a standardized .mcp.json configuration file at your plugin root. This file specifies the server connection details, enabling tool discovery and exposure from external services via the /mcp interface.

What transport types are supported for MCP server integration?

MCP server integration supports local stdio servers alongside hosted SSE, HTTP, and WebSocket server types. The configuration enforces secure transport protocols like HTTPS and WSS to ensure safe communication between the Claude Code plugin and external services.

Can I use environment variables and OAuth in .mcp.json configurations?

Yes, .mcp.json configurations support environment-variable expansion for dynamic values and handle OAuth alongside token-based authentication patterns. This allows secure credential management and lifecycle configuration when linking external MCP servers.

How does tool discovery work with linked MCP servers?

Tool discovery works through the /mcp interface once the .mcp.json configuration links your MCP servers. It enables cross-service automation by exposing and discovering available tools from the connected external services with scoped tool permissions.

What is the best way to secure MCP server connections in Claude Code plugins?

The best way to secure MCP server connections is by enforcing HTTPS and WSS transport protocols within your .mcp.json configuration. The integration also supports scoped tool permissions and token-based authentication patterns to restrict access safely.

Do I need a specific file format to enable MCP server lifecycle management?

Yes, you need a .mcp.json file placed at your plugin root to enable MCP server lifecycle management. This standardized configuration file defines the server types, transport settings, and authentication patterns required for proper lifecycle control.