MCP Integration

Integrate external MCP servers with Claude Code plugins across stdio, SSE, HTTP, and WebSocket.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/mamba-mental/rize-mcp-ultimate --skill mcp-integration-mamba-mental
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: MCP Integration
Source: https://github.com/mamba-mental/rize-mcp-ultimate/tree/main/.cursor/skills/mcp-integration
Command: npx skills add https://github.com/mamba-mental/rize-mcp-ultimate --skill mcp-integration-mamba-mental

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the challenge of integrating external MCP servers with Claude Code plugins, enabling plugins to expose external services as MCP-enabled tools within Claude's ecosystem.

Core Features & Use Cases

  • Exposes external services as MCP tools across stdio, SSE, HTTP, and WebSocket configurations.
  • Provides a guided integration workflow including plugin.json/.mcp.json configuration and environment variable documentation.
  • Supports OAuth and token-based authentication patterns, tool discovery, and lifecycle management for MCP servers.

Quick Start

  1. Create a .mcp.json at your plugin root (or configure via plugin.json) to define MCP servers.
  2. Document required environment variables in the plugin README.
  3. Use Claude Code commands to verify MCP integration with the /mcp command and discover available tools.

Frequently Asked Questions about MCP Integration

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

FAQPage Schema
How do I integrate external MCP servers with Claude Code plugins?

You can integrate external MCP servers by creating a .mcp.json file at your plugin root or configuring them via plugin.json to expose external services as MCP tools within Claude's ecosystem.

What transport protocols are supported for MCP integration in Claude Code?

MCP integration supports stdio, SSE, HTTP, and WebSocket configurations, allowing you to expose external services as MCP-enabled tools across various network transport layers.

How do I configure OAuth and token-based authentication for an MCP server?

OAuth and token-based authentication patterns are supported directly through the MCP integration workflow, requiring you to document the necessary environment variables in your plugin README.

What is the best way to discover available MCP tools after configuring a server?

To discover available MCP tools, use the Claude Code /mcp command to verify your MCP integration and list all tools exposed by the configured external servers.

Does MCP integration require specific frontmatter metadata for Claude Code plugins?

Yes, MCP integration enforces frontmatter metadata requirements to ensure proper plugin configuration, alongside a structured guidance body with optional resources for full server integration.

Why do I need to document environment variables for my MCP plugin?

Documenting environment variables in the plugin README is required because MCP servers often rely on OAuth tokens and configuration variables to authenticate and connect to external services.