mcp-integration

Configure Model Context Protocol servers for plugin integrations with external services.

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/AvaTar-ArTs/.Agent-skills --skill mcp-integration-avatar-arts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mcp-integration
Source: https://github.com/AvaTar-ArTs/.Agent-skills/tree/main/skills/mcp-integration
Command: npx skills add https://github.com/AvaTar-ArTs/.Agent-skills --skill mcp-integration-avatar-arts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Connecting plugins to external services and APIs requires correctly configuring MCP servers, handling authentication, and managing tool naming, which is error-prone without clear guidance. ## Core Features & Use Cases - Server Configuration: Set up MCP servers via dedicated .mcp.json files or inline mcpServers fields in plugin.json, with environment variable expansion for portable, secure configs. - Transport & Auth Coverage: Supports stdio, SSE, HTTP, and WebSocket server types with OAuth or token-based authentication patterns. - Use Case: When building a plugin that connects to GitHub and Jira, use this Skill to configure both SSE servers, pre-allow the specific MCP tools in command frontmatter, and validate the setup with the /mcp command. ## Quick Start Ask the AI to create an MCP server configuration in .mcp.json for your plugin using the appropriate server type and environment variables.

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 in a plugin?▼

Create a `.mcp.json` file at the plugin root defining the server with its command, args, and env fields, or add an `mcpServers` field inline in `plugin.json`. Use `${CLAUDE_PLUGIN_ROOT}` for portable paths and document required environment variables.

What MCP server types are available for plugins?▼

MCP supports four transport types: stdio for local child processes, SSE for hosted servers with OAuth, HTTP for REST APIs with token headers, and WebSocket for real-time bidirectional communication. Choose based on whether the server is local or hosted.

How does OAuth authentication work with MCP SSE servers?▼

OAuth is handled automatically for SSE servers: the user is prompted to authenticate in a browser on first use, and tokens are managed by the host environment. No manual token configuration is needed beyond specifying the server URL.

Why is my MCP server not connecting or tools not appearing?▼

Check that the server URL is correct, the server process is running for stdio types, and network connectivity works. Run the `/mcp` command to list available servers and tools, and use debug logging to inspect connection attempts and authentication flows.

Should I use wildcards when allowing MCP tools in commands?▼

No, pre-allowing specific MCP tools in command frontmatter is the recommended security practice. Wildcards like `mcp__plugin_server__*` grant broader access than necessary and should be used sparingly.