mcp-integration

Connect MCP servers with Claude Code plugins for structured tool access.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/astrosteveo/marketplace --skill mcp-integration-astrosteveo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-integration
Source: https://github.com/astrosteveo/marketplace/tree/main/plugins/plugin-dev/skills/mcp-integration
Command: npx skills add https://github.com/astrosteveo/marketplace --skill mcp-integration-astrosteveo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

MCP integration enables Claude Code plugins to connect external services via the Model Context Protocol (MCP), enabling structured tool access and seamless tool discovery.

Core Features & Use Cases

  • MCP server support: stdio (local), SSE (hosted), HTTP (REST), and WebSocket servers for versatile tool access.
  • Automatic tool discovery: Tools are registered and exposed as mcp__plugin_<plugin>_<server>__<tool-name>, visible in /mcp.
  • Authentication & security: Supports OAuth for SSE/HTTP and token-based headers with environment-variable expansion; aligns with best security practices.
  • Lifecycle & configuration: Server startup, connection management, and per-plugin configuration (via .mcp.json or inline definitions).

Quick Start

Add an MCP configuration at the plugin root (e.g., .mcp.json) or declare an inline server, then test with the /mcp command and start using MCP tools.

Frequently Asked Questions about mcp-integration

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

FAQPage Schema
How do I connect an MCP server to Claude Code plugins?

To connect an MCP server to Claude Code plugins, add a valid MCP configuration file like .mcp.json or declare inline server definitions at the plugin root. This enables structured tool access and automatic tool discovery for external services.

Can I use environment variables for MCP server authentication tokens?

Yes, MCP server authentication supports environment-variable expansion for tokens and endpoints. It also supports OAuth for SSE and HTTP servers, ensuring secure token-based header management aligned with best security practices.

What types of MCP servers are supported for external service integration?

MCP integration supports four server types: local stdio, hosted SSE, HTTP, and WebSocket servers. This allows versatile tool access across different communication protocols for connecting external services to Claude Code.

How does tool discovery work when integrating MCP servers?

MCP integration provides automatic tool discovery by registering and exposing tools using the naming convention mcp__plugin_<plugin>_<server>__<tool-name>. You can view these registered tools using the /mcp command after configuration.

Do I need a .mcp.json file to configure MCP server connections?

You need either a valid .mcp.json configuration file at the plugin root or inline server definitions. Both methods support environment-variable expansion for tokens and endpoints, enabling flexible per-plugin server lifecycle and connection management.

Why are my MCP tools not showing up after server configuration?

MCP tools appear as mcp__plugin_<plugin>_<server>__<tool-name> and are visible via the /mcp command. If they are missing, verify your .mcp.json or inline definitions are correct, ensure server startup succeeds, and confirm environment variables for authentication are properly set.