mcp-management

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

Updated Dec 16, 2025
One-click install
npx skills add https://github.com/nguyenvanlinh1902/trackingSolar --skill mcp-management-nguyenvanlinh1902
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-management
Source: https://github.com/nguyenvanlinh1902/trackingSolar/tree/main/.opencode/skill/mcp-management
Command: npx skills add https://github.com/nguyenvanlinh1902/trackingSolar --skill mcp-management-nguyenvanlinh1902

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

MCP management solves the challenge of coordinating multiple external MCP servers by enabling centralized discovery, intelligent tool selection, and safe execution without polluting the main context.

Core Features & Use Cases

  • Multi-server discovery and management
  • Intelligent tool, prompt, and resource analysis
  • Context-efficient execution via subagents and gated loading
  • Persistent tool catalog: automatically saves discovered tools to JSON for fast reference

Quick Start

Install dependencies, configure MCP servers in .opencode/.mcp.json, and run the MCP management CLI to list tools.

Frequently Asked Questions about 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?

You can manage multiple MCP servers without polluting the main context by using centralized discovery and subagent execution to orchestrate external tools safely. This approach filters prompts and resources intelligently across servers.

What is MCP server discovery and tool orchestration?

MCP server discovery and tool orchestration is the process of analyzing cross-server capabilities and executing tools deterministically via a dedicated CLI. It enables intelligent tool selection while keeping external tooling out of the main context.

How do I configure and list tools for multiple MCP servers?

To list tools across multiple MCP servers, install dependencies, configure your servers in the .opencode/.mcp.json file, and run the MCP management CLI. This generates a persistent tools.json catalog for fast reference.

Does MCP management work with the @modelcontextprotocol/sdk?

Yes, MCP management works with the @modelcontextprotocol/sdk as its core dependency. It leverages this SDK to enable cross-server capability discovery, intelligent resource filtering, and deterministic tool execution.

Why does my MCP tool execution fail during multi-server interactions?

MCP tool execution may fail during multi-server interactions if your .opencode/.mcp.json configuration is invalid or the assets/tools.json catalog is missing. The system requires robust error handling and a maintained configuration to execute successfully.

What's the best way to keep external MCP tooling out of the main context?

The best way to keep external MCP tooling out of the main context is to use gated loading and optional subagent flows for context-efficient execution. This approach ensures only necessary tool capabilities are loaded into the active context.