| name | mcp-ecosystem-optimizer |
| description | Review and optimize MCP server setup—inventory, registry hygiene, config, versioning, and observability. Use when managing multiple MCP servers in Cursor or Claude. Triggers: "MCP server", "MCP config", "MCP registry", "optimize MCP", "too many MCP tools". Use when this capability is needed. |
MCP Ecosystem Optimizer
Operational review of Model Context Protocol servers: what is installed, what is used, and how to reduce noise and risk. Complements mcp-builder (authoring servers) with consumer-side hygiene.
When to use
- Slow or cluttered agent tool lists
- Debugging MCP connection failures
- Onboarding team to shared MCP config
- Auditing third-party MCP servers before enable
When not to use
- Building a new MCP server (use
mcp-builder)
- General agent eval (use
agent-evaluation)
Workflow
- Inventory — list enabled servers, tools exposed, auth method
- Usage — which tools actually get called; disable unused servers
- Config — single source of truth (
.cursor/mcp.json or team template); no duplicated entries
- Versioning — pin server versions; document upgrade path
- Observability — log tool errors; note latency outliers
- Security — run
skill-supply-chain-audit mindset: network scope, credential storage
Optimization checklist
Anti-patterns
- Enabling every server from a registry "just in case"
- Storing API keys in committed config
- Platform-specific CLI wrappers that hide what tools run
Related skills
mcp-builder — implement serversagent-tool-contracts — tool schema designskill-supply-chain-audit — third-party trust review
Clean-room MCP operations workflow inspired by ecosystem management patterns.
Source: charlieviettq/awesome-agent-skill — distributed by TomeVault.
