semantic_search_toolsLABSCO SUMMARY
The point is run_functions_code — data moves between tools without passing through the model.
Fetch a document and write it into another system as code, and the content is a variable in memory rather than something serialized into context twice. The three discovery tools in front of it are deliberately graduated: names first, semantic search when the names are not clear, and full schemas only for the tools you actually picked.
What it is
A meta-server that connects to your MCP servers and re-exposes them through four tools: three for graduated discovery, and one that runs JavaScript calling the underlying tools directly.
What you get
- get_mcps_servers_overview — tool names only, across every connected server, with no schemas loaded
- semantic_search_tools — describe the task in plain English and get ranked matches with similarity scores
- get_tools_overview — full definitions for just the tools you name, with parameter schemas and example usage
- run_functions_code — code that calls several tools in sequence or parallel, keeps intermediate data in memory, and returns only the final result
- Tool metadata and analyzed output schemas persisted across sessions
Requirements
Node.js with npm or yarn, plus the MCP servers you want to aggregate. The README's run line names @dbestai/mcp-of-mcps, which npm does not have; the server list is passed inline with --config or as a file with --config-file. Version 3.1.0.
Setup effort
Build from source — git clone https://github.com/eliavamar/mcp-of-mcps.git
USE CASES
01
Moving a large document between two services
Read it and write it in one code block; only the final result reaches the model.
02
Finding a tool when you do not know its name
Describe the intent and get ranked matches with their server and path.
03
Keeping schemas out of the context until they are needed
Scan names first, then load definitions for the two tools you settled on.
04
Running a multi-step workflow in one call
Compose the whole sequence, including error handling, and return once.
4 tools
Listed in project docs. Your client may show a different list.
get_mcps_servers_overviewget_tools_overviewrun_functions_codeBEFORE YOU INSTALL
What to know first
Tools you get
4 tools named in the project's documentation.
Requires
Node.js and npm
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/eliavamar/mcp-of-mcps.git
cd mcp-of-mcps
npm install
npm run buildCreate a config.json listing the MCP servers to aggregate: a JSON array of {"name", "command", "args"} entries, for example [{"name":"time","command":"uvx","args":["mcp-server-time"]}]
Add the server to your client. This is the README's Cline block, pointed at build/index.js in your clone instead of the npm package @dbestai/mcp-of-mcps, which the npm registry does not have:
MCP Clients
Cline
CLINE · JSON
{
"mcpServers": {
"mcp-of-mcps": {
"autoApprove": [],
"disabled": false,
"timeout": 60,
"type": "stdio",
"command": "node",
"args": [
"<YOUR_PATH_TO_MCP_OF_MCPS>/build/index.js",
"--config-file",
"<YOUR_PATH_TO_CONFIG>"
]
}
}
}
