Skill

mcp-integration

Guide for bundling MCP servers with plugins. Use when the user asks to "add MCP server", "integrate MCP", "external tools", ".mcp.json", or "Model Context Protocol".

From claude-plugin-dev

Install

Run in your terminal

npx claudepluginhub nthplusio/functional-claude --plugin claude-plugin-dev

Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Similar Skills

executing-plans

Executes pre-written implementation plans: critically reviews, follows bite-sized steps exactly, runs verifications, tracks progress with checkpoints, uses git worktrees, stops on blockers.

superpowers

134.2k

brainstorming

7 files

Guides idea refinement into designs: explores context, asks questions one-by-one, proposes approaches, presents sections for approval, writes/review specs before coding.

superpowers

134.2k

dispatching-parallel-agents

Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.

superpowers

134.2k

Stats

Parent Repo Stars1

Parent Repo Forks0

Last CommitMar 9, 2026

Actions

View Source View Plugin View on GitHub View README

.mcp.json Format

{ "server-name": { "command": "${CLAUDE_PLUGIN_ROOT}/servers/my-server", "args": ["--config", "${CLAUDE_PLUGIN_ROOT}/config.json"], "env": { "API_KEY": "${API_KEY}" } } }

Key conventions:

Use ${CLAUDE_PLUGIN_ROOT} for plugin-relative paths in command and args

Use ${ENV_VAR} syntax for secrets in env

stdio servers use command + args; remote servers use url

Inline Marketplace Pattern

For simple MCP servers, define directly in marketplace.json:

{ "name": "github", "source": "./external_plugins/github", "strict": false, "mcpServers": { "github": { "command": "npx", "args": ["-y", "@anthropic/github-mcp"] } } }

Note: strict: false is required when defining mcpServers inline.

MCP Integration

Guide for bundling MCP (Model Context Protocol) servers with plugins.

MCP Location

my-plugin/
├── .claude-plugin/
│   └── plugin.json
└── .mcp.json          # MCP server configs

.mcp.json Format

{
  "server-name": {
    "command": "${CLAUDE_PLUGIN_ROOT}/servers/my-server",
    "args": ["--config", "${CLAUDE_PLUGIN_ROOT}/config.json"],
    "env": {
      "API_KEY": "${API_KEY}"
    }
  }
}

Key conventions:

Use ${CLAUDE_PLUGIN_ROOT} for plugin-relative paths in command and args
Use ${ENV_VAR} syntax for secrets in env
stdio servers use command + args; remote servers use url

Inline Marketplace Pattern

For simple MCP servers, define directly in marketplace.json:

{
  "name": "github",
  "source": "./external_plugins/github",
  "strict": false,
  "mcpServers": {
    "github": {
      "command": "npx",
      "args": ["-y", "@anthropic/github-mcp"]
    }
  }
}

Note: strict: false is required when defining mcpServers inline.

Tool Naming Convention

MCP tools are namespaced: mcp__<server>__<tool>

Examples:

mcp__postgres__query
mcp__github__create_issue

Use in hook matchers:

{
  "matcher": "mcp__postgres__.*"
}

External Plugin Pattern

For wrapping third-party MCP servers as standalone plugins:

external_plugins/
└── service-name/
    ├── .claude-plugin/
    │   └── plugin.json
    └── .mcp.json

Document required environment variables in README.