retrieve_mcps
Performs retrieval from our registry of MCPs.
Find MCP servers by describing what you need — semantic search over an MCP registry, from inside your assistant.
LABSCO SUMMARY
Server names are not descriptive — nobody looking for a way to read PDFs searches for the package that does it. Matching on meaning is what makes "something that reads my calendar" return an answer. One tool and no credentials means it costs almost nothing to keep attached, and it is most useful in the moment you realise the assistant cannot do something yet.
A single-tool MCP server that searches an MCP registry semantically. You describe the capability you are after in ordinary words and it returns matching servers, so discovery happens in the client you are already using rather than by browsing a directory.
retrieve_mcpsNo account and no key. The npm package name is mcp-server-retriever (0.6.2); build from a clone with npm install and npm run build, confirm it starts with node ./dist/index.js, then point your client at that path — or install through Smithery.
One command — npx -y github:KBB99/mcp-registry-server
USE CASES
Describe what you want the assistant to be able to do and get back candidate servers, without leaving the conversation to search a directory.
Search the registry before writing your own server for a job someone has already solved.
Query broadly — search, databases, calendars — and read what the registry returns to see how many alternatives there are.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
retrieve_mcpsPerforms retrieval from our registry of MCPs.
BEFORE YOU INSTALL
1 tool when we connected.
npx on PATH
CONTEXT COST
Rated by the size of the one tool definition that rides along on every turn
INSTALLATION
Add the block to your client, or run the command directly.
{
"mcpServers": {
"mcp-registry-server": {
"command": "npx",
"args": [
"-y",
"github:KBB99/mcp-registry-server"
]
}
}
}npx -y github:KBB99/mcp-registry-server