MCP Integration

Expose external services as MCP tools across stdio, SSE, HTTP, and WebSocket servers.

Updated Jan 13, 2026
One-click install
npx skills add https://github.com/lusya123/cloudcode --skill mcp-integration-lusya123
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: MCP Integration
Source: https://github.com/lusya123/cloudcode/tree/main/claude-code-main/plugins/plugin-dev/skills/mcp-integration
Command: npx skills add https://github.com/lusya123/cloudcode --skill mcp-integration-lusya123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claude Code plugins often need reliable access to external services. MCP integration provides a standardized bridge to expose external capabilities as tools inside Claude Code, reducing bespoke wiring and improving plugin interoperability.

Core Features & Use Cases

  • Exposes external services as MCP tool sets within plugins, enabling cross-service automation and orchestration.
  • Supports all MCP server types (stdio, SSE, HTTP, WebSocket) to fit local, cloud, and hybrid deployments.
  • Includes lifecycle guidance from server discovery to runtime tool invocation, with secure authentication patterns (OAuth and tokens) and environment-variable configuration.
  • Real-world use cases include integrating databases, SaaS APIs, and cloud services as first-class tools in plugin workflows.

Quick Start

Configure an MCP server at the plugin root (for example, via a .mcp.json file) and verify the available tools using Claude Code's /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 expose external services as tools in Claude Code via MCP?▼

To expose external services via MCP, configure an MCP server at the plugin root using a .mcp.json file to bridge external capabilities as tool sets. This enables cross-service automation and orchestration directly inside Claude Code plugins.

What MCP server types are supported for Claude Code plugin integration?▼

MCP integration supports stdio, SSE, HTTP, and WebSocket server types to fit local, cloud, and hybrid deployments. This allows flexible connectivity when exposing external services as first-class tools in plugin workflows.

How do I configure authentication and environment variables for an MCP server?▼

MCP server configuration supports secure authentication patterns including OAuth and tokens, alongside environment-variable expansion. These are defined within the .mcp.json file to manage credentials and runtime settings safely.

What is the lifecycle of an MCP tool from server startup to invocation?▼

The MCP lifecycle spans server discovery, startup, and runtime tool invocation. This process is managed through standardized configuration and environment-variable expansion to ensure reliable tool availability within Claude Code.

Can I integrate databases and SaaS APIs into Claude Code plugins using MCP?▼

Yes, MCP integration enables connecting databases, SaaS APIs, and cloud services as first-class tools in plugin workflows. This standardizes external service access and reduces bespoke wiring for cross-service automation.

How do I verify available MCP tools after configuring a server?▼

After configuring an MCP server via .mcp.json, verify available tools using Claude Code's /mcp command. This confirms successful server startup, tool discovery, and lifecycle management from configuration to invocation.