MCP Sqlite vs Nhost
A side-by-side look at the MCP Sqlite and Nhost MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Sqlite for databases work as a local process; choose Nhost for databases. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Sqlite 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
db_info, query, list_tables.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 65/100 · Great | 51/100 · Good |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | No auth required | Not declared |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 131 | 9,366 |
| Directory activity | 5 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 8 | Not listed |
| Full listing | View MCP Sqlite | View Nhost |
Tools & capabilities
MCP Sqlite tools 8
db_infoGet information about the SQLite database including path, existence, size, and table countqueryExecute a raw SQL query against the database with optional parameter valueslist_tablesList all user tables in the SQLite database (excludes system tables)get_table_schemaGet the schema information for a specific table including column detailscreate_recordInsert a new record into a table with specified dataread_recordsRead records from a table with optional conditions, limit, and offsetupdate_recordsUpdate records in a table based on specified conditionsdelete_recordsDelete records from a table based on specified conditions
Nhost 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.
MCP Sqlite
{
"mcpServers": {
"jparkerweb-mcp-sqlite": {
"command": "npx",
"args": [
"-y",
"mcp-sqlite"
]
}
}
}
Nhost
No confirmed install command for Nhost yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
MCP Sqlite is categorized under Databases and uses a local stdio subprocess. Nhost belongs to Databases and uses an install path we have not confirmed yet. Pick MCP Sqlite for databases work and Nhost 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. Nhost has no confirmed install command yet — follow its own setup instructions.
MCP Sqlite is listed as free. Auth: no auth required. Nhost is listed as free. 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 jparkerweb-mcp-sqlite and nhost-nhost as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Sqlite has a quality signal of 65/100 (Great) with 5 views, 0 installs and 131 GitHub stars. Nhost has 51/100 (Good) with 0 views, 0 installs and 9,366 GitHub stars.