discoverServersLABSCO SUMMARY
Gateway mode trades tool-name clarity for one connection.
The namespacing is the whole design: accuweather___getWeather is ugly to read and unambiguous to call, which is the right trade when a dozen upstream servers are sharing one connection. Use server mode when you know exactly which one server you want and would rather see its tools under their real names. The catch with any aggregator is that the tool list you see belongs to the servers behind it, not to this package — what this package itself contributes is the four discovery tools and the routing.
What it is
The client-side proxy for MCP-Hive, a hosted catalogue of MCP servers. It runs in your agent host and routes calls out to Hive, in one of two modes: server mode proxies a single named MCP server through to your client, and gateway mode exposes every server available to you through one connection, with each upstream tool namespaced as serverName___toolName.
What you get
- A single named MCP server from Hive wired into your client, with
--server <name>naming which one - Or every server at once through one connection with
--gateway, where tools arrive namespaced —validator___echo,accuweather___getWeather— so two servers that both call a toolsearchdo not collide - Discovery tools in gateway mode that let the agent find out what is reachable before it calls anything:
discoverServers,listTools,listResources,listPrompts - A choice of transport: stdio by default, or HTTP with
--httpand--port, plus--verbosewhen a call is not going where you expect
Requirements
Consumer credentials from mcp-hive.com, passed with --credentials. The npm package is @mcp-hive-utils/proxy (1.0.19 in package.json, 1.0.15 pinned in server.json) with a mcp-hive-proxy binary and stdio transport; a Smithery listing is available for one-click install into Claude Desktop. Whatever the upstream server itself needs — its own API key, its own account — still applies; the proxy carries your Hive identity, not the upstream service's.
Setup effort
One command plus credentials — npx @mcp-hive-utils/proxy --gateway --credentials <YOUR_CREDENTIALS>, then supply credentials
USE CASES
01
Adding one hosted server without hosting anything
Point the proxy at a single named server from the Hive catalogue and let it appear in your client as if it ran locally.
02
Giving an agent a broad toolbox from one connection
Run in gateway mode so every server you have access to is reachable at once, each tool prefixed with the server it came from.
03
Finding out what is actually available to you
Ask for the server list and then the tools, resources and prompts on the ones that look relevant, before writing any workflow around them.
04
Serving several clients from one process
Run the proxy over HTTP on a chosen port instead of stdio, so it is not tied to a single client's process lifetime.
4 tools
Listed in project docs. Your client may show a different list.
listToolslistResourceslistPromptsBEFORE YOU INSTALL
What to know first
Tools you get
4 tools named in the project's documentation.
Requires
npx on PATH
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"mcp-hive": {
"command": "npx",
"args": [
"@mcp-hive-utils/proxy",
"--gateway",
"--credentials",
"<YOUR_CREDENTIALS>"
]
}
}
}<YOUR_CREDENTIALS> is a credential ID from your MCP Hive account (Credentials → New Credential → Generate). To proxy a single server instead of all of them, use --server and that server's name instead of --gateway.
npx
TERMINAL
npx @mcp-hive-utils/proxy --gateway --credentials <YOUR_CREDENTIALS>
