call-tool
Call a specific tool from a specific server. TIP: Use find-tools first to discover the tool and get the correct serverName and toolName
LABSCO SUMMARY
One entry point instead of a client wired server by server.
Discovery is the whole design: find-tools takes a keyword or a regex and returns the serverName and toolName that call-tool needs, and get-tool fills in the input schema before the call goes out. list-all-tools carries its own advice to search first, which tells you what listing everything costs. Nothing here adds capability — it re-exposes what the connected servers already do, through a surface small enough to keep.
What it is
Seven tools that front other MCP servers — list what is connected, search their tools by pattern, read one tool's full input schema, and invoke it with arguments.
What you get
- The connected MCP servers listed
- Tool search by keyword or regex across every connected server, with case sensitivity and a choice of which field to match
- The same search scoped to a single server
- Every tool from every server, or every tool from one server, as name and description
- A named tool's complete schema, including its inputSchema
- A call placed against a named tool on a named server, with its arguments passed through
Requirements
Node.js 18.0.0 or later, and a Claude Desktop-format config file listing the servers the hub should connect to — pass it with --config-path, set MCP_CONFIG_PATH, or keep mcp-config.json in the directory the hub starts in. Every call identifies its target by serverName.
Setup effort
One command — npx -y mcp-hub-mcp
USE CASES
01
Finding a tool you are not sure exists
Search every connected server by keyword or regex, and what comes back is the server name and tool name the call needs, plus the schema to fill in.
02
Driving another server's tool from here
The call is placed by naming the server and the tool and passing the arguments through, so a session holding the hub reaches everything the hub is connected to.
03
Taking stock of one server's surface
Names and descriptions for everything a single server exposes, or a pattern search scoped to it, for when the question is what that server can do rather than where a specific tool lives.
7 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
find-tools
Use this tool to find best tools by searching with keywords or regex patterns. If you don't have a specific tool for a task, this is the best way to discover what tools are available.
find-tools-in-server
Find tools matching a pattern in a specific MCP server (returns name and description only)
get-tool
Get complete schema for a specific tool from a specific server, including inputSchema. TIP: Use find-tools first to discover the tool and get the correct serverName and toolName
list-all-tools
List ALL available tools from all connected servers. NOTE: For better performance, use find-tools with keywords first. Only use this when you need to see everything or if find-tools didn't find what you need
list-all-tools-in-server
List ALL tools from a specific MCP server (returns name and description only)
list-servers
List all connected MCP servers
BEFORE YOU INSTALL
What to know first
Tools you get
7 tools when we connected.
Requires
- npx on PATH
- Node.js 18.0.0 or later
- A Claude Desktop-format config file (mcpServers) listing the MCP servers the hub connects to
CONTEXT COST
Light Standing cost
Rated by the size of the 7 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
Configuration file
JSON
{
"mcpServers": {
"other-tools": {
"command": "npx",
"args": [
"-y",
"mcp-hub-mcp",
"--config-path",
"/Users/<YOUR_USERNAME>/mcp.json"
]
}
}
}Add this to your mcp.json. --config-path points at a Claude Desktop-format file (an mcpServers object) listing the servers the hub should connect to. You can set MCP_CONFIG_PATH instead, or keep mcp-config.json in the directory the hub starts in.
npx
TERMINAL
npx -y mcp-hub-mcp
