agentleFS
captain-corgicaptain-corgi/marketplace-website/.claude/skills/mcp-management/SKILL.md

mcp-management

Skill0 starsChanged 11 months agoMITView on GitHub

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.

  • Installs packages

12 other projects use a version of this, 8 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use ads-management, ai-artist and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • OpenAnalystIncSkill

    ads-management

    Activate for paid advertising campaigns on Google Ads, Meta Ads, LinkedIn Ads, TikTok Ads. Includes ad copywriting, audience targeting, budget optimization, A/B testing, and ROAS tracking. Used by ads-specialist and campaign-manager agents.

    Also in 3 projects that use this

  • OpenAnalystIncSkill

    ai-artist

    Write and optimize prompts for AI-generated outcomes across text and image models. Use when crafting prompts for LLMs (Claude, GPT, Gemini), image generators (Midjourney, DALL-E, Stable Diffusion, Imagen, Flux), or video generators (Veo, Runway). Covers prompt structure, style keywords, negative prompts, chain-of-thought, few-shot examples, iterative refinement, and domain-specific patterns for marketing, code, and creative writing.

    Also in 3 projects that use this

  • sumuligeSkill

    seo-optimization

    SEO best practices for Git, documentation, and web projects

    Also in 3 projects that use this

  • claude-office-skillsSkill

    email-marketing

    Email marketing automation - campaign creation, sequence building, A/B testing, deliverability optimization, and analytics

    Also in 3 projects that use this

  • +6 more from OpenAnalystInc

The file

We split this skill into the rules it gives an agent

8 rules. 4 are common, 2 are distinctive, and 2 are very specific to this project.

  • 4

    Common

    Most of the 9 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Use this skill when:

    line 23
  2. Distinctive:

    Use Gemini CLI for automatic tool discovery and execution.

    line 91
  3. Distinctive:

    No natural language ambiguity

    line 110
  4. Very specific:

    Use mcp-manager agent when Gemini CLI unavailable.

    line 116
  5. Very specific:

    IMPORTANT: Use stdin piping, NOT -p flag (deprecated, skips MCP init)

    line 189
  6. Common:

    Use when: Need specific tool/server control

    line 193
  7. Common:

    Use when: Gemini unavailable or failed

    line 197
  8. Common:

    Check Gemini CLI availability first

    line 203

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

MCP Management

Skill for managing and interacting with Model Context Protocol (MCP) servers.

