qbash / Database MCP server
Use your database in Claude, Cursor or ChatGPT, with nothing to install.
Connect Postgres, SQL Server or MySQL to qbash with a read-only login and get a hosted MCP server. Add its URL to Claude, Cursor, Claude Code or ChatGPT, sign in, and ask about your data. There is no npx, Docker or config file to keep up to date.
Your password is stored encrypted on qbash, not on each laptop. Queries run with the login's own rights, and you choose which tools the assistant can call.
Supported databases
Postgres, SQL Server and MySQL each add four tools.
Each database connector adds tools to list schemas, list tables, describe a table and run a query. Turn off any the assistant does not need. Each page below covers setup, the read-only login to create and an example.
| Database | Also covers | Read-only login |
|---|---|---|
| PostgreSQL | Supabase, Neon, Amazon RDS and other PostgreSQL hosts | A login with SELECT on the schemas the assistant should see |
| Microsoft SQL Server | Azure SQL and SQL Server on a cloud VM or on premises | A login with the db_datareader role |
| MySQL | MariaDB, Amazon RDS, Aurora MySQL and Google Cloud SQL | A user granted SELECT and nothing else |
Where it runs
Skip the install. qbash runs the database MCP server.
An open-source database MCP server runs wherever you install it. Each person sets it up, keeps it updated and puts a connection string in their client's config. On qbash the server is already running, and the password stays in one place.
| Concern | Self-hosted database MCP server | qbash |
|---|---|---|
| Where it runs | On each person's laptop, or on a server you deploy | Hosted on qbash |
| Database credentials | In each person's client configuration | Stored once in qbash, encrypted |
| Who can connect | Anyone with the configuration and the password | People you share the server with, signed in through OAuth |
| Removing access | Change the database password for everyone | Remove one person's share, or make the server private |
| Custom logic | Fork and maintain the server | Add a Task with your own query and checks |
Set it up
Connect the database, build the server, then add it to your client.
- Create a read-only login for the database the assistant should see.
- In qbash, connect PostgreSQL, Azure SQL or MySQL with that login.
- Open MCP Servers, select New server and add the connector block. Turn off any tools you do not want to expose.
- Share the server with the people who should use it, then copy the server URL from Connect.
- Add the URL as a custom connector in Claude, as an app in ChatGPT with developer mode turned on, or as a remote MCP server in Cursor or Claude Code. Then sign in with qbash. Developer mode in ChatGPT depends on your plan and workspace settings.
Queries run with the rights of the connected login. A read-only login keeps every query to reads, whatever the assistant asks for.
Before you build
Questions
Can the assistant change data?
Only if the connected login has write access. Connect a read-only login and the database rejects every write.
Can one server reach more than one database?
Yes. Add a block for each connector, such as PostgreSQL and MySQL, to the same MCP server, and the assistant sees each set of tools.
Which clients can connect?
Any client that supports remote MCP servers, including claude.ai, Claude Code, ChatGPT, Cursor and VS Code. Use OAuth sign-in where the client supports it.
Can I expose some tools and hide others?
Yes. Turn off connector tools you do not want the assistant to call, rename them, or replace them with Tasks that run fixed queries.
Is there a free plan?
Yes. The Free plan includes 100 executions a month and 3 Tasks, with no credit card.