mcp-integration

Configure MCP servers in Claude Code plugins with transport and auth settings.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps you set up Model Context Protocol (MCP) servers so your Claude Code plugins can connect to external services and expose them as usable tools.

Core Features & Use Cases

  • MCP server configuration guidance: Shows how to define MCP servers via a dedicated .mcp.json or inline mcpServers in plugin.json.
  • Transport + auth coverage: Explains the differences and correct configurations for stdio, SSE, HTTP, and ws, including environment-variable auth patterns and OAuth expectations.
  • Tool naming and safe enablement: Provides the required MCP tool naming convention and shows how to pre-allow specific tools for command security.
  • Lifecycle and debugging: Describes how servers start, when connections are made, how to verify with /mcp, and how to debug with claude --debug.

Quick Start

Tell the AI to generate a .mcp.json for a plugin-root-local (stdio) MCP filesystem server using ${CLAUDE_PLUGIN_ROOT} for portable paths and include guidance for verifying the tools via /mcp.

Frequently Asked Questions about mcp-integration

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

FAQPage Schema
How do I add an MCP server to a Claude Code plugin?

To add an MCP server to a Claude Code plugin, define the server configuration in a dedicated `.mcp.json` file or inline within `plugin.json` to expose external services as callable tools.

What transport types can I configure for MCP servers in Claude Code?

MCP servers in Claude Code support stdio, SSE, HTTP, and WebSocket transport types, each requiring specific configuration patterns for environment variables and OAuth authentication.

How do I verify and debug MCP server connections in Claude Code?

Verify MCP server connections and available tools using the `/mcp` command, and debug server lifecycle or connection issues by running Claude Code with the `claude --debug` flag.

What is the correct way to name and allow MCP tools for plugin security?

MCP tools must follow a specific naming convention and be pre-allowed in your configuration to ensure command security, restricting plugin workflows to explicitly enabled external service tools.

Can I use environment variables for MCP server auth in plugin configurations?

Yes, you can wire environment variables for authentication in MCP server configurations, applying OAuth expectations and secure auth patterns for stdio, SSE, HTTP, and WebSocket transports.

How do I use portable paths when configuring a local stdio MCP server?

When configuring a plugin-root-local stdio MCP server, use the `${CLAUDE_PLUGIN_ROOT}` variable in your `.mcp.json` file to ensure portable paths across different environments.