Hub MCP vs Visibility — MCP Server Comparison | AllMCPs
Hub MCP vs Visibility
A side-by-side look at the Hub MCP and Visibility MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Hub MCP for developer tools work over a hosted endpoint; choose Visibility for developer tools over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Hub MCP when
You need dedicated capabilities in the Developer Tools domain.
You prefer a remote HTTP/SSE transport.
Its auth model fits you: API key required.
You have the keys it needs: HUB_PAT_TOKEN, MCP_AUTH_TOKEN.
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.
Hub MCP is categorized under Developer Tools and uses a remote HTTP/SSE transport. Visibility belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick Hub MCP for developer tools work and Visibility for developer tools.
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.
Hub MCP is listed as free. Auth: api key required. Visibility has no declared pricing — check the project's own site. Auth: no auth required. 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 docker-hub-mcp and visibility as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Hub MCP has a quality signal of 77/100 (Great) with 37 views, 0 installs and 170 GitHub stars. Visibility has 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.