MCP Integration

Configure MCP servers in Claude Code plugins with transports and authentication.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/quanngynx/GDGO-2026.Servexa-Warranty-AI --skill mcp-integration-quanngynx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: MCP Integration
Source: https://github.com/quanngynx/GDGO-2026.Servexa-Warranty-AI/tree/main/servexa-warranty-ai/.cursor/skills/mcp-integration
Command: npx skills add https://github.com/quanngynx/GDGO-2026.Servexa-Warranty-AI --skill mcp-integration-quanngynx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Integrating Model Context Protocol (MCP) servers into Claude Code plugins can be confusing because you must correctly configure transports, authentication, tool naming, and secure access controls. This Skill turns that setup into a clear, repeatable process so external services become usable tools inside your plugin.

Core Features & Use Cases

  • Configure MCP server transport (stdio, SSE, HTTP, WebSocket): Select the correct connection method and required fields for local servers or hosted cloud services.
  • Implement plugin-level MCP configuration: Add .mcp.json at the plugin root or configure mcpServers in plugin.json to bundle servers with your plugin.
  • Handle authentication safely (OAuth, bearer tokens, env vars, dynamic headers): Use the right auth pattern per transport and document required environment variables.
  • Secure tool access with allowed-tools: Pre-allow specific MCP tool names (or carefully scoped wildcards) for command security.
  • Troubleshoot and validate: Use /mcp and debug logs to ensure servers appear and tools work reliably.

Quick Start

Use this Skill to configure a plugin’s MCP connection by adding a .mcp.json at the plugin root for your MCP server (including URL/command, transport type, and authentication details), then 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 configure an MCP server in Claude Code?

To configure an MCP server in Claude Code, add a `.mcp.json` file at your plugin root or define `mcpServers` in `plugin.json`, specifying the transport type, command or URL, and authentication details. You then validate the connection using the `/mcp` command.

What MCP transport types are supported for Claude Code plugins?

Claude Code plugins support stdio, SSE, HTTP, and WebSocket transports for MCP servers. You select the correct connection method based on whether you are running local servers or connecting to hosted cloud services.

How does OAuth authentication work with MCP servers?

OAuth authentication for MCP servers involves selecting the right auth pattern per transport, handling dynamic headers, and documenting required environment variables. The setup ensures secure access to external services exposed as callable tools within your plugin.

How do I secure MCP tool access with allowed-tools?

To secure MCP tool access with allowed-tools, you pre-allow specific MCP tool names or use carefully scoped wildcards. This command security pattern prevents unauthorized tool execution while maintaining plugin functionality.

Why is my MCP server not showing up in Claude Code?

If your MCP server is not showing up in Claude Code, you should troubleshoot the configuration by checking transport selection, authentication handling, and tool naming. Use debug logs and the `/mcp` command to validate server visibility and tool reliability.

Can I bundle MCP servers directly inside my Claude Code plugin?

Yes, you can bundle MCP servers with your Claude Code plugin by adding `.mcp.json` at the plugin root or configuring `mcpServers` in `plugin.json`. This exposes external services as callable tools for your plugin.