MCP Integration

Connect external services via MCP and expose their tools to Claude Code.

Updated Jan 30, 2026

Search Tags:#authentication #oauth #mcp #claude-code #external-services #server-types #plugin-integration

Ready to run

npx skills add https://github.com/czambr/04-altura --skill mcp-integration-czambr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: MCP Integration
Source: https://github.com/czambr/04-altura/tree/main/.agents/skills/mcp-integration
Command: npx skills add https://github.com/czambr/04-altura --skill mcp-integration-czambr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

MCP integration enables Claude Code plugins to connect external services and expose their capabilities as tools, simplifying cross-service automation and tool orchestration.

Core Features & Use Cases

Support for all MCP server types (stdio, SSE, HTTP, WebSocket) to fit local, hosted, and API-based services.
Flexible configuration via .mcp.json at plugin root and optional per-server settings.
Automatic tool discovery and standardized naming (mcp__plugin_<plugin>_<server>__<tool>) for seamless command and agent usage.
Authentication patterns including OAuth (for SSE/HTTP) and token-based approaches, with secure token management.
Lifecycle management and error handling with practical examples and migration guidance.

Quick Start

Create a .mcp.json at your plugin root to configure one or more MCP servers, then verify available tools with the /mcp command.

Frequently Asked Questions about MCP Integration

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

FAQPage Schema

How do I connect an external API to Claude Code using MCP?▼

To connect an external API to Claude Code, you configure an MCP server within a `.mcp.json` file at your plugin root, which exposes the external service's capabilities as tools. The integration supports server types like SSE and HTTP to fit hosted or API-based services.

What authentication patterns are supported for MCP server integration?▼

MCP server integration supports OAuth for SSE and HTTP server types, alongside token-based approaches. It provides secure token management to authenticate external services and expose their tools to Claude Code safely.

How do I configure multiple MCP servers for a single Claude Code plugin?▼

You configure multiple MCP servers by defining them within the `.mcp.json` file at your plugin root, applying optional per-server settings. This multi-server pattern allows you to orchestrate cross-service automation and manage different external service connections simultaneously.

Does MCP integration support local stdio servers alongside hosted WebSocket connections?▼

Yes, MCP integration supports all server types including stdio, SSE, HTTP, and WebSocket. This allows you to fit local services using stdio alongside hosted or API-based services using WebSocket connections within the same plugin ecosystem.

How are MCP tools named when exposed to Claude Code commands and agents?▼

MCP tools are exposed using a standardized naming convention: `mcp__plugin_<plugin>_<server>__<tool>`. This automatic tool discovery and standardized naming ensures seamless command and agent usage within the Claude Code environment.

How do I troubleshoot MCP server connections that are not working in Claude Code?▼

When an MCP server connection is not working, you can verify available tools and server status using the `/mcp` command. The integration also provides lifecycle management and error handling with practical examples to diagnose connection issues.