Overview

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:

  • Progressive disclosure of MCP capabilities (load only what's needed)
  • Intelligent tool/prompt/resource selection based on task requirements
  • Multi-server management from single config file
  • Context-efficient: subagents handle MCP discovery and execution
  • Persistent tool catalog: automatically saves discovered tools to JSON for fast reference

When to Use This Skill

Use this skill when:

  1. Discovering MCP Capabilities: Need to list available tools/prompts/resources from configured servers
  2. Task-Based Tool Selection: Analyzing which MCP tools are relevant for a specific task
  3. Executing MCP Tools: Calling MCP tools programmatically with proper parameter handling
  4. MCP Integration: Building or debugging MCP client implementations
  5. Context Management: Avoiding context pollution by delegating MCP operations to subagents

Core Capabilities

1. Configuration Management

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.

GEMINI.md Response Format: Project root contains GEMINI.md that Gemini CLI auto-loads, enforcing structured JSON responses:

{"server":"name","tool":"name","success":true,"result":<data>,"error":null}

This ensures parseable, consistent output instead of unpredictable natural language. The file defines:

  • Mandatory JSON-only response format (no markdown, no explanations)
  • Maximum 500 character responses
  • Error handling structure
  • Available MCP servers reference

Benefits: Programmatically parseable output, consistent error reporting, DRY configuration (format defined once), context-efficient (auto-loaded by Gemini CLI).

2. Capability Discovery

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.

3. Intelligent Tool Analysis

LLM analyzes assets/tools.json directly - better than keyword matching algorithms.

4. Tool Execution

Primary: Gemini CLI (if available)

# IMPORTANT: Use stdin piping, NOT -p flag (deprecated, skips MCP init)
echo "Take a screenshot of https://example.com" | gemini -y -m gemini-2.5-flash

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.

Implementation Patterns

Pattern 1: Gemini CLI Auto-Execution (Primary)

Use Gemini CLI for automatic tool discovery and execution. Gemini CLI auto-loads GEMINI.md from project root to enforce structured JSON responses.

Quick Example:

# IMPORTANT: Use stdin piping, NOT -p flag (deprecated, skips MCP init)
# Add "Return JSON only per GEMINI.md instructions" to enforce structured output
echo "Take a screenshot of https://example.com. Return JSON only per GEMINI.md instructions." | gemini -y -m gemini-2.5-flash

Expected Output:

{"server":"puppeteer","tool":"screenshot","success":true,"result":"screenshot.png","error":null}

Benefits:

  • Automatic tool discovery
  • Structured JSON responses (parseable by Claude)
  • GEMINI.md auto-loaded for consistent formatting
  • Faster than subagent orchestration
  • No natural language ambiguity

See references/gemini-cli-integration.md for complete guide.

Pattern 2: Subagent-Based Execution (Fallback)

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.

Pattern 3: LLM-Driven Tool Selection

LLM reads assets/tools.json, intelligently selects relevant tools using context understanding, synonyms, and intent recognition.

Pattern 4: Multi-Server Orchestration

Coordinate tools across multiple servers. Each tool knows its source server for proper routing.

Scripts Reference

scripts/mcp-client.ts

Core MCP client manager class. Handles:

  • Config loading from .claude/.mcp.json
  • Connecting to multiple MCP servers
  • Listing tools/prompts/resources across all servers
  • Executing tools with proper error handling
  • Connection lifecycle management

scripts/cli.ts

Command-line interface for MCP operations. Commands:

  • list-tools - Display all tools and save to assets/tools.json
  • list-prompts - Display all prompts
  • list-resources - Display all resources
  • call-tool <server> <tool> <json> - Execute a tool

Note: list-tools persists complete tool catalog to assets/tools.json with full schemas for fast reference, offline browsing, and version control.

Quick Start

Method 1: Gemini CLI (recommended)

npm install -g gemini-cli
mkdir -p .gemini && ln -sf .claude/.mcp.json .gemini/settings.json
# IMPORTANT: Use stdin piping, NOT -p flag (deprecated, skips MCP init)
# GEMINI.md auto-loads to enforce JSON responses
echo "Take a screenshot of https://example.com. Return JSON only per GEMINI.md instructions." | gemini -y -m gemini-2.5-flash

Returns structured JSON: {"server":"puppeteer","tool":"screenshot","success":true,"result":"screenshot.png","error":null}

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.

Technical Details

See references/mcp-protocol.md for:

  • JSON-RPC protocol details
  • Message types and formats
  • Error codes and handling
  • Transport mechanisms (stdio, HTTP+SSE)
  • Best practices

Integration Strategy

Execution Priority

  1. Gemini CLI (Primary): Fast, automatic, intelligent tool selection
    • Check: command -v gemini
    • Execute: echo "<task>" | gemini -y -m gemini-2.5-flash
    • IMPORTANT: Use stdin piping, NOT -p flag (deprecated, skips MCP init)
    • Best for: All tasks when available
  2. Direct CLI Scripts (Secondary): Manual tool specification
    • Use when: Need specific tool/server control
    • Execute: npx tsx scripts/cli.ts call-tool <server> <tool> <args>
  3. mcp-manager Subagent (Fallback): Context-efficient delegation
    • Use when: Gemini unavailable or failed
    • Keeps main context clean

Integration with Agents

The mcp-manager agent uses this skill to:

  • Check Gemini CLI availability first
  • Execute via gemini command if available
  • Fallback to direct script execution
  • Discover MCP capabilities without loading into main context
  • Report results back to main agent

This keeps main agent context clean and enables efficient MCP integration.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.