MySQL · MariaDB · Windows app · MCP

Give your agent the database. Keep the undo button.

OwlSQL lets Claude Code, Cursor and Codex query and fix your real MySQL database themselves, instead of asking you to paste from phpMyAdmin. It's read-only until you flip the switch, every write can be undone, and anything risky waits for you to click Allow in the OwlSQL app.

Free for one database · Pro $49 once · version 0.2.0 · Windows 10 and 11 · no Node.js needed

Works on shared hosting too: Hostinger, HostGator, Bluehost, GoDaddy, SiteGround, any cPanel box, or your own server.

claude code · my-shop
› some category names have "Jewlery" in them, fix it

⏺ owlsql_query(sql: "SELECT id, name FROM categories WHERE name LIKE '%Jewlery%'")
  3 rows, 38 ms
  id | name
  14 | Jewlery & Watches
  22 | Kids Jewlery
  31 | Jewlery Boxes

⏺ owlsql_query(sql: "UPDATE categories SET name = REPLACE(name, 'Jewlery', 'Jewelry') WHERE name LIKE '%Jewlery%'")
  Done: UPDATE on categories, 3 rows affected (41 ms).
  Undo: owlsql_undo reverts it (write id mux8k2a1).

› wait, the SEO plugin keys off those. put them back

⏺ owlsql_undo()
  Undone: write mux8k2a1 (UPDATE on categories)
  - restore 3 changed rows in categories

The owl's rules

An agent that can run SQL on a live site can also wipe it with one bad WHERE. OwlSQL sits between them and checks every statement before it runs.

Read-only until you flip the switch

Reads run in a read-only transaction that is always rolled back. Writes stay off until you switch them on in the app, per database. Agents can't flip that switch.

Risky writes wait for your click

No WHERE, more rows than your limit, dropping or emptying a table, or anything that can't be undone: the app shows the SQL and the rows it touches, and waits for Allow or Deny. Agents can't approve their own writes.

Every write can be undone

Before an UPDATE, DELETE, INSERT, ALTER, DROP or TRUNCATE runs, OwlSQL saves exactly what it will change, including rows a foreign key cascades into. One click in History puts it back.

Undo never clobbers your site

Before undoing, OwlSQL checks whether anything touched that data since. If customers placed orders in the meantime, it stops and shows you instead of wiping them.

Server-level damage is off the table

User and privilege changes, DROP DATABASE, reading or writing files on the server, global settings and multi-statement tricks are refused outright.

You see everything, live

Every call an agent makes shows up in the app as it happens: what it ran, how many rows, how long it took, and which agent it was. Every write is kept in a history you can undo from.

When it matters, the owl asks. You click.

Say your agent tries to raise every price by 10% without a WHERE. OwlSQL doesn't run it. The OwlSQL window comes to the front with the exact SQL, why it needs your OK, how many rows it touches, a sample of those rows, and whether it can be undone.

  • Allow runs it (snapshotted first, so it's still undoable). Deny tells the agent no, and to ask you instead of trying again.
  • The agent can't say yes for you. Its own "confirm" is ignored while the app is open. Set a database to Only approve here and risky writes wait until you open OwlSQL.
  • Nervous about a live store? Turn on Ask before every write for that database.
  • No answer within two minutes counts as Deny.
The OwlSQL approval dialog: Claude Code wants to change owltest. UPDATE products SET price = ROUND(price * 1.10, 2) has no WHERE clause and touches 8 rows; undo is available. Deny and Allow buttons.

A real approval from our test shop on Hostinger shared hosting.

The OwlSQL window: the Activity tab lists Claude Code's calls on owltest, from listing tables and a dry run to a fixed category name, and the 10% price change marked denied: nothing was changed.

The same session afterwards: the fix ran, the price change was denied.

Your database, with a window on it

OwlSQL is a desktop app, not just a plug-in. Agents' calls run inside it, so you always know what touched your data.

  • Activity: every agent call as it happens.
  • History & undo: every write, who made it, and an Undo button while its snapshot is kept.
  • Browse & query: your tables and rows, and a SQL box with the same safety rules.
  • Backups: the whole database to a .sql file in one click, optionally portable to older MySQL and MariaDB.
  • Connect an agent: one click for Claude Code, Claude Desktop or Cursor; copy-paste config for Codex and the rest.

Download OwlSQL

newVersion 0.2.0 for Windows 10 and 11 (64-bit). Free for one database; Pro unlocks unlimited databases.

Installer

Installs OwlSQL with a Start menu entry and desktop shortcut. Recommended.

Download installer 77 MB
SHA-256 c87e5b2bc67e24f6e108f63b9a3d16a7c6d5f88b7596c21b247dbd92a015eeaa

Portable

One file, nothing to install. Run it from anywhere, even a USB stick.

Download portable 77 MB
SHA-256 ad55a33c658eb03eb7d90e4bb63d62c1d0d5d1d1dd03c6185499bfcde69b1638

OwlSQL isn't code-signed yet, so Windows SmartScreen may say "Windows protected your PC". Click More info, then Run anyway. On a Mac or Linux? The command-line tool and MCP server run anywhere Node.js does; the npm package is coming soon.

Every feature free on one database. Pro for all of them.

Free is the full OwlSQL, nothing held back, for one database. The moment you connect a second one, a client's site or your own, that is Pro: $49 once, unlimited databases, updates for life.

Free

Your one database, with every feature. No account, no nag.

  • 1 database, direct, over SSH or through the PHP bridge
  • Read-only until you flip the switch
  • Snapshots and undo for every write
  • Approvals in the app for risky writes
  • Write history, backups, the table browser
  • MCP server for Claude Code, Codex, Cursor
Download

Pro $49, one-time payment

For anyone with more than one database: freelancers, agencies, a few sites of your own. Per person, up to three machines.

  • Unlimited databases, every client and project you have
  • Everything in Free, same download: paste your key and the limit is gone
  • Works in the app, the CLI and Claude Code (ask Claude to activate your OwlSQL license)
  • Updates for life, no renewals, no subscription
  • Priority support by email, from the person who wrote it
Buy Pro $49

Secure checkout by Stripe. Your key arrives by email within a minute. Lost it? Get your keys re-sent.

Three ways in. One works on your host.

Most shared hosts block MySQL connections from outside. In the app, Add database offers a way around that for every kind of host. You type the password into the app, it's encrypted with your Windows account, and the agent never sees it.

Remote MySQL

Direct connection

If your hosting panel has a "Remote MySQL" page, add your IP address there and connect straight in. Optional TLS.

SSH

SSH tunnel

Have SSH access? The database never has to be reachable from the internet. Uses your existing SSH key and pins the server's host key.

PHP bridge

One small file

Neither allowed? Your host still runs PHP. OwlSQL writes one file with a random name for you to upload next to your site. Without its secret token it only answers "404 Not Found".

Tested on Hostinger shared hosting (MariaDB 11.8) through the PHP bridge, and on MySQL 9.4 and MariaDB 10.4. When a shared host briefly refuses new connections, OwlSQL waits and tries again by itself. Works with the database behind WordPress, WooCommerce, Laravel and plain PHP sites.

How undo works

Before a write runs, OwlSQL saves exactly what it is about to change, in the same transaction. Undo puts it back, but only after checking that nothing else has touched those rows since.

The writeWhat OwlSQL saves firstWhat undo does
UPDATE / DELETEThe rows its WHERE matches, locked so nothing else can change them firstPuts the old values back by primary key; re-inserts deleted rows
INSERTThe new rowsRemoves exactly those rows
REPLACE, upserts, key changesThe table, keeping only the rows that changedApplies the reverse of the change
Foreign-key cascadesThe rows in other tables that cascade with itRestores them in the same transaction, parents first
ALTER, DROP, TRUNCATEThe table's full definition and every rowRebuilds the table and reloads it
CREATE TABLE / RENAMEThe namesDrops the new table / renames back

Undo first re-reads the affected rows and compares them with their state right after the write. If your site changed them since, undo stops and lists the conflicts. It only overwrites them if you say so. Some writes can't be snapshotted: statements across several tables, tables with no primary key (except deletes), and changes over 100,000 rows. OwlSQL tells you before running those.

Before a big change, make a backup from the Backups tab: the whole database in a .sql file you can import with phpMyAdmin. Tick Portable and it also imports into older MySQL and MariaDB versions.

Quickstart

About five minutes, and no terminal needed.

  1. Install OwlSQL

    Download the installer and run it. Everything is included; you don't need Node.js or anything else.

  2. Add your database

    Click Add database and pick one of the three ways in. Use the database login from your hosting panel or wp-config.php, not your FTP login. OwlSQL tests the connection, and for the PHP bridge, shows you exactly where to upload the file.

  3. Connect your agent

    Click Connect an agent, then Claude Code, Claude Desktop or Cursor, and start a new session. For Codex and others, the same dialog gives you the config to paste. To pin a project to its database, use Settings → Link a project folder.

  4. Let it write, when you're ready

    Until then, your agent can look but not touch. Flip Writes on for one database, keep OwlSQL open, and approve risky changes as they come. Flip it back off whenever you like.

Prefer a terminal?

Everything also works from the command line: owlsql db add, owlsql bridge, owlsql query, owlsql undo, owlsql dump, and owlsql mcp for agents. Commands run through the app when it's open, so you still see them there and approve risky writes in it. The npm package for Mac and Linux is coming soon.

Things the owl will never do

Some statements aren't about your data. They're about the server. OwlSQL refuses them however they're phrased, with a short explanation so the agent stops trying.

DROP DATABASEGRANTCREATE USERLOAD DATAINTO OUTFILELOAD_FILE()SET GLOBALKILLSHUTDOWN/*! hidden SQL */two statements; at once

Tools your agent gets

  • owlsql_query: one statement, with placeholders and dry runs
  • owlsql_undo and owlsql_history: revert any recent write
  • owlsql_tables and owlsql_describe: the schema, foreign keys and triggers
  • owlsql_dump: a full local backup
  • owlsql_status: connection, version, privileges, write mode

FAQ

Is it safe to let an AI agent near my production database?

With raw credentials, not really: one bad statement and the data is gone. OwlSQL is built for exactly that worry. The agent never gets your credentials, writes are off until you turn them on, every write is saved first so it can be undone, and anything destructive waits for you to click Allow. And before the agent does anything big, make a backup.

Can the agent approve its own risky writes?

Not while OwlSQL is open: approvals happen in the app, and the agent's own "confirm" is ignored. It also can't change OwlSQL's settings: writes on or off, approval rules and connections can only be changed in the app or a terminal. If you set a database to Only approve here, risky writes simply wait until you open OwlSQL.

What happens when OwlSQL is closed?

Agents can still read, and make writes that aren't risky (those are still snapshotted and undoable). For risky ones it depends on the database's setting: Only approve here makes them wait until you open the app; the other setting lets the agent show you the preview in chat and ask.

Does my database password reach the AI?

No. You type it into the OwlSQL app (or a hidden terminal prompt). It's stored encrypted with your Windows account and used only to connect. The agent's tools never return passwords or bridge tokens.

Is the PHP bridge a security risk?

It only answers HTTPS POST requests that carry a 256-bit token. The file stores just a SHA-256 hash of that token, and anything without it just gets "404 Not Found". The file name is random too, so nobody finds it by guessing. Treat the token like your database password: OwlSQL keeps it encrypted locally. You can limit the bridge to your IP address, and deleting the file revokes access instantly.

What can't be undone?

A single statement that changes several tables, an UPDATE on a table with no primary key, cascades more than one level deep, and changes larger than the snapshot limit (100,000 rows, adjustable). OwlSQL says "no undo" and asks before running any of these. Changes made by triggers in other tables aren't captured either, and OwlSQL lists a table's triggers so you know.

Does it work with WordPress?

Yes. WordPress runs on MySQL or MariaDB, so add the database named in wp-config.php. It's handy for fixing options, posts and WooCommerce data without clicking through phpMyAdmin.

Which agents does it work with?

Anything that speaks MCP: Claude Code, Claude Desktop, Cursor, Codex, Windsurf and more. The app connects the first three in one click and gives you the config for the rest.

Mac or Linux?

The app is Windows-only for now. The command-line tool and MCP server run anywhere Node.js does, and the npm package is coming soon.

What does it cost?

Nothing for one database: Free has every feature. For more than one, OwlSQL Pro is a one-time $49 with unlimited databases and updates for life.

coolFTP. Your agent changed the database; now let it ship the code. coolFTP deploys to any SFTP or FTP host and undoes a bad deploy.

woodpeckerDig. Is the bug in the code, not the data? woodpeckerDig shows Claude what your program said: logs, errors and stack traces.

magpieSnap. OwlSQL shows Claude your data. magpieSnap shows it what you see: press Print Screen, box it, send it.