NeoSQL MCP vs Db Access MCP
A side-by-side look at the NeoSQL MCP and Db Access MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
N
NeoSQL MCPDatabases · Local subprocess (stdio)Schemas, SQL, ERDs, and codegen for PostgreSQL, MySQL, Oracle, SQLite, and more via NeoSQL Desktop.60GoodAuth: no auth requiredVerdict: choose NeoSQL MCP for databases work as a local process; choose Db Access MCP for databases as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
NChoose NeoSQL MCP 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
ping, get-mcp-session-id, list-connections.
Choose Db Access MCP when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- You want tools like
dialect_list, connection_list, connection_find.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | N NeoSQL MCP | |
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 60/100 · Good | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 10 | 11 |
| Full listing | View NeoSQL MCP | View Db Access MCP |
Tools & capabilities
NeoSQL MCP tools 10
pingReturns `pong` for a lightweight MCP health check.get-mcp-session-idDiagnostic tool that returns the upstream session id used by this process.list-connectionsLists MCP-enabled NeoSQL connections and schemas for the current project.get-context-helpExplains active-project Default and explicit target usage.list-tablesLists tables.get-table-detailsReturns columns, keys, indexes, and related table metadata.erd-create-tablesAdds virtual tables to an ERD without changing the database.erd-modify-tablesModifies virtual ERD table models without changing the database.execute-queryExecutes SQL, including DDL.generate-codeGenerates and saves source files for specified tables using template packs configured in Project Settings. Requires template packs, required variables, and an output folder (Location). May overwrite existing files without an additional confirmation dialog.
Db Access MCP tools 11
dialect_listLists the supported database dialects: name (the `type` value for connections), default port and the plan format `query_plan` produces.connection_listLists configured connections: key, type, description, `read_only`, host/port/database, tunnel name, metadata. Credentials are **never** returned (allowlist-based sanitization; connection strings are parsed only for host/port/database).connection_findFinds connections by `host`, `port`, `database`, `type`, `read_only` and/or `metadata` key-value pairs. All filters are combined with **AND**. `user`/`password` filters are ignored (and noted in the response).connection_testEnd-to-end health check: secrets → tunnel → pool → one-row server-info query. Returns `ok: true` with server version/user/database/latency, or `ok: false` with the failure code and hint (an unreachable DB is a valid result, not a tool error).queryExecutes SQL on a connection. Accepts `connection`, `query`, optional `database` (see multi-database connections), `max_rows` and `timeout_ms` overrides. Results are truncated to the row cap with `truncated: true`.query_to_fileExecutes a query and writes the result to a file (`csv`/`jsonl`, inferred from the extension) instead of the model context. `file_path` is relative to the export dir (default `/tmp/db-access-mcp/exports`, created on demand), or an absolute/`~` path **under** the export dir or a configured `allow_ex…query_planReturns the execution plan without running the query: `EXPLAIN (FORMAT JSON)` for postgres, `EXPLAIN FORMAT=JSON` for mysql, text `EXPLAIN` for redshift, `SHOWPLAN_XML` for mssql.up_tunnelOpens (or reuses) the tunnel configured for a connection and returns `{host, port, tunnel_id, reused}`. Optional `local_port` binds an exact local port; if the tunnel is already open on a different port or the port is taken, the call fails with the current port in the error.down_tunnelCloses a tunnel by `tunnel_id`. By default only the up_tunnel pin is released — if query pools still hold the tunnel it stays open (`remaining_holders`); `force: true` drains the holder pools and closes it unconditionally.tunnel_listLists the tunnels currently open in this MCP instance with a live health probe: `tunnel_id`, tunnel name/type, local and remote endpoints, `healthy`, holder pools (`connections`), up_tunnel `pins`, external PIDs.config_reloadRe-reads the config files into the running server so connections/tunnels added or edited on disk become usable without a restart. **Never disturbs live state** — see below.
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.
NeoSQL MCP
{
"mcpServers": {
"neosql-mcp": {
"command": "npx",
"args": [
"-y",
"neosql-mcp"
]
}
}
}
Db Access MCP
{
"mcpServers": {
"rheopyrin-db-access-mcp": {
"command": "npx",
"args": [
"-y",
"@rheopyrin/db-access-mcp"
]
}
}
}
Frequently asked questions
NeoSQL MCP is categorized under Databases and uses a local stdio subprocess. Db Access MCP belongs to Databases and uses a local stdio subprocess. Pick NeoSQL MCP for databases work and Db Access MCP 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.
NeoSQL MCP is listed as free. Auth: no auth required. Db Access MCP 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 neosql-mcp and rheopyrin-db-access-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, NeoSQL MCP has a quality signal of 60/100 (Good) with 0 views, 0 installs and 1 GitHub stars. Db Access MCP has 56/100 (Good) with 1 views, 0 installs and 0 GitHub stars.