MCPHub vs Sidewise

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

MCPHub logoMCPHubAggregators · Local subprocess (stdio)Self-hosted MCP gateway that aggregates, routes and manages multiple MCP servers behind one endpoint.48FairAuth: not declaredSidewise logoSidewiseAggregators · Remote HTTP/SSENews from 17 outlets with left/center/right bias tags and one-sided blindspot detection40FairAuth: not declared

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

Which MCP server should you choose?

MCPHub logoChoose MCPHub when

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

Sidewise logoChoose Sidewise when

  • You need dedicated capabilities in the Aggregators domain.
  • You prefer a remote HTTP/SSE transport.
Explore Sidewise

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMCPHub logoMCPHubSidewise logoSidewise
CategoryAggregatorsAggregators
Quality signal48/100 · Fair40/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthNot declaredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars2,5780
Directory activity 3 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

MCPHub tools

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

Sidewise 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.

MCPHub

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

Sidewise

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "sidewise": {
      "url": "https://sidewise.heyitsmejosh.com/mcp"
    }
  }
}

Frequently asked questions

MCPHub is categorized under Aggregators and uses a local stdio subprocess. Sidewise belongs to Aggregators and uses a remote HTTP/SSE transport. Pick MCPHub for aggregators work and Sidewise 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.

MCPHub is listed as free. Sidewise has no declared pricing — check the project's own site. 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 mcphub-2 and sidewise as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, MCPHub has a quality signal of 48/100 (Fair) with 3 views, 0 installs and 2,578 GitHub stars. Sidewise has 40/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.