MCP Integration

Automate MCP server integration for Claude Code plugins across stdio, SSE, HTTP, and WebSocket workflows.

2|Updated Aug 2, 2025
One-click install
npx skills add https://github.com/wssAchilles/Mycode --skill mcp-integration-wssachilles
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: MCP Integration
Source: https://github.com/wssAchilles/Mycode/tree/main/telegram/.agents/skills/mcp-integration
Command: npx skills add https://github.com/wssAchilles/Mycode --skill mcp-integration-wssachilles

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill guides developers in integrating Model Context Protocol (MCP) servers with Claude Code plugins, enabling external tool access, secure authentication, and seamless server configuration.

Core Features & Use Cases

  • Two configuration methods: Use a dedicated .mcp.json at plugin root or embed MCP server definitions in plugin.json.
  • Multi-type MCP support: Works with stdio, SSE, HTTP, and WebSocket MCP servers for local, hosted, and cloud services.
  • Tool discovery & authentication: Automates tool discovery via /mcp and supports OAuth and token-based authentication flows.
  • Use Case: Set up a plugin that leverages external services (databases, APIs) via MCP-enabled tools across multiple servers.

Quick Start

Configure MCP servers for your Claude Code plugin using either .mcp.json or plugin.json, then verify available tools with the /mcp command and start invoking tools as needed.

Frequently Asked Questions about MCP Integration

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

FAQPage Schema
How do I configure MCP servers for Claude Code plugins?

Configure MCP servers for Claude Code plugins using either a dedicated .mcp.json file at the plugin root or by embedding server definitions directly within plugin.json. Both methods support local, hosted, and cloud services across stdio, SSE, HTTP, and WebSocket workflows.

Can I use OAuth and token-based authentication for MCP server integration?

Yes, MCP server integration supports both OAuth and token-based authentication flows. It emphasizes environment-variable-based security practices to manage credentials safely when configuring access to external services like databases and APIs.

What is the best way to discover available tools after setting up an MCP server?

The best way to discover available tools after setting up an MCP server is to run the /mcp command. This automates tool discovery, allowing you to verify configured tools and start invoking them as needed within your Claude Code plugin.

Does MCP integration support multi-server orchestration?

Yes, MCP integration supports multi-server orchestration. You can configure multiple local, hosted, and REST MCP servers simultaneously, enabling your plugin to leverage external services and orchestrate tools across different server environments.

When should I use .mcp.json instead of plugin.json for server configuration?

Use .mcp.json when you prefer a dedicated configuration file at the plugin root for managing MCP servers. Alternatively, embed definitions in plugin.json to consolidate settings, with both supporting standard MCP patterns for stdio, SSE, HTTP, and WebSocket workflows.