Dataki for Cursor

Query your database from Cursor

Dataki's hosted MCP server gives Cursor's agent read-only access to the databases you have connected to Dataki. It can read the schema, run queries while you work and save what it finds as a dashboard, and the connection string never sits in your editor.

  1. Cursor
  2. Dataki MCP server
  3. Your database, read-only
Signs in with
A Dataki API key, created for you on the install click.
Works in
Cursor's chat and agent.
You need
Cursor, and a Dataki account with at least one data source.
Server URL
https://dataki.ai/api/mcp
Connect Cursor Go to the steps

01Set it up

3 steps, a couple of minutes

Dataki's connect page walks through the same steps with buttons, and creates a key wherever one is needed.

  1. 01

    Add Dataki to Cursor from the connect page

    Open the Cursor steps on Dataki's connect page and click Add to Cursor. It creates a key for Cursor and opens Cursor with Dataki ready to install.

  2. 02

    In Cursor, click Install

  3. 03

    Ask it something in Cursor's chat

    Start with What data can you see in Dataki?.

Add it by hand instead

Create a key on Dataki's connect page and put it in ~/.cursor/mcp.json. The file holds the key, so keep it in your home directory rather than in a repository.

~/.cursor/mcp.json 
{
  "mcpServers": {
    "dataki": {
      "type": "http",
      "url": "https://dataki.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_DATAKI_KEY"
      }
    }
  }
}

02Ask it

What to ask in Cursor's chat

The assistant finds your sources, reads what the columns mean, writes the SQL and hands it to Dataki, which runs it read-only and returns the rows. The query is part of every answer.

Which tables in the billing database hold subscriptions, and how do they join to customers?

Answered from get_data_context: the tables, columns and types, plus any metric definitions and join paths your team has recorded for that source.

How many users signed up each day since Monday's release, and how does that compare with the week before?

The assistant writes the SQL, Dataki runs it read-only and returns the rows. The query is in the answer, so you can check it.

Are there any orders without a matching customer? Show me the ten most recent.

The kind of check you would otherwise run by opening a SQL client against production, without handing the editor a connection string.

Put a chart of daily signups for the last 90 days on a dashboard called Growth.

save_dashboard keeps it as a live Dataki dashboard with a link, which refreshes on its own and can be shared with people who never open an editor.

03What it can reach

Any source you connect to Dataki

Cursor sees the sources your Dataki account can open, and one question can read more than one of them.

04Worth knowing

What Cursor gets, and what it never does

The key is a password
It acts as you, and anything you can reach in Dataki, it can reach. It carries daily ceilings on query count and bytes scanned, every query it runs is logged with its name, and you can revoke it from Dataki at any time. Do not commit it to a repository.
Not a connection string in a config file
A local database MCP server needs the database URL on your machine and in the editor's config. With Dataki, the editor holds a revocable key; the database credentials stay encrypted in Dataki, and every query runs with a read-only role.
The data your app writes, not your code
Dataki answers from the database: signups, orders, events. It never sees your repository.

More on the server itself, and every tool it offers, on the MCP server page. How credentials, keys and the query log work: security and governance.

Dataki and Cursor

How do I connect Cursor to a PostgreSQL database with MCP?
Connect the database to Dataki with a read-only user, then add Dataki's hosted MCP server to Cursor: one click on Dataki's connect page, or an entry in ~/.cursor/mcp.json with a Dataki API key. Cursor's agent can then read the schema and run read-only queries.
Does Cursor get my database password?
No. Your database credentials are stored encrypted in Dataki and are never sent to Cursor or to any model. Cursor calls Dataki's MCP server, the server runs the SQL on its side with a read-only role, and only the rows that come back reach the conversation.
Can Cursor change or delete data through Dataki?
No. Dataki's query tool is read-only: a statement that changes data is refused before it runs, and the database connection itself uses a role that cannot write. Cursor can create and edit Dataki dashboards, which are Dataki's own records, never rows in your database.
Which databases can Cursor query through Dataki?
Any source connected to Dataki: Google BigQuery, PostgreSQL, MySQL, Amazon Redshift, Supabase, Google Sheets and uploaded CSV or Excel files, including hosted databases such as Neon, Amazon RDS, Cloud SQL and PlanetScale. Google Analytics 4, Firebase, Search Console, Firestore and Stripe work through their exports to BigQuery. One question can read more than one source.

Using another assistant?

Connect Cursor. Ask it something.

Connect a source to Dataki, add the server to Cursor, and the first answer is one question away. Anything worth keeping becomes a dashboard with a link that stays live.

Connect Cursor Stuck? Ask us