NeoSQL MCP vs Simple Snowflake MCP
A side-by-side look at the NeoSQL MCP and Simple Snowflake 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 Simple Snowflake 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 Simple Snowflake MCP when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
CONFIG_FILE, LOG_LEVEL, MCP_READ_ONLY. - You want tools like
execute-snowflake-sql, execute-query, get-connection-info.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | N NeoSQL MCP | |
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 60/100 · Good | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | API key required |
| Pricing | Free | BYOK (pay the provider) |
| Required env vars | None listed | CONFIG_FILELOG_LEVELMCP_READ_ONLY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 8 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 10 | 15 |
| Full listing | View NeoSQL MCP | View Simple Snowflake 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.
Simple Snowflake MCP tools 15
execute-snowflake-sqlExecutes a SQL query on Snowflake and returns the result. Supports `json` (default), `markdown`, and `csv` output via the `format` argument.execute-queryExecutes a SQL query with server-enforced read-only protection. In read-only mode (the default) only `SELECT`, `SHOW`, `DESCRIBE`, `EXPLAIN`, and `WITH` statements (without DML) are allowed. Read-only mode is governed **solely by server configuration** and cannot be relaxed by the caller. Supports…get-connection-infoReturns current Snowflake connection information and server status.list-snowflake-warehousesLists available Data Warehouses (DWH) on Snowflake. Pass `include_details: false` for names only.list-databasesLists all accessible Snowflake databases. Supports a `pattern` filter (wildcards) and `include_details`.list-schemasLists schemas in a `database`. Supports a `pattern` filter (wildcards) and `include_details`.list-tablesLists tables in a `database`/`schema`. Supports a `pattern` filter (wildcards) and `include_details`.list-viewsLists views in a `database`/`schema`. Supports a `pattern` filter (wildcards) and `include_details`.describe-tableReturns the columns and types of a `database`/`schema`/`table` (works for views too). Supports `json` (default)/`markdown`/`csv` via `format`.query-viewReads rows from a `database`/`schema`/`view` (or table) by name, with the same server-enforced read-only protection and row limiting as `execute-query`. Supports a `limit`, an `offset` for paging, and `markdown` (default)/`json`/`csv` via `format`.export-schemaExports hierarchical schema metadata (databases → schemas → tables/views → columns). Supports `json` (default), `yaml`, and `sql` via `format`, an optional `database` filter, and opt-in `include_data_samples` (table rows only, max 3 rows per table).add-noteAdds or updates a note (`name`, `content`) kept in server memory for the session.- +3 more on 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.
NeoSQL MCP
{
"mcpServers": {
"neosql-mcp": {
"command": "npx",
"args": [
"-y",
"neosql-mcp"
]
}
}
}
Simple Snowflake MCP
{
"mcpServers": {
"yannbrrd-simple-snowflake-mcp": {
"command": "uvx",
"args": [
"simple-snowflake-mcp"
],
"env": {
"CONFIG_FILE": "YOUR_CONFIG_FILE_HERE",
"LOG_LEVEL": "YOUR_LOG_LEVEL_HERE",
"MCP_READ_ONLY": "YOUR_MCP_READ_ONLY_HERE"
}
}
}
}
Frequently asked questions
NeoSQL MCP is categorized under Databases and uses a local stdio subprocess. Simple Snowflake MCP belongs to Databases and uses a local stdio subprocess. Pick NeoSQL MCP for databases work and Simple Snowflake 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. Simple Snowflake MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key 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 neosql-mcp and yannbrrd-simple-snowflake-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. Simple Snowflake MCP has 53/100 (Good) with 2 views, 0 installs and 8 GitHub stars.