AI powered automation toolkit which acts as an agent that discovers MCP servers for you. Point it at GitHub/npm/confi...
Copy the install, test the workflow, then decide if it earns a permanent slot.
Still active enough to matter. Good candidate for a fast stack test instead of a long evaluation loop.
Copy the install, test the workflow, then decide if it earns a permanent slot.
You can test this quickly and remove it cleanly if it misses.
GitHub health unknown. no security policy. 0 open issues make this testable, but not something to trust blind.
AI Agent
Cursor AI
Model
Claude
Fastest way to find out if lyra-tool-discovery belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
claude mcp add lyra-tool-discovery -- npx lyra-tool-discoveryRun this first. You will know quickly if the workflow earns a permanent slot.
claude mcp remove lyra-tool-discoveryNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude.json └─ mcp_servers/ └─ lyra-tool-discovery ← registers here
AI powered automation toolkit which acts as an agent that discovers MCP servers for you. Point it at GitHub/npm/configure your own discovery, let GPT or Claude analyze the API or MCP or any tool, get ready-to-ship plugin configs. Zero manual work.