qbash / Postgres MCP server
Use Postgres in Claude, Cursor or ChatGPT, with nothing to install.
Connect a read-only Postgres login to qbash 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.
What the assistant gets
Four tools cover schema lookup and queries.
The PostgreSQL connector adds these tools to an MCP server. Turn off any the assistant does not need. A server for analysts might keep all four, and a server for a support team might expose a single saved query instead.
| Tool | What it does |
|---|---|
| postgres_list_schemas | Lists the user schemas in the database |
| postgres_list_tables | Lists tables, views and foreign tables in a schema |
| postgres_describe_table | Shows columns, types, keys, constraints and indexes for a table |
| postgres_execute_query | Runs a SQL query with the rights of the connected login |
Where it runs
Skip the install. qbash runs the Postgres MCP server.
An open-source Postgres 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 Postgres 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 database login with read-only access to the schemas the assistant should see.
- In qbash, connect PostgreSQL with that login.
- Open MCP Servers, select New server and add the PostgreSQL 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.
Your own rules
Wrap a query in a Task when the assistant should follow a fixed path.
A Task is a Python function saved on qbash. This one runs a single approved query for paid orders that have not shipped, and the assistant supplies only the number of days. Add the Task to the same MCP server and the assistant calls it like any other tool.
days = qbash.inputs.get("days") if days is None: days = 2 if not isinstance(days, int) or isinstance(days, bool) or not 1 <= days <= 90: raise ValueError("Provide a whole number of days from 1 to 90.") rows = qbash.integrations.postgres.execute_query( query=( "SELECT order_id, created_at FROM orders " "WHERE status = 'paid' AND shipped_at IS NULL " "AND created_at < now() - make_interval(days => $1) " "ORDER BY created_at LIMIT 100" ), query_params=[days], read_only=True, )["result"] qbash.output({ "waiting_orders": rows, "oldest_order": rows[0]["order_id"] if rows else None, })
Declare days as an optional Number input and name the Task Orders Waiting To Ship. Replace the orders table and its columns with your own schema, and check that created_at is stored in UTC.
Before you build
Questions
Can the assistant change data?
Only if the connected login has write access. Postgres rejects writes from a read-only login.
Does this work with Supabase, Neon or Amazon RDS?
Yes. They run PostgreSQL, so connect with the database host and a login. Supabase also has its own connector in qbash.
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.