mcp-integration

Configure Model Context Protocol servers in Claude Code plugins for external service integration.

1|Updated Jul 6, 2015
One-click install
npx skills add https://github.com/ksolomon/dotfiles --skill mcp-integration-ksolomon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mcp-integration
Source: https://github.com/ksolomon/dotfiles/tree/main/AI/.claude/plugins/marketplaces/claude-plugins-official/plugins/plugin-dev/skills/mcp-integration
Command: npx skills add https://github.com/ksolomon/dotfiles --skill mcp-integration-ksolomon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Connecting Claude Code plugins to external services like databases, APIs, and cloud tools requires correctly configuring MCP servers, choosing the right transport type, and handling authentication—tasks that are error-prone without clear guidance. ## Core Features & Use Cases - MCP Server Configuration: Set up servers via a dedicated .mcp.json file or inline in plugin.json, using ${CLAUDE_PLUGIN_ROOT} for portable paths. - Four Transport Types: Configure stdio servers for local processes, SSE for hosted services with OAuth, HTTP for REST APIs with token auth, and WebSocket for real-time communication. - Authentication & Security Patterns: Handle OAuth flows, bearer tokens, environment variables, and dynamic headers while following security best practices. - Use Case: You want your plugin to create Asana tasks. Add an SSE server entry pointing to https://mcp.asana.com/sse in .mcp.json, then pre-allow the generated mcp__plugin_asana_asana__asana_create_task tool in your command frontmatter. ## Quick Start Add an MCP server to my plugin that connects to the Asana hosted service and pre-allow its task creation tool in my command.

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?▼

Create a .mcp.json file at the plugin root defining the server with its command or URL, or add an mcpServers field to plugin.json. Use ${CLAUDE_PLUGIN_ROOT} for file paths so the configuration stays portable across machines.

What MCP server type should I use for my plugin?▼

Use stdio for local tools and custom servers, SSE for hosted cloud services with OAuth, HTTP for REST APIs with token authentication, and WebSocket for real-time bidirectional communication. The choice depends on where the server runs and its auth model.

How does OAuth authentication work with MCP servers?▼

Claude Code handles the full OAuth 2.0 flow automatically for SSE and HTTP servers. On first tool use, the user is prompted to authorize in a browser, and tokens are stored and refreshed by Claude Code without extra configuration.

Why is my MCP server not connecting in Claude Code?▼

Check that the URL or command path is correct, verify required environment variables are set, and run claude --debug to inspect connection logs. Use the /mcp command to confirm the server appears and restart Claude Code after configuration changes.

How do I allow MCP tools in a plugin command?▼

List the full tool names in the command's allowed-tools frontmatter, using the format mcp__plugin_<plugin-name>_<server-name>__<tool-name>. Pre-allow specific tools rather than wildcards for better security.