What problem does it solve? MCP servers expose dozens of tools whose definitions bloat the system prompt and cause agents to pick the wrong tool. This Skill maintains a machine-readable index (.ai-badger/mcp-tools.json) mapping every MCP tool to tags and intent descriptions, feeding a hook that injects only relevant tool recommendations into each LLM turn. ## Core Features & Use Cases - Index lifecycle commands: init, update, validate, tag, intent, list, and migrate commands manage the JSON index, preserving manually curated tags across updates. - Multi-source server discovery: Queries hermes and claude CLIs in a fallback chain, with optional --discover per-server enumeration and catalog-based seeding for servers the host cannot enumerate. - Hook-driven recommendations: A UserPromptSubmit hook ranks indexed tools via BM25 against each prompt and injects top matches as additional context. - Use Case: After adding a new MCP server, run mcp-index update so its tools are tagged, described, and recommended on relevant prompts instead of bloating every turn. ## Quick Start Ask the agent to run mcp-index init against your project root to build the MCP tool index, then curate any tools left tagged as general.