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.
Works on shared hosting too: Hostinger, HostGator, Bluehost, GoDaddy, SiteGround, any cPanel box, or your own server.
› 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
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.
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.
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.
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.
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.
User and privilege changes, DROP DATABASE, reading or writing files on the server, global settings and multi-statement tricks are refused outright.
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.
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.

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

The same session afterwards: the fix ran, the price change was denied.
OwlSQL is a desktop app, not just a plug-in. Agents' calls run inside it, so you always know what touched your data.
.sql file in one click, optionally portable to older MySQL and MariaDB.newVersion 0.2.0 for Windows 10 and 11 (64-bit). Free for one database; Pro unlocks unlimited databases.
Installs OwlSQL with a Start menu entry and desktop shortcut. Recommended.
Download installer 77 MBOne file, nothing to install. Run it from anywhere, even a USB stick.
Download portable 77 MBOwlSQL 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.
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.
Your one database, with every feature. No account, no nag.
For anyone with more than one database: freelancers, agencies, a few sites of your own. Per person, up to three machines.
Secure checkout by Stripe. Your key arrives by email within a minute. Lost it? Get your keys re-sent.
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.
If your hosting panel has a "Remote MySQL" page, add your IP address there and connect straight in. Optional TLS.
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.
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.
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 write | What OwlSQL saves first | What undo does |
|---|---|---|
UPDATE / DELETE | The rows its WHERE matches, locked so nothing else can change them first | Puts the old values back by primary key; re-inserts deleted rows |
INSERT | The new rows | Removes exactly those rows |
REPLACE, upserts, key changes | The table, keeping only the rows that changed | Applies the reverse of the change |
| Foreign-key cascades | The rows in other tables that cascade with it | Restores them in the same transaction, parents first |
ALTER, DROP, TRUNCATE | The table's full definition and every row | Rebuilds the table and reloads it |
CREATE TABLE / RENAME | The names | Drops 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.
About five minutes, and no terminal needed.
Download the installer and run it. Everything is included; you don't need Node.js or anything else.
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.
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.
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.
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.
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
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.