Persyst connector
Redash MCP connector for ChatGPT, Claude and Copilot
Connected once by the company, with no Redash account 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 a vendor MCP server: Redash does not publish one, Persyst provides its own, hosted, with nothing to install on workstations.
- Query by query: a Redash query is approved, then opened to a team, a client or a person. The others do not exist for their AI.
- No free-form SQL: the assistant reads the latest computed result or runs an approved query with validated parameters.
- The Redash API key stays encrypted in Persyst; it is never sent to the browser or the assistant.
EXAMPLES
What your team can ask
What is the monthly churn over the last three months?
According to the “Monthly churn” query computed this morning at 6:10: 2.1% in July, 2.4% in August, 1.9% in September. September’s drop follows the launch of end-of-trial reminders.
Sources consulted
- Redash · Monthly churn · latest result
How many orders for the customer Atelier Nord in September?
Query “Orders by customer” run with customer = Atelier Nord, period = September: 37 orders, €12,400 excl. VAT, average basket €335.
Sources consulted
- Redash · Orders by customer · parameterized run
HOW IT WORKS
Redash in your AI, in three steps
Connect the instance
Under Data sources, an administrator enters the Redash instance URL and a user API key. Persyst tests the connection, encrypts the key and never returns it to the browser. The key can be replaced at any time; reads in progress are then invalidated.
Approve and open queries
The administrator selects the Redash queries to expose, then grants them to a team, a client or a person, with the allowed tools. Running parameterized queries is enabled separately from reading results.
Ask from the assistant
The member asks their question in ChatGPT, Claude or Copilot. The assistant picks an approved query, reads its latest result or runs it with validated parameters, and cites its computation time. The history keeps who used which tool, and when.
TOOLS
What your assistant can do
Redash· 5 tools
Opened team by teamLists the queries approved for the member, with their description and parameters, without SQL.
list_redash_queriesSearches those queries by name or description.
search_redash_queriesDetails of an approved query: expected parameters, freshness of the latest result.
get_redash_queryLatest computed result of a query without parameters, with its computation time.
read_redash_query_resultRuns an approved query with validated parameters, paginated through a continuation.
execute_redash_query
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 Redash MCP server?
| Criterion | Persyst | Community Redash 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 free-form SQL, no query creation or edition from the assistant.
- No dashboards, widgets or alerts: only the query is a Persyst resource.
- No copy of the results: every read goes through Redash, with the freshness of the latest computation or a guarded run.
- The queries’ SQL is never sent to the assistant, only their metadata and results.
Questions
Frequently asked questions
Is there an official MCP server for Redash?
Persyst does not need one. It calls the Redash API with the organization’s key and exposes its own read tools. Community servers require an API key per machine and expose every query that key can reach; Persyst opens queries one by one.
Does every member need a Redash account?
No. An administrator connects the instance with a Redash user API key. Authorized members then read the opened queries from their AI, without a Redash account.
Can an executive ask a question without opening Redash?
Yes. If they have access to the “Net subscribers” query, they ask their assistant for this week’s figure and get the latest computed result, with its date. They have no Redash login and no dashboard to maintain.
How do I limit what a team can read?
You approve specific queries and grant them to a team, a client or a person. A marketing team can read “Monthly churn” without ever seeing “Margins”.
Are parameterized queries safe?
Parameter values are validated before execution; no SQL, job id or result id is accepted from the assistant. Execution has to be explicitly enabled for the connection.
