Watchmode vs MCPHub

A side-by-side look at the Watchmode and MCPHub MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Watchmode logoWatchmodeAggregators · Local subprocess (stdio)Streaming availability across 200+ services: titles, sources, releases.43FairAuth: not declaredMCPHub logoMCPHubAggregators · Local subprocess (stdio)Self-hosted MCP gateway that aggregates, routes and manages multiple MCP servers behind one endpoint.43FairAuth: not declared

Verdict: choose Watchmode for aggregators work as a local process; choose MCPHub for aggregators as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Watchmode logoChoose Watchmode when

  • You need dedicated capabilities in the Aggregators domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: PLATFORM_WATCHMODE_KEY.
Explore Watchmode

MCPHub logoChoose MCPHub when

  • You need dedicated capabilities in the Aggregators domain.
  • You prefer a local stdio subprocess transport.
Explore MCPHub

Feature & specification comparison

Rows where the two servers differ are marked.

SpecWatchmode logoWatchmodeMCPHub logoMCPHub
CategoryAggregatorsAggregators
Quality signal43/100 · Fair43/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredFree
Required env varsPLATFORM_WATCHMODE_KEYNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars02,572
Directory activity 1 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Watchmode tools

No tool names declared yet. Check the project README from the listing page.

MCPHub tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Watchmode

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "watchmode": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-watchmode"
      ],
      "env": {
        "PLATFORM_WATCHMODE_KEY": "YOUR_PLATFORM_WATCHMODE_KEY_HERE"
      }
    }
  }
}

MCPHub

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcphub-2": {
      "command": "npx",
      "args": [
        "-y",
        "time-mcp"
      ]
    }
  }
}

Frequently asked questions

Watchmode is categorized under Aggregators and uses a local stdio subprocess. MCPHub belongs to Aggregators and uses a local stdio subprocess. Pick Watchmode for aggregators work and MCPHub for aggregators.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Watchmode has no declared pricing — check the project's own site. MCPHub is listed as free. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add watchmode and mcphub-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Watchmode has a quality signal of 43/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. MCPHub has 43/100 (Fair) with 1 views, 0 installs and 2,572 GitHub stars.