Agent skill · software engineering · secondsky
mcp-dynamic-orchestrator
Dynamic MCP server discovery and code-mode execution via central registry. Use for multiple MCP integrations, tool discovery, progressive disclosure, or encountering MCP context bloat, changing server sets, large tool sets.
Why this skill is useful
Adds executable TypeScript code generation for dynamic MCP server interactions that aren't covered in public documentation.
What it needs
Requires typescript installed locally. About 3k tokens when loaded. Last updated 2026-08-06. 204 stars on the source repository.
What this skill does
Overview Use this skill to: Discover which MCP servers are available and what they are for. Inspect a specific MCP's capabilities without loading all tool schemas. Execute TypeScript/JavaScript that calls MCP tools via generated mcp-clients/ modules. If no MCP servers are configured, listmcpcapabilities will respond with an empty list and a message pointing to skills/mcp-dynamic-orchestrator/mcp.registry.json so the user can add MCP entries. This skill reads from mcp.registry.json, so adding an MCP entry there (for example the Cloudflare MCP) automatically makes it discoverable without changing tool wiring. Cloudflare MCP example The Cloudflare MCP server can be configured in mcp.registry.json like this: With this entry present: listmcpcapabilities will return cloudflare when queries mention Cloudflare, Workers, KV, R2, Queues, etc. describemcp with id: "cloudflare" will surface concise tool summaries from the Cloudflare MCP server. executemcpcode lets the agent write TypeScript such as: The actual available functions under mcp-clients/cloudflare are generated dynamically from the MCP tool definitions; the agent should always: 1. Discover via listmcpcapabilities. 2. Inspect via describemcp to see available operations. 3. Use those operations via executemcpcode. How to use 1. Call listmcpcapabilities with a natural language query or filters to see which MCPs exist. 2. For a chosen MCP (e.g. cloudflare), call describemcp to understand its operations. 3. Write TypeScript/JavaScript that imports from mcp-clients/<id> and calls the exported functions. 4. Run your code with executemcpcode, optionally restricting allowedMcpIds for safety. Rules Do not assume individual MCP tools are top-level tools. Always: discover → describe → generate code → executemcpcode. Request detail: "schema" in describemcp only when exact parameter shapes are required. Known Limitations Sandbox Security (CRITICAL) ⚠️ The current sandbox implementation is NOT secure for untrusted code. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills secondsky/mcp-dynamic-orchestrator