MCP Integration

Configure Claude Code plugins to connect external services via MCP servers.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/rawhit-r/ai-files --skill mcp-integration-rawhit-r
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: MCP Integration
Source: https://github.com/rawhit-r/ai-files/tree/main/.gemini/mcp-integration
Command: npx skills add https://github.com/rawhit-r/ai-files --skill mcp-integration-rawhit-r

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Enables Claude Code plugins to connect external services through Model Context Protocol (MCP) servers, enabling structured tool access and cross-service integration.

Core Features & Use Cases

  • Supports multiple MCP server types (stdio, SSE, HTTP, WebSocket) with automatic tool discovery via /mcp.
  • Provides secure authentication patterns (OAuth and tokens) for cloud services and APIs.
  • Exposes MCP tools per server for plugin ecosystems.

Quick Start

Configure an MCP server at the plugin root and verify the exposed tools with the /mcp command.

Frequently Asked Questions about MCP Integration

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

FAQPage Schema
How do I connect external services to Claude Code using the Model Context Protocol?

You connect external services to Claude Code by configuring an MCP server at the plugin root, which securely exposes external APIs through structured tools. The integration uses a frontmatter-driven entry specifying the server name and description to enable cross-service access.

What MCP server transport types are supported for external service integration?

MCP integration supports stdio, SSE, HTTP, and WebSocket server types for external service connections. This allows plugin developers to connect diverse external APIs and cloud services through the Model Context Protocol using various network communication standards.

How does authentication work when accessing external APIs through MCP servers?

Authentication for MCP servers accessing external APIs uses secure patterns like OAuth and tokens for cloud services. The integration manages environment expansion and lifecycle behavior to safely authenticate and maintain connections between Claude Code plugins and external services.

Can I use optional plugin components like scripts and references when configuring MCP tools?

Yes, MCP integration supports optional plugin components including scripts, references, and assets alongside the mandatory frontmatter entry. These components help define environment expansion, authentication patterns, lifecycle behavior, and tool naming conventions for the exposed MCP tools.

How do I discover available external service tools after setting up an MCP server?

You discover available external service tools by running the /mcp command after configuring your MCP server at the plugin root. This automatic tool discovery feature exposes the MCP tools provided by each connected server for use in the plugin ecosystem.