Manage Model Context Protocol (MCP) servers - discover, analyze, and execute tools/prompts/resources from configured MCP servers. Use when working with MCP integrations, need to discover available MCP capabilities, filter MCP tools for specific tasks, execute MCP tools programmatically, access MCP prompts/resources, or implement MCP client functionality. Supports intelligent tool selection, multi-server management, and context-efficient capability discovery.
npx skills add https://github.com/mrgoonie/claudekit-skills --skill mcp-management
Skill for managing and interacting with Model Context Protocol (MCP) servers.
MCP is an open protocol enabling AI agents to connect to external tools and data sources. This skill provides scripts and utilities to discover, analyze, and execute MCP capabilities from configured servers without polluting the main context window.
Key Benefits:
Use this skill when:
MCP servers configured in .claude/.mcp.json.
Gemini CLI Integration (recommended): Create symlink to .gemini/settings.json:
mkdir -p .gemini && ln -sf .claude/.mcp.json .gemini/settings.json
See references/configuration.md and references/gemini-cli-integration.md.
npx tsx scripts/cli.ts list-tools # Saves to assets/tools.json
npx tsx scripts/cli.ts list-prompts
npx tsx scripts/cli.ts list-resources
Aggregates capabilities from multiple servers with server identification.
LLM analyzes assets/tools.json directly - better than keyword matching algorithms.
Primary: Gemini CLI (if available)
gemini -y -m gemini-2.5-flash -p "Take a screenshot of https://example.com"
Secondary: Direct Scripts
npx tsx scripts/cli.ts call-tool memory create_entities '{"entities":[...]}'
Fallback: mcp-manager Subagent
See references/gemini-cli-integration.md for complete examples.
Use Gemini CLI for automatic tool discovery and execution. See references/gemini-cli-integration.md for complete guide.
Quick Example:
gemini -y -m gemini-2.5-flash -p "Take a screenshot of https://example.com"
Benefits: Automatic tool discovery, natural language execution, faster than subagent orchestration.
Use mcp-manager agent when Gemini CLI unavailable. Subagent discovers tools, selects relevant ones, executes tasks, reports back.
Benefit: Main context stays clean, only relevant tool definitions loaded when needed.
LLM reads assets/tools.json, intelligently selects relevant tools using context understanding, synonyms, and intent recognition.
Coordinate tools across multiple servers. Each tool knows its source server for proper routing.
Core MCP client manager class. Handles:
.claude/.mcp.jsonCommand-line interface for MCP operations. Commands:
list-tools - Display all tools and save to assets/tools.jsonlist-prompts - Display all promptslist-resources - Display all resourcescall-tool <server> <tool> <json> - Execute a toolNote: list-tools persists complete tool catalog to assets/tools.json with full schemas for fast reference, offline browsing, and version control.
Method 1: Gemini CLI (recommended)
npm install -g gemini-cli
mkdir -p .gemini && ln -sf .claude/.mcp.json .gemini/settings.json
gemini -y -m gemini-2.5-flash -p "Take a screenshot of https://example.com"
Method 2: Scripts
cd .claude/skills/mcp-management/scripts && npm install
npx tsx cli.ts list-tools # Saves to assets/tools.json
npx tsx cli.ts call-tool memory create_entities '{"entities":[...]}'
Method 3: mcp-manager Subagent
See references/gemini-cli-integration.md for complete guide.
See references/mcp-protocol.md for:
command -v geminigemini -y -m gemini-2.5-flash -p "<task>"npx tsx scripts/cli.ts call-tool <server> <tool> <args>The mcp-manager agent uses this skill to:
gemini command if availableThis keeps main agent context clean and enables efficient MCP integration.
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Replace with description of the skill and when Claude should use it.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Take mrgoonie/mcp-management from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.
The instructions reference npm, npx.
Without those the skill loads but fails at the first command.