Mcp Hive Proxy

io.github.MCP-HivePublished by GitHub account MCP-Hivev1.0.0Updated Oct 24, 2026

MCP Hive is a gateway to paid commercial-grade MCP servers. Learn more at https://mcp-hive.com

VerifiedSTDIODesktop onlyProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

A local proxy that connects an assistant to MCP-Hive, a paid gateway for commercial MCP servers, either one server at a time or all of them at once.

What you can do
Proxy a single named MCP-Hive server to the client, or run in gateway mode to expose all available servers through one proxy with namespaced tools (serverName___toolName). In gateway mode, discover servers and list their tools, resources and prompts. Run over stdio or HTTP transport with a chosen port, with optional verbose logging.
When to use it
Use it when you want to reach commercial MCP servers offered through MCP-Hive from an agentic host, either a specific one or the whole catalog behind a single connection.
Requirements
Runs as a local process via the npm package @mcp-hive-utils/proxy, so Node.js is needed. Requires MCP-Hive consumer credentials passed with the --credentials flag, obtained from the provider. Desktop host only; HTTP mode needs a port.
Before you install
It is a gateway to paid commercial servers, so using the proxied servers may involve payment. It requires consumer credentials on the command line; keep them out of shared logs and configs. In gateway mode all available servers' tools are exposed to the assistant.

Installation

In SourceWeft

  1. Open Mcp Hive Proxy in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

MCP-Hive Proxy

This is the MCP-Hive Proxy. It can be loaded by any agentic host in order to access MCP-Hive and is a gateway to other MCP servers. To obtain credentials, and read further documentation, go to mcp-hive.com

[smithery badge]

Running

The proxy can run in two modes:

Server Mode (Single MCP)

Proxy a specific MCP server to your MCP client:

bash
node src/proxy/mcpHiveProxy.ts --server <server-name> --local --credentials <credentials>

Gateway Mode (All MCPs)

Expose all available MCP servers through a single proxy with namespaced tools:

bash
node src/proxy/mcpHiveProxy.ts --gateway --local --credentials <credentials>

In gateway mode:

  • Discovery tools are available: discoverServers, listTools, listResources, listPrompts
  • All server tools are namespaced: serverName___toolName (e.g., validator___echo, accuweather___getWeather)

Proxy Flags

FlagDescription
--server <name>Proxy a specific MCP server (omit for gateway mode)
--gatewayExplicitly enable gateway mode
--httpRun the proxy in HTTP transport
--port <port_num>Port number to be used if HTTP-transport
--credentials <id>Consumer credentials for authentication
--verboseEnable verbose logging

Source: README.md at commit a6e0294

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts