MCP Integration

Configure MCP servers for Claude Code plugins via .mcp.json or plugin.json.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/dostos/agent-workspace --skill mcp-integration-dostos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: MCP Integration
Source: https://github.com/dostos/agent-workspace/tree/main/.claude/skills/mcp-integration
Command: npx skills add https://github.com/dostos/agent-workspace --skill mcp-integration-dostos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill guides developers to connect external MCP servers to Claude Code plugins, enabling a scalable, secure tool interface and automation across services.

Core Features & Use Cases

  • Model Context Protocol (MCP) enables Claude Code plugins to expose external services as tools with consistent schemas.
  • Provide guidance for configuring MCP servers in plugin deployments via a dedicated .mcp.json or plugin.json fields.
  • Support for MCP server types: stdio, SSE, HTTP, and WebSocket, with environment-variable expansion and security considerations.
  • Practical patterns for using MCP tools in commands and agents, plus testing and debugging guidance.

Quick Start

  1. Choose an MCP server type and add its configuration to your plugin:
  • For dedicated config: create a .mcp.json at the plugin root; or
  • For inline config: add an mcpServers field to plugin.json.
  1. Use /mcp to discover available MCP tools, then start calling tools in your commands or agents.

Frequently Asked Questions about MCP Integration

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

FAQPage Schema
How do I connect external services to Claude Code plugins using MCP servers?

MCP Integration bridges external services into Claude Code plugins by exposing MCP servers as tools. Configure your plugin with a .mcp.json or mcpServers field in plugin.json, supporting stdio, SSE, HTTP, and WebSocket server types. Use /mcp to discover tools and call them directly in commands and agents.

What MCP server types does Claude Code support?

Claude Code supports four MCP server types: stdio for local processes, SSE for server-sent events, HTTP for REST endpoints, and WebSocket for bidirectional communication. Each type handles environment-variable expansion and secure token-based authentication for external service integration.

How do I handle authentication when integrating OAuth and token-based services with MCP?

MCP Integration provides secure token handling through environment-variable expansion in your .mcp.json or plugin.json configuration. Store OAuth credentials and API tokens as environment variables, reference them in your server configuration, and the Skill manages automated token lifecycle and secure tool exposure.

Can I use MCP servers from multiple external services in a single Claude Code plugin?

Yes, MCP Integration supports tool discovery and management across multiple services within one plugin. Configure multiple MCP servers in your plugin.json or .mcp.json, and the Skill handles standardized tool naming, automated server lifecycle management, and consistent schema exposure across all services.

What's the best way to test and debug MCP tools in Claude Code plugins?

Use the /mcp command to discover available tools and inspect their schemas before calling them. MCP Integration provides debugging guidance for stdio, SSE, HTTP, and WebSocket servers, plus patterns for testing tool discovery and automated lifecycle management within your plugin packaging.

Do I need to manually manage MCP server lifecycle in Claude Code plugins?

No, MCP Integration handles automated server lifecycle management. Configure your MCP servers in plugin.json or .mcp.json with the appropriate server type, and the Skill manages startup, shutdown, and connection handling for stdio, SSE, HTTP, and WebSocket servers.