mcp-integration

Integrate MCP servers into Claude Code plugins as callable tools.

28|5|Updated Jun 24, 2025
One-click install
npx skills add https://github.com/thevibeworks/claude-code-docs --skill mcp-integration-thevibeworks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-integration
Source: https://github.com/thevibeworks/claude-code-docs/tree/main/content/github/claude-plugins-official/plugins/plugin-dev/skills/mcp-integration
Command: npx skills add https://github.com/thevibeworks/claude-code-docs --skill mcp-integration-thevibeworks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the problem of integrating external tools and services into Claude Code plugins by wiring up Model Context Protocol (MCP) servers so they can be called as first-class tools.

Core Features & Use Cases

  • MCP server integration: Add and configure MCP servers so Claude Code can discover and register tools exposed by external services.
  • Multiple transport support: Configure stdio (local process) and remote transports like SSE, HTTP, and WebSocket with appropriate authentication patterns.
  • Plugin-friendly deployment: Use a dedicated .mcp.json workflow (recommended) or inline plugin.json configuration for portable, maintainable setups.

Quick Start

Ask Claude Code to configure Model Context Protocol for your plugin so it can connect your chosen MCP server type (stdio, SSE, HTTP, or ws) and expose the resulting tools under the correct mcp__plugin_* naming scheme.

Frequently Asked Questions about mcp-integration

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

FAQPage Schema
How do I integrate an MCP server into a Claude Code plugin?

To integrate an MCP server into a Claude Code plugin, configure transport-specific connectivity using a root-level .mcp.json file or inline plugin.json mcpServers, exposing external services as callable tools.

What transports are supported for connecting Model Context Protocol servers?

Model Context Protocol server configuration supports multiple transports including local stdio processes and remote SSE, HTTP, and WebSocket connections, each with appropriate authentication patterns like OAuth or tokens.

How do I secure MCP server access using environment variables and OAuth?

Secure MCP server access by configuring environment variables and OAuth or token patterns within the transport fields of your .mcp.json configuration, ensuring secure URL and header usage.

What is the naming convention for calling MCP tools in Claude Code plugins?

MCP tools in Claude Code plugins are accessed via the allowed-tools list using the mcp__plugin_<plugin>_<server>__<tool> naming convention to register and invoke the exposed external services.

Should I use .mcp.json or plugin.json for MCP server configuration?

Using a dedicated root-level .mcp.json workflow is recommended for portable, maintainable MCP server configuration, though inline plugin.json mcpServers configuration is also supported for deployment.

Does Model Context Protocol work with remote HTTP and WebSocket services?

Yes, Model Context Protocol works with remote HTTP and WebSocket services by configuring the appropriate transport fields and securing access via environment variables or OAuth/token authentication patterns.