mcp-integration

Automate MCP server integration into Claude Code plugins via .mcp.json or plugin.json.

Updated Dec 17, 2024
One-click install
npx skills add https://github.com/LAF-US/IDAHO-VAULT --skill mcp-integration-laf-us
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-integration
Source: https://github.com/LAF-US/IDAHO-VAULT/tree/main/.claude/plugins/marketplaces/claude-plugins-official/plugins/plugin-dev/skills/mcp-integration
Command: npx skills add https://github.com/LAF-US/IDAHO-VAULT --skill mcp-integration-laf-us

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

MCP server integration is centralized for Claude Code plugins, enabling seamless external tool access via Model Context Protocol.

Core Features & Use Cases

  • Exposes external tools from MCP servers to Claude Code plugins
  • Supports stdio, SSE, HTTP, and WebSocket MCP server types with OAuth or token-based auth
  • Provides two configuration methods: a dedicated .mcp.json at plugin root or inline in plugin.json, along with environment variable support
  • Use Case: Bundle multiple MCP servers and discover tools via the /mcp interface for commands and agents

Quick Start

Configure MCP in your plugin by using a .mcp.json file or a plugin.json entry and verify tool availability 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 integrate an MCP server into a Claude Code plugin?

MCP server integration for Claude Code plugins supports stdio, SSE, HTTP, and WebSocket server types. It manages authentication via OAuth or token-based methods and bundles multiple MCP servers together for deterministic startup and external tool access.

Can I use environment variables for MCP server configuration in Claude Code?

After integrating MCP servers into your Claude Code plugin, you can discover and verify available external tools using the /mcp interface. This interface exposes the bundled tools for use by commands and agents within your plugin.

What MCP server types are supported for external tool discovery in Claude Code?

Claude Code enforces support for stdio, SSE, HTTP, and WebSocket MCP server types. These types allow plugins to expose external tools and manage authentication, including OAuth or token-based methods, for deterministic startup.

Does Claude Code support OAuth for MCP server authentication?

Yes, Claude Code supports OAuth and token-based authentication for MCP server integration. This allows plugin authors to securely manage access to external tools exposed via stdio, SSE, HTTP, or WebSocket server types.

How do I verify external tool availability after configuring an MCP server?

You can verify external tool availability by running the /mcp command in Claude Code after configuring your servers in .mcp.json or plugin.json. This interface lists all discovered tools from your bundled MCP servers for commands and agents.