Agent mode moves fast
Cursor’s agent can write a migration and apply it in one go. The risky part is easy to miss in a long diff.
JillionDB + Cursor
Cursor’s agent can change your schema as fast as your code. JillionDB shows you each change on your schema, in plain words, before it runs.
Cursor’s agent can write a migration and apply it in one go. The risky part is easy to miss in a long diff.
A migration can look fine and still cut off text, fail on rows you already have, or drop a column you meant to rename.
Cursor proposes, you see the change on a drawing of your schema, and nothing happens until you approve.
Create a key in Settings, then add this to .cursor/mcp.json in your project, or to ~/.cursor/mcp.json for every project. Put your key in place of dbk_…
{
"mcpServers": {
"jilliondb": {
"url": "https://jilliondb.com/mcp",
"headers": { "Authorization": "Bearer dbk_…" }
}
}
}Open Cursor’s settings, find MCP, and check that jilliondb shows as connected.
Fits your stack
Nothing to replace. Your agent proposes, you approve in JillionDB, and your own migration tool applies the SQL.
In plain words, like “add a timezone to users”.
Open the link the agent gives you. Each change is on your schema with its risk and a reason.
Your agent gets the exact migration, or your note, and carries on.
Still curious?
The docs cover every step, from connecting your agent to reading a review.
Read the docsNo. It works with your schema only, the shape of your tables. It never connects to your database.
No. JillionDB writes plain SQL and your agent puts it where your project keeps migrations. Prisma, Drizzle, Rails, Django, Laravel or plain SQL files all work.
It’s free during early access. Pro will be $12 a month for unlimited projects, keys and history.
PostgreSQL, MySQL and SQLite.
Open the demo and approve an agent’s change in under a minute.