Searching registries by keyword fails on exactly the queries that matter, which is why the recommendation side runs several providers at once and backs them with vector search over descriptions rather than titles. The second tool is the one that saves the afternoon: once a candidate is chosen, it returns the config for your client instead of leaving you to translate a README into JSON.
A discovery service for MCP servers. One tool takes a task description and returns candidate servers; the other takes a server name and source URL and returns the installation and configuration steps for a named client.
- recommend-mcp-servers takes a task description, with optional keywords and required capabilities, and returns each candidate's name, what it does, and its category
- install-mcp-server takes the server's name and source URL — a GitHub URL, for instance — and returns how to install and configure it, tailored to the client you name
- Several search providers queried in parallel and merged: the Compass and GetMCP registries, Meilisearch, a Nacos service-discovery provider, and an offline provider
- The offline provider combines text matching with vector search, so a description that shares no keywords with a server's README can still reach it
- Search options for result limit and minimum similarity, so a broad query and a precise one behave differently
- Configuration through environment variables or an .mcpadvisorrc.json file; the Nacos provider takes NACOS_SERVER_ADDR, with namespace, group and credentials optional, and LOG_DIR sets where logs land
No account and no key for the default setup — it runs as npx -y @xiaohui-wang/mcpadvisor. The Nacos provider is the exception: it needs NACOS_SERVER_ADDR, plus NACOS_USERNAME and NACOS_PASSWORD where that Nacos instance requires authentication. MIT.
One command — npx -y @xiaohui-wang/mcpadvisor