mcp-integration

Configure MCP servers and authenticate tools for Claude Code plugins.

Updated Oct 26, 2025
One-click install
npx skills add https://github.com/Conte777/config_for_claude_code --skill mcp-integration-conte777
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-integration
Source: https://github.com/Conte777/config_for_claude_code/tree/main/src/skills/mcp-integration
Command: npx skills add https://github.com/Conte777/config_for_claude_code --skill mcp-integration-conte777

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claude Code plugins often need to connect to external services via MCP servers. This skill provides a structured approach to configure, discover MCP-backed tools, and securely authenticate and manage tool access.

Core Features & Use Cases

  • MCP configuration guidance for stdio, SSE, HTTP, and WebSocket MCP servers at plugin roots.
  • Tool discovery and naming conventions to expose external tools as mcp__plugin_<plugin>_<server>__<tool>.
  • Authentication patterns including OAuth and token-based schemes, with guidance on secure storage and best practices.
  • Use case examples such as integrating a database or cloud service into a Claude Code plugin, and managing multiple MCP servers within a plugin.

Quick Start

Start by adding an MCP configuration at the plugin root, verify available MCP servers with the /mcp command, and call an MCP tool to perform a test operation. Example config at plugin root: { "my-plugin": { "type": "stdio", "command": "node", "args": ["server.js"] } } Then run: claude --debug and use /mcp to validate.

Frequently Asked Questions about mcp-integration

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

FAQPage Schema
How do I configure external services in Claude Code plugins via MCP?

To configure external services via MCP, add an MCP server configuration at the plugin root using a .mcp.json or plugin.json file. Specify the server type, command, and arguments to enable reliable tool access within plugin workflows.

What MCP server transport types are supported for plugin integration?

Plugin integration supports four MCP server transport types: stdio, SSE, HTTP, and WebSocket. Each type allows external services to connect to Claude Code plugins and expose tools for discovery and execution.

How does tool discovery work for MCP-backed external services?

Tool discovery for MCP-backed services uses a specific naming convention where external tools are exposed as mcp__plugin_<plugin>_<server>__<tool>. You can verify available MCP servers and discovered tools using the /mcp command in debug mode.

Can I use OAuth or token-based authentication with MCP servers in plugins?

Yes, MCP server integration supports OAuth and token-based authentication schemes for plugins. The skill provides guidance on secure token storage and authentication best practices to manage tool access safely.

What's the best way to test an MCP server configuration in a Claude Code plugin?

The best way to test an MCP server configuration is to run Claude in debug mode using the --debug flag, then execute the /mcp command. This validates that the plugin root configuration correctly registers the server and discovers available tools.

How do I manage multiple MCP servers within a single Claude Code plugin?

You can manage multiple MCP servers within a single plugin by defining each server configuration in the plugin root .mcp.json or plugin.json file. This allows simultaneous integration of various external services like databases and cloud APIs.