Sidewise vs MCPHub

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

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

Verdict: choose Sidewise for aggregators work over a hosted endpoint; 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?

Sidewise logoChoose Sidewise when

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

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.

SpecSidewise logoSidewiseMCPHub logoMCPHub
CategoryAggregatorsAggregators
Quality signal40/100 · Fair48/100 · Fair
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars02,578
Directory activity 1 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

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

Sidewise

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

MCPHub

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

Frequently asked questions

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

Sidewise 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 sidewise and mcphub-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.

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