Persyst connector
Read-only PostgreSQL MCP connector for ChatGPT, Claude and Copilot
Connected once by the company, read-only, with no database credentials for each member.
Updated on October 11, 2026
Your tools
- Connected once, by the admin
- Rights per person, team or client
- Who read what, and when
Everyone’s AI
In short
- Persyst works without an MCP server to install: it is a remote MCP server, shared by the whole team, with no Node or Python on workstations.
- Read-only: SELECT or WITH … SELECT only, a single statement, at most 200 rows and 60 seconds per query.
- Per table: a team sees subscriptions and payments, not users. The schema sent to the assistant only contains the opened tables.
- Connection credentials stay encrypted in Persyst; the assistant receives results, never the password or the host.
EXAMPLES
What your team can ask
How many net subscribers this week?
+1,240 net subscribers from September 29 to October 5: 3,180 new, 1,940 cancellations. Wednesday’s peak follows the new season launch.
Sources consulted
- Table subscriptions · read
- Table payments · read
Which ten customers ordered the most this quarter?
Atelier Nord leads with 48 orders for €31,200, then Groupe Verne (37, €24,800) and Beltran (29, €19,100). The next seven are between €8,000 and €15,000. Query on orders joined to customers, July 1 to September 30.
Sources consulted
- Table orders · read
- Table customers · read
HOW IT WORKS
PostgreSQL in your AI, in three steps
Connect the database
Under Data sources, an administrator enters the host, port, database and a read role. Persyst tests the connection and encrypts the credentials; they are never returned to the browser. We recommend a PostgreSQL role limited to SELECT on the tables to share.
Open tables to each team
The administrator links the connection to a team, a client or a project, then picks the opened tables. Those tables’ schema is provided to the assistant, the rest of the database is unknown to it. Allowlists can be changed at any time.
Ask from the assistant
The member asks their question in ChatGPT, Claude or Copilot. The assistant reads the allowed schema, writes a SELECT query and sends it to Persyst, which checks it, runs it within its limits and returns the result. The history keeps who queried which database, and when.
TOOLS
What your assistant can do
PostgreSQL· 1 tool
Opened team by teamRuns a read-only SELECT query on the tables opened to the team, at most 200 rows and 60 seconds. The assistant first reads the allowed schema.
query_database
Rights and audit trail
Rights per person, team or client.
Then, inside the tool, only the items you open. The rest does not exist for the AI.
One-click revocation.
Removing a member cuts their access in every AI at once.
A history.
Who used which tool, and when.
Credentials that stay put.
They remain encrypted in Persyst, never in the assistants.
COMPARISON
Persyst or a PostgreSQL MCP server?
| Criterion | Persyst | Community PostgreSQL MCP server |
|---|---|---|
| Who authenticates | The company, once, through an administrator. | Each member, with their own API key. |
| Installation | None: a remote MCP server, authorized from the assistant. | A server to install and maintain on every machine, or a third-party service you hand the key to. |
| Where credentials live | Encrypted in Persyst, never in the assistant. | In each member’s assistant configuration. |
| Scope | Per person, team or client, then per opened item. | Everything the key allows. |
| History | Who used which tool, and when, for the whole team. | None, or machine by machine. |
| When a member leaves | One-click revocation, in every AI. | A key to revoke at the vendor, machine by machine. |
What this connector does not do
- No writes: no INSERT, UPDATE, DELETE or DDL, and no multiple statements.
- No table outside the allowlist: an unopened table appears neither in the schema nor in results.
- No bulk extraction: 200 rows per query. A full export goes through your usual tools.
- No personal connection: PostgreSQL connects at the organization level, through an administrator.
Questions
Frequently asked questions
Is there an official MCP server for PostgreSQL?
There are many PostgreSQL MCP servers to install on a machine, with the database credentials. Persyst is the opposite: a remote server, connected once by the company, that exposes to each team only its tables, read-only, with a history.
How is read-only guaranteed?
Persyst only accepts a single SELECT or WITH … SELECT statement, with no writes or DDL, and bounds every query to 200 rows and 60 seconds. We also recommend connecting a PostgreSQL role that only has SELECT on the relevant tables.
Can an executive query the database without knowing SQL?
Yes. They ask their question in plain language in their assistant. The assistant reads the allowed schema, writes the SELECT, Persyst runs it and returns the result. They have no credentials and no dashboard to maintain.
Can different teams see different tables?
Yes. The connection is unique, the table allowlist is specific to each team. Product sees subscriptions and payments; finance also sees invoices; nobody sees users.
What about ClickHouse or Supabase?
ClickHouse has its own Persyst connector, with the same guarantees. A Supabase database is a PostgreSQL database: it connects with this connector, and the Supabase platform is read through its catalog MCP server.
