Database change tracking · AI-native

Three steps. That's it.

Connect your database, link Claude, and start asking questions about your data — just by asking. No scripts, no binlog wrangling, no spare server.

Point dbtrail at your MySQL instance. Works with RDS, Aurora, Percona — anything that speaks binlog.

Add dbtrail as a remote MCP server in Claude. One URL, one API key — done.

Ask questions in plain English. Query changes, recover deleted rows, audit who did what.

dbtrailconnected

Someone deleted customer 1001. Can you recover it?

dbtrail · recoverpk=1001

Found it. Here's your INSERT — ready to run.

Step 3 in action

Just talk to your database

Once Claude is connected, ask anything. Here are real examples of what people ask every day.

Query

“Show me all DELETEs on the users table in the last hour”

“What changed on order 12345?”

“Which table had the most DELETEs this week?”

Recover

“Generate recovery SQL for customer 1001 that was deleted”

“Recover the orders table to how it looked yesterday at 3pm”

“Restore user 42 and all their child records”

Audit

“Who touched order 5001?”

“What SQL did root run in the last hour?”

“Were there any ALTER TABLEs on the orders table recently?”

Documentation

Guides, API docs, and everything else you need once you're up and running.

Add your first server and start tracking changes in under 5 minutes.

Set up Claude as your AI-powered database assistant via MCP.

Authentication, query, recover, and status endpoints.

Every tool available when Claude connects to your dbtrail server.

Point-in-time recovery, foreign keys, and best practices.

Common issues, binlog configuration, and connectivity fixes.