A side-by-side look at the Gateway and Dbhub MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Gateway for databases work over a hosted endpoint; choose Dbhub for databases as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Gateway when
You need dedicated capabilities in the Databases domain.
No tool names declared yet. Check the project README from the listing page.
Dbhub tools 1
dbhub.toml
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.
Gateway is categorized under Databases and uses a remote HTTP/SSE transport. Dbhub belongs to Databases and uses a local stdio subprocess. Pick Gateway for databases work and Dbhub for databases.
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.
Gateway is listed as free. Auth: api key required. Dbhub 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 centralmind-gateway and dbhub as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Gateway has a quality signal of 52/100 (Good) with 5 views, 0 installs and 548 GitHub stars. Dbhub has 57/100 (Good) with 1 views, 0 installs and 3,691 GitHub stars.