mcp-management

Orchestrate MCP tools, prompts, and resources across configured servers via CLI.

Updated Jan 31, 2026

Search Tags:#cli #mcp #multi-server #context-management #model-context-protocol #tool-discovery

Ready to run

npx skills add https://github.com/luan-thnh/hrm-auto-extension --skill mcp-management-luan-thnh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mcp-management
Source: https://github.com/luan-thnh/hrm-auto-extension/tree/main/.opencode/skills/mcp-management
Command: npx skills add https://github.com/luan-thnh/hrm-auto-extension --skill mcp-management-luan-thnh

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Efficiently orchestrate MCP capabilities across configured servers while keeping the main task context clean.

Core Features & Use Cases

Centralized multi-server management from a single config to discover, analyze, and execute MCP tools, prompts, and resources.
Progressive disclosure and context-efficient loading to bring in only what is needed for each task.
CLI-driven workflows to list tools/prompts/resources and execute tools across servers with robust error handling and fallbacks.

Quick Start

Configure MCP servers in .opencode/.mcp.json and run the CLI to list tools and begin using capabilities.

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 cluttering the main context?▼

To manage multiple MCP servers without cluttering context, use a centralized configuration to orchestrate capabilities. This approach enables progressive disclosure and on-demand loading, ensuring only the necessary tools, prompts, and resources are brought in per task.

How does tool discovery work for the Model Context Protocol?▼

Tool discovery for the Model Context Protocol works through a centralized configuration that lists available servers. A CLI workflow then programmatically discovers, analyzes, and executes available MCP tools, prompts, and resources across those configured servers.

Can I execute MCP tools programmatically across different servers?▼

Yes, you can execute MCP tools programmatically across different servers. A centralized orchestration layer distributes capabilities and invokes tools via a CLI workflow, complete with robust error handling and fallbacks for reliable execution.

Do I need the @modelcontextprotocol/sdk to orchestrate MCP capabilities?▼

Yes, the @modelcontextprotocol/sdk is required as a dependency. It provides the foundational components needed to distribute and orchestrate MCP capabilities, enabling intelligent analysis and programmatic execution from a single configuration.

What is the best way to list and invoke MCP resources from a single config?▼

The best way to list and invoke MCP resources from a single config is using a CLI-driven workflow. This method allows you to efficiently discover, analyze, and execute tools, prompts, and resources across multi-server environments while keeping context clean.

When should I use centralized multi-server MCP management?▼

Use centralized multi-server MCP management when orchestrating capabilities across configured servers to keep the main task context clean. It is ideal for scenarios requiring on-demand tool loading, progressive disclosure, and robust error handling during execution.