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.
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.
- 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
Node on your PATH, and the other MCP servers already configured for the hub to connect to — every call identifies its target by serverName.
One command — npx -y mcp-hub-mcp