mcp-integration

Configure MCP servers with stdio, SSE, HTTP, or WebSocket transports.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/sjnims/plugin-dev --skill mcp-integration-sjnims
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-integration
Source: https://github.com/sjnims/plugin-dev/tree/main/plugins/plugin-dev/skills/mcp-integration
Command: npx skills add https://github.com/sjnims/plugin-dev --skill mcp-integration-sjnims

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and examples (resource) components.

What problem does it solve?

Integrating Claude Code plugins with external APIs and services can be complex, requiring custom authentication, tool definition, and lifecycle management. This Skill simplifies the process, enabling seamless connection to any external system and expanding Claude's capabilities.

Core Features & Use Cases

  • Seamless External Connectivity: Integrate with databases, APIs, and file systems using stdio, SSE, HTTP, or WebSocket MCP servers, tailored to your service's needs.
  • Automated Authentication: Leverage OAuth, token-based, or environment variable authentication patterns for secure and hassle-free access to external resources.
  • Tool Exposure & Usage: Expose external service capabilities as structured tools within Claude Code, making them directly usable by your commands and agents for powerful workflows.
  • Use Case: You need to connect your Claude plugin to a proprietary internal REST API. Use this Skill to configure an HTTP MCP server, handle token-based authentication, and expose your API endpoints as Claude tools for automated data retrieval and manipulation.

Quick Start

Explain how to configure a new stdio MCP server in your plugin's .mcp.json to allow file system access, using ${CLAUDE_PLUGIN_ROOT} for portability.

Frequently Asked Questions about mcp-integration

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

FAQPage Schema
How do I integrate external APIs and services into Claude Code plugins?

Use MCP (Model Context Protocol) servers to integrate external services into Claude Code plugins. Configure stdio, SSE, HTTP, or WebSocket MCP servers in your plugin's .mcp.json file, set up authentication via OAuth or token-based methods, and expose API endpoints as structured tools for Claude to use directly.

What authentication methods does MCP support for connecting to external services?

MCP supports OAuth, token-based authentication, and environment variable expansion for secure access to external resources. Store sensitive credentials securely and use environment variables with ${VARIABLE_NAME} syntax in configuration files for portability across deployments.

How do I configure an MCP server to access file systems or databases?

Configure a stdio MCP server in .mcp.json with the service executable path and authentication credentials. Use ${CLAUDE_PLUGIN_ROOT} for portable file system paths, define tool schemas to expose database queries or file operations, and manage server lifecycle through the plugin's initialization process.

Can I use MCP with both command-line and agent-based workflows in Claude?

Yes, MCP-exposed tools work seamlessly in both Claude Code commands and agents. Once configured and authenticated, external service capabilities are available as structured tools that agents can invoke automatically or that commands can use explicitly for data retrieval and manipulation.

What's the difference between stdio, SSE, HTTP, and WebSocket MCP servers?

Stdio MCP servers run as local processes and communicate via standard input/output, ideal for file system access. SSE, HTTP, and WebSocket servers run remotely or locally as network services, enabling real-time bidirectional communication for APIs, databases, and external platforms at scale.

Do I need custom code to expose external API endpoints as Claude tools?

MCP handles tool exposure automatically. Define tool schemas in your .mcp.json or plugin configuration that map external API endpoints to structured tools, including parameters and response handling. Authentication and header management are configured declaratively, eliminating custom tool-wrapping code.