DBHub Analytics vs Nlqueries
A side-by-side look at the DBHub Analytics and Nlqueries MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose DBHub Analytics for databases work as a local process; choose Nlqueries 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 DBHub Analytics when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- You want tools like
execute_sql, search_objects.
Choose Nlqueries when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
ANTHROPIC_API_KEY, OPENAI_API_KEY, QDRANT_API_KEY, NLQ_MCP_STATIC_TOKEN.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 48/100 · Fair | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | ANTHROPIC_API_KEY |
Tools & capabilities
DBHub Analytics tools 2
execute_sqlExecute SQL queries with read-only enforcement and row limitingsearch_objectsBrowse catalogs, schemas, tables, columns, indexes, and routines
Nlqueries 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.
DBHub Analytics
{
"mcpServers": {
"dbhub-analytics": {
"command": "npx",
"args": [
"-y",
"dbhub-analytics"
]
}
}
}
Nlqueries
{
"mcpServers": {
"nlqueries-nlqueries": {
"command": "uvx",
"args": [
"nlqueries-core"
],
"env": {
"ANTHROPIC_API_KEY": "YOUR_ANTHROPIC_API_KEY_HERE",
"OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE",
"QDRANT_API_KEY": "YOUR_QDRANT_API_KEY_HERE",
"NLQ_MCP_STATIC_TOKEN": "YOUR_NLQ_MCP_STATIC_TOKEN_HERE"
}
}
}
}
Frequently asked questions
DBHub Analytics is categorized under Databases and uses a local stdio subprocess. Nlqueries belongs to Databases and uses a local stdio subprocess. Pick DBHub Analytics for databases work and Nlqueries 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.
DBHub Analytics has no declared pricing — check the project's own site. Nlqueries 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 dbhub-analytics and nlqueries-nlqueries as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, DBHub Analytics has a quality signal of 48/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. Nlqueries has 49/100 (Fair) with 1 views, 0 installs and 4 GitHub stars.