ck:mcp-management

Discover, analyze, and execute MCP server capabilities across multiple servers.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/EdgeHunt/EdgeHunt --skill ck-mcp-management-edgehunt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:mcp-management
Source: https://github.com/EdgeHunt/EdgeHunt/tree/main/.claude/skills/mcp-management
Command: npx skills add https://github.com/EdgeHunt/EdgeHunt --skill ck-mcp-management-edgehunt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @modelcontextprotocol/sdk, and includes scripts (resource) and references (resource) components.

What problem does it solve?

MCP management across multiple servers is streamlined: discover, analyze, and execute capabilities without polluting the main context.

Core Features & Use Cases

  • Multi-server discovery and management of MCP capabilities from a single config
  • Intelligent tool/prompt/resource selection based on task requirements
  • Context-efficient: delegate MCP operations to subagents and persist a tool catalog to assets/tools.json

Quick Start

Configure MCP servers in .claude/.mcp.json and run the MCP CLI (scripts/cli.ts) to list tools and build the catalog.

Frequently Asked Questions about ck:mcp-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage multiple MCP servers without polluting the main context?

To manage multiple MCP servers without polluting the main context, delegate discovery and execution operations to subagents. This approach orchestrates capabilities across servers while keeping the primary context clean and efficient.

How do I discover and list tools across multiple MCP servers?

To discover and list tools across multiple MCP servers, configure your servers in a .claude/.mcp.json file and run the MCP CLI. This process executes list-tools operations and persists a comprehensive tools catalog to assets/tools.json.

Does MCP server orchestration require a specific configuration format?

MCP server orchestration requires a valid .claude/.mcp.json configuration file. This file defines the multiple servers to be managed, enabling the CLI to discover, analyze, and execute capabilities across the specified instances.

Can I execute prompts and resources via the MCP CLI alongside tool calls?

Yes, you can execute prompts and resources via the MCP CLI. The CLI supports list-tools, list-prompts, list-resources, and call-tool operations, allowing intelligent selection and execution of capabilities based on task requirements.

What is the best way to build a persistent catalog of MCP server tools?

The best way to build a persistent catalog of MCP server tools is to run the MCP CLI script against your .mcp.json configuration. This automatically discovers capabilities across servers and persists the output to assets/tools.json.

Why does MCP integration require subagents for tool selection?

MCP integration requires subagents for tool selection to maintain context efficiency. Delegating multi-server discovery, analysis, and execution to subagents prevents large tool definitions from overwhelming the main processing context.