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