mcp-integration_skill

This skill helps you connect MCP servers to Claude Code plugins to expose external service capabilities as tools.

JavaScript

0

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill s-hiraoku/harnesses-factory --skill mcp-integration

SKILL.md2.2 KB

Overview

This skill guides connecting MCP (Model Context Protocol) servers to Claude Code plugins so external services can be exposed as tools. It provides configuration patterns, supported transport types, and practical steps for secure, portable integration. Use it when you need to run local processes or call remote MCP endpoints from a Claude plugin. The guidance focuses on reproducible configuration and safe authentication handling.

How this skill works

The skill describes two configuration methods: a dedicated .mcp.json file (recommended) or inline mcpServers inside plugin.json. It explains supported server types — stdio (local process), http (REST), sse (server-sent events), and websocket — and how to reference environment variables with ${VAR_NAME}. It also covers portability tokens like ${CLAUDE_PLUGIN_ROOT} and commands for local testing and status checks.

When to use it

When wiring a local helper process as an MCP server using stdio.
When calling a remote MCP endpoint over HTTPS, SSE, or WebSocket.
When you must keep keys or tokens out of source code via environment variables.
When packaging a plugin that needs relative paths to bundled server code.
When validating MCP connectivity and tool permission configuration before deployment.

Best practices

Prefer a dedicated .mcp.json for clear separation of server settings and to simplify CI/CD.
Always use HTTPS/WSS for remote servers; never expose plain HTTP endpoints.
Inject secrets via environment variables and avoid hardcoding tokens in config files.
Limit tool permissions and pre-allow only specific capabilities; avoid wildcard grants.
Document required environment variables and startup commands for reproducibility.

Example use cases

Run a local node-based adapter as a stdio MCP server to expose a database query tool.
Connect to a third-party REST-to-MCP gateway using an http type with Bearer token auth.
Stream events from an external service to the plugin via an sse MCP server for live updates.
Host a long-lived WebSocket MCP server for bidirectional telemetry or control flows.
Package a plugin with a bundled server and use ${CLAUDE_PLUGIN_ROOT} to resolve the entry point.

FAQ

Use a dedicated .mcp.json for clarity and easier environment-specific overrides; inline settings are acceptable for very small plugins or examples.

How do I pass secrets securely to MCP servers?

Reference secrets with ${VAR_NAME} and set those environment variables in your deployment environment or CI secrets store; never commit secrets to source control.