Give your team read-only PostgreSQL access, from ChatGPT or Claude
Your teams query the PostgreSQL database in plain language from their AI, on the tables that concern them only, with no database credentials and no SQL to write.
Published on October 28, 2026
In short
- Connect the database once in Persyst, with a read-only role: each team queries it in plain language from its assistant, with no credentials.
- Each team only sees its tables: the schema passed to the assistant contains nothing else.
- Persyst only runs SELECTs bounded to 200 rows and 60 seconds, and records every query.
How many new subscribers this week, and how many cancellations?
From October 20 to 26: 3,180 new subscribers and 1,940 cancellations, so +1,240 net. Cancellations are stable compared with the previous week; the rise comes from Wednesday’s sign-ups. Query on subscriptions, grouped by day.
Sources consulted
- PostgreSQL · subscriptions table · read
The problem: the data is there, access is not
Everyday questions (how many subscribers, which clients, which trend) have their answer in the database. Getting it takes credentials, writing SQL, or asking someone on the tech team. Handing out credentials opens the whole database; so does installing an MCP server on every machine.
How Persyst opens the database, table by table
With Persyst’s PostgreSQL connector:
- An administrator connects the database once, with a read-only role. Credentials stay encrypted in Persyst; the assistant never receives the password or the host.
- They open tables to each team: product sees
subscriptionsandpayments, finance also seesinvoices, nobody seesusers. - The member asks their question in their assistant. The assistant reads the allowed schema, writes a SELECT, and Persyst runs it (
query_database) within the set limits.
Every query is recorded: who, which table, when.
Three questions to try
- “Who are the ten clients who ordered the most this quarter?”
- “Compare the average basket in September and October, by acquisition channel.”
- “How many accounts created last month never paid?”
Preparing the database
- A dedicated role for Persyst, with SELECT only.
- Readable tables: explicit column names help the assistant write the right query.
- Views for sensitive business calculations (revenue, churn): the team queries the view, the definition stays under control.
The PostgreSQL guide details the connection, and each member adds Persyst to their assistant from getting started.
Limits to know
- No writes: no INSERT, UPDATE, DELETE or multiple statements.
- 200 rows and 60 seconds at most per query.
- A table that is not opened appears neither in the schema nor in results.
Questions
Frequently asked questions
How is read-only guaranteed?
Persyst only accepts a SELECT or WITH … SELECT statement, with no writes and no DDL. Also connect a PostgreSQL role that only has SELECT on the relevant tables: the guarantee then holds on the database side too.
Do I need to write SQL?
No. The member asks in plain language. The assistant reads the allowed schema, writes the query, Persyst runs it and returns the result. The query stays visible for anyone who wants to check it.
Can I export a whole table?
No. Each query is limited to 200 rows: the intended use is questions, not extraction. A full export goes through your usual tools.
What about a Supabase database?
A Supabase database is a PostgreSQL database: it connects with this connector, with the same guarantees.