A side-by-side look at the Dbmcp and Dbx MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Dbmcp for databases work over a hosted endpoint; choose Dbx for databases as a local process. You can also run both side by side in one mcpServers block.
DB_BACKEND.tables, schema, kind.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 49/100 · Fair | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Free |
| Required env vars | DB_BACKEND | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 33 | 27,359 |
| Directory activity | 1 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 39 | Not listed |
| Full listing | View Dbmcp | View Dbx |
tablesschemakindownercommentviewsdescriptiondefinitiondefinersecuritycheckOptionupdatableNo tool names declared yet. Check the project README from the listing page.
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.
{
"mcpServers": {
"dbmcp": {
"url": "http://127.0.0.1:9001/mcp"
}
}
}
{
"mcpServers": {
"dbx": {
"command": "npx",
"args": [
"-y",
"@dbx-app/mcp-server"
]
}
}
}