Dataki for Supabase
Ask Supabase in plain English
Connect your Supabase Postgres database and turn it into dashboards. Sign in with Supabase to pick the project, add its database password, and Dataki queries your tables directly.
Connects directly Sign in with Supabase, then add the database password.
How many people signed up each week for the last eight weeks?
Weekly signups went from 312 to 544 in six weeks; this week has 521 so far.
01Questions
What people ask Supabase
Each one becomes a query against Supabase, run read-only, with the SQL shown beside the chart so anyone who reads SQL can check it. Anything worth keeping goes on a dashboard that refreshes on its own.
- How many people signed up each week this month, and how many came back?
- Which plan do our most active users pay for?
- How many projects did each plan create in the last 7 days?
- Which organisations added the most members this month?
02From your assistant
Ask Supabase from Claude, ChatGPT or Cursor
Dataki runs a hosted MCP server. Add it to your assistant once and it can read your Supabase schema and run read-only queries through Dataki. The assistant gets the rows back; the Supabase credentials stay encrypted in Dataki and never reach the model.
Setup for your assistant:
How many new users did we get each day this week in Supabase, and which sign-up method did they use?
- list_sources · finds Supabase · public
- get_data_context · reads the tables and what the columns mean
- query · runs the SQL read-only, returns the rows
- render_ui · draws the chart from those rows, in the chat
https://dataki.ai/api/mcp 03Setting it up
Connecting Supabase
Sign in with Supabase, then add the database password. The setup guide covers it step by step.
- Setup
- About 10 minutes, the read-only role included.
- Connects from
34.89.253.13, over IPv4. Allow it if you use network restrictions.- Encryption
- TLS: Dataki offers it first, so Supabase's
Enforce SSLcan be on. The server certificate is not verified. - What it reads
- Tables and views in the
publicschema, and only the rows row level security lets its role see.
Live dashboards
Every answer can become a live dashboard.
Ask in plain English. Dataki writes the SQL, runs it on your database and charts the answer. Keep it as a dashboard with its own link, and your team sees current numbers every time they open it.
3 views · Updated just now
One click turns the answer into a dashboard:
Always current. The query runs again whenever the dashboard opens, so Friday's meeting sees Friday's numbers.
- Share it
- Send the link to anyone. Viewers are free on every plan.
- Refine it
- The SQL is always visible. Adjust it by hand or ask for a change.
- Embed it
- Put the same dashboard in your own product with two HTML tags.
Using Dataki with Supabase
- Can I query Supabase in plain English instead of writing SQL?
- Yes. Dataki reads your Supabase schema, turns a plain-English question into a query, runs it on Supabase and returns a chart. The query is shown with every result, so you can check or edit it.
- Is there a hosted Supabase MCP server?
- Yes, Dataki. Its remote MCP server reaches Supabase through a read-only connection you set up once in Dataki: nothing to install, and no connection string in your assistant's config. Assistants can list sources, read the schema and what it means, run read-only SQL, draw charts in the conversation and save dashboards. Every query is logged with the key that ran it.
- How do I build a dashboard from Supabase data without an ETL pipeline?
- Connect Supabase to Dataki with a read-only connection, ask your question and save the answer as a dashboard widget. Dataki queries Supabase live, so there is no pipeline to build, no warehouse to sync and no copy of your data to maintain.
- Can Claude, ChatGPT or Cursor query my Supabase data?
- Yes, through Dataki's hosted MCP server at https://dataki.ai/api/mcp. Connect Supabase to Dataki, add that URL as a connector in Claude or ChatGPT (or in Cursor, VS Code or Claude Code with a Dataki key), and your assistant can read the schema and run read-only queries. It works with the results, while your credentials stay encrypted in Dataki and never reach the model.