MCP Integration

Expose external services as MCP tools to Claude Code plugins.

Updated Dec 1, 2025
One-click install
npx skills add https://github.com/stevessr/dotsfiles --skill mcp-integration-stevessr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: MCP Integration
Source: https://github.com/stevessr/dotsfiles/tree/main/dot_claude/private_plugins/private_marketplaces/claude-code-plugins/plugins/plugin-dev/skills/mcp-integration
Command: npx skills add https://github.com/stevessr/dotsfiles --skill mcp-integration-stevessr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

MCP Integration enables Claude Code plugins to expose external services as MCP tools, bridging plugin functionality with external APIs and data sources.

Core Features & Use Cases

  • Expose external services as MCP tools within Claude Code for seamless automation.
  • Support all MCP server types (stdio, SSE, HTTP, ws) and lifecycle management for reliable tool discovery.
  • Provide robust authentication patterns (OAuth, tokens, dynamic headers) and secure token handling.
  • Enable per-plugin server bundles and automatic discovery via the /mcp command.

Quick Start

Create a .mcp.json at the plugin root and restart Claude Code to initialize MCP servers.

Frequently Asked Questions about MCP Integration

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

FAQPage Schema
How do I expose external APIs as MCP tools in Claude Code?

You expose external APIs as MCP tools by creating a `.mcp.json` file at your plugin root to configure server endpoints, then restarting Claude Code to initialize and discover the MCP servers automatically.

What authentication methods are supported for MCP server integrations?

MCP server integrations support OAuth, static tokens, and dynamic headers for secure authentication, ensuring robust token handling when bridging plugin workflows with external APIs and data sources.

Which MCP server types can I configure for tool discovery?

You can configure all standard MCP server types including stdio, SSE, HTTP, and ws, with full lifecycle management to ensure reliable tool discovery via the `/mcp` command.

Can I bundle specific MCP servers on a per-plugin basis?

Yes, you can enable per-plugin server bundles by defining your server configurations within the `.mcp.json` file, allowing each Claude Code plugin to securely manage its own external service integrations.

Why are my external services not showing up after adding an MCP configuration?

External services may not show up if Claude Code was not restarted after creating the `.mcp.json` file, as the initialization process requires a restart to load server configurations and execute tool discovery.

How do environment variables work with MCP server configurations?

Environment variables are enforced within MCP server configurations to securely manage credentials and runtime parameters, allowing external services to connect safely without exposing sensitive tokens directly in the codebase.