mcp-integration

Configure Model Context Protocol servers for Claude Code plugins.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/jaimedhenriques/finsyt --skill mcp-integration-jaimedhenriques
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-integration
Source: https://github.com/jaimedhenriques/finsyt/tree/main/artifacts/platform/.agents/skills/mcp-integration
Command: npx skills add https://github.com/jaimedhenriques/finsyt --skill mcp-integration-jaimedhenriques

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill removes the friction of wiring external services into Claude Code plugins by providing a clear, reliable path for adding Model Context Protocol servers.

Core Features & Use Cases

  • Server Configuration: Set up MCP servers through either a dedicated .mcp.json file or inline plugin.json configuration.
  • Transport Support: Handle stdio, SSE, HTTP, and WebSocket server types for both local and hosted integrations.
  • Authentication and Safety: Use environment variables, OAuth, and token-based headers while keeping paths portable and access scoped.
  • Use Case: A plugin author can connect a hosted issue tracker, a local database tool, and a real-time service into one Claude workflow without rewriting the integration pattern each time.

Quick Start

Ask Claude to help you configure an MCP server for your plugin and generate the right .mcp.json or plugin.json setup for your chosen transport.

Frequently Asked Questions about mcp-integration

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

FAQPage Schema
How do I configure an MCP server for Claude Code plugins?

You can configure MCP servers for Claude Code plugins by defining your setup in a dedicated .mcp.json file or inline within plugin.json. This process handles transport types, environment variable expansion, and tool naming for reliable external tool access.

What transport types does Model Context Protocol support for Claude integrations?

Model Context Protocol integrations support stdio, SSE, HTTP, and WebSocket transport types. This enables developers to connect both local servers and hosted remote endpoints into a single Claude workflow.

Can I use OAuth and environment variables for MCP server authentication?

Yes, MCP server authentication supports environment variables, OAuth, and token-based headers. This approach keeps paths portable and access scoped while ensuring secure connectivity between Claude plugins and external services.

What is the best way to connect a local stdio server to a Claude workflow?

The best way to connect a local stdio server to a Claude workflow is by configuring the Model Context Protocol server through a .mcp.json file. This standardizes the plugin integration pattern for local tools and services.

Why is my MCP server configuration not working in Claude Code?

MCP server configuration issues in Claude Code often stem from incorrect .mcp.json setup, environment-variable expansion failures, or mismatched transport types. Troubleshooting tool naming and authentication patterns helps restore external tool access.