Quarry vs MCP Datalink
A side-by-side look at the Quarry and MCP Datalink MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Q
QuarryDatabasesSafety-railed database access: Postgres, MySQL, SQLite, Redis. Read-only by default.35FairAuth: not declaredVerdict: choose Quarry for databases work; choose MCP Datalink 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 MCP Datalink when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
list_databases, list_tables, describe_table.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Q Quarry | |
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 35/100 · Fair | 60/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner |
Tools & capabilities
Quarry tools
No tool names declared yet. Check the project README from the listing page.
MCP Datalink tools 6
list_databasesList configured database connectionslist_tablesList tables with row countsdescribe_tableGet schema, indexes, foreign keysqueryRun SELECT queriesexecuteRun INSERT/UPDATE/DELETEexplainShow query execution plans
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.
Quarry
No confirmed install command for Quarry yet — follow the setup steps linked from its listing page rather than a guessed package name.
MCP Datalink
{
"mcpServers": {
"pilat-mcp-datalink": {
"command": "npx",
"args": [
"-y",
"@pilat/mcp-datalink"
]
}
}
}
Frequently asked questions
Quarry is categorized under Databases and uses an install path we have not confirmed yet. MCP Datalink belongs to Databases and uses a local stdio subprocess. Pick Quarry for databases work and MCP Datalink 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. Quarry has no confirmed install command yet — follow its own setup instructions.
Quarry is listed as free. MCP Datalink is listed as free. 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 quarry-2 and pilat-mcp-datalink as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Quarry has a quality signal of 35/100 (Fair) with 0 views, 0 installs and 4 GitHub stars. MCP Datalink has 60/100 (Good) with 2 views, 0 installs and 5 GitHub stars.
