Why is DBHub MCP not working in Cursor?

It worked in our test on Oct 21, 2026. Errors we observed: {"success": {"content": [{"text": {"text": "{\n \"success\": false,\n \"error\": \"table test_records has no column named value\

DBHub MCP not working in Cursor? Fixes

Passed It worked in our test on Oct 21, 2026. Below is the exact setup we used in Cursor (2026.10.19-6bbf2c4), every error we saw, and what to check, all from our own run log.

Date tested: Oct 21, 2026 · From our harness, not the maker’s claims · How we test

1. Use the install config we tested in Cursor

{
 "mcpServers": {
  "dbhub": {
   "command": "/home/box/opt/node24/bin/npx",
   "args": [
    "-y",
    "@bytebase/dbhub@latest",
    "--transport",
    "stdio",
    "--dsn",
    "sqlite:///workspace/timmy/harness/sandbox/db/dbhub.db"
   ],
   "env": {
    "PATH": "/home/box/opt/node24/bin:/usr/local/bin:/usr/bin:/bin"
   }
  }
 }
}

Replace any <YOUR_…> placeholder and local test paths with your own. Every client’s tested snippet is on the DBHub page.

2. Check that Cursor connects to it

In our run the connect check was OK (connected in 1.4s). Our check output:

dbhub: ready

3. Confirm the tools are visible

Cursor listed 2 tools from this server in our run (the protocol check found 2). Fewer or none usually means the server did not start; check the config above.

Errors we observed

agent task: roundtrip (tool error during the run): {"success": {"content": [{"text": {"text": "{\n \"success\": false,\n \"error\": \"table test_records has no column named value\",\n \"code\": \"EXECUTION_ERROR\"\n}"}}], "isError": true, "systemReminders": []}}

Quoted from our run log. Secrets redacted. We list only what we saw.

More help

DBHub: all results and setup · Full Cursor run · General Cursor MCP troubleshooting