Add the SQLite (DBHub) MCP server to Cursor
Config last verified Jun 1, 2026
The exact config to run SQLite (DBHub) in Cursor — paste it in, restart, and the tools load.
Prerequisites
- Cursor installed.
- DSN — Database connection string. For SQLite use sqlite:///path/to/database.db. Can be passed as --dsn or via the DSN env var.
Setup
1. Open ~/.cursor/mcp.json
2. Add this configuration
Add to ~/.cursor/mcp.json
~/.cursor/mcp.json
json
{
"mcpServers": {
"sqlite": {
"command": "npx",
"args": [
"-y",
"@bytebase/dbhub",
"--transport",
"stdio",
"--dsn",
"sqlite:///path/to/database.db"
]
}
}
}3. Restart Cursor and confirm the SQLite (DBHub) tools load.
Gotchas
Cursor keeps MCP servers under an "mcpServers" object in ~/.cursor/mcp.json for global use, and also reads a project-scoped .cursor/mcp.json so a repository can ship its own servers. Remote servers are configured with a bare "url" field and connect natively, with OAuth handled in-app when a server requires it.