SIXTA Connect puts a database reliability engineer's toolbox in your editor. You never call these tools by name: connect once, then ask in plain language ("is this migration safe?", "why is this query slow?") and your model picks the right one. Everything works from what you paste; nothing is stored. (Connect Pro's optional live connection is read-only, separate, and off by default.)
claude mcp add --transport http sixta https://connect.sixta.ai/mcp
That is the whole install for Claude Code; the landing page has the one-URL setup for Cursor, VS Code, Windsurf, and Codex. The same tools also power the CI gate, so a verdict you see at your cursor is the verdict your pipeline enforces.
sixta_analyze_queryPaste a query.
The workhorse. Named findings with a severity for the patterns that make queries slow (functions that defeat an index, leading-wildcard LIKE, deep OFFSET) and, just as important, the bugs that silently change which rows come back (a LEFT JOIN filtered in WHERE, NULL comparisons that drop rows). Add the query's EXPLAIN output or the table's CREATE TABLE and the findings get more confident and start recommending concrete indexes. When a safe fix exists, the ready-to-run rewrite is included.
sixta_explain_planPaste raw EXPLAIN output. No query needed.
A plain-language narrative of what the planner is doing, where the cost concentrates, and what to fix: full scans, spilling sorts, nested-loop blowups, row misestimates. Reads PostgreSQL text and JSON, and every MySQL format.
sixta_analyze_workloadPaste a slow query log or pg_stat_statements export.
Your worst queries ranked by total time, not worst single run. Thousands of log lines collapse into a few query shapes, so you see where your database time actually goes and which two or three queries own most of it. Hands the worst offenders straight to the query analyzer.
sixta_detect_n_plus_onePaste an application or ORM query trace.
Finds the classic N+1: one parent query, then the same per-row lookup repeated hundreds of times. Reports each pattern with the framework-specific eager-load fix (Rails includes, Django select_related, Hibernate JOIN FETCH, Prisma include).
sixta_analyze_schema_changePaste a migration or any DDL.
The tool the CI gate is built on. Whether an ALTER locks the table depends on your exact engine version, and that is where answering from memory ships outages. You get an explicit safety verdict per statement, the exact lock taken and what it blocks, and the safe execution strategy as ready-to-run SQL (CREATE INDEX CONCURRENTLY, NOT VALID plus VALIDATE, gh-ost / pt-osc). With Connect Pro, verdicts are graded against your real table sizes instead of guesses.
sixta_rewrite_queryAsk for the fix to a flagged query.
The safe, equivalent rewrite for a known anti-pattern, with any semantics caveat spelled out. Every rewrite is re-analyzed before you see it and reported clean or not, so you are never handed a "fix" that just trades one problem for another.
sixta_review_securityPaste SQL you want reviewed for security or compliance.
A static review for least-privilege violations (GRANT ALL, grants to PUBLIC), injection indicators, weak hashing, and a tight compliance subset such as PCI-prohibited CVV storage. Findings are worded as potential issues to verify, not accusations.
sixta_explain_errorPaste a database error code or message.
The fastest front door. A MySQL error number (1213, 1062...) or PostgreSQL SQLSTATE (40P01, 23505...) becomes the proximate cause, the concrete fix, and the next artifact worth pasting when the error is a symptom of something deeper.
sixta_explain_deadlockPaste a deadlock dump.
Reconstructs the cycle from MySQL's SHOW ENGINE INNODB STATUS or a PostgreSQL deadlock log entry: which transaction held and waited for which lock, the inconsistent ordering that caused it, which one was rolled back, and the fix.
sixta_diagnoseDescribe a symptom, attach whatever you have.
For the vague ones: "p99 spiked after Tuesday's deploy". Bring the symptom plus any artifacts (query, plan, DDL, diagnostics) and get one coherent diagnosis: ranked hypotheses with the evidence for each, and next steps ordered by what they would tell you.
sixta_review_indexesPaste your schema DDL.
Finds the indexes you can drop: exact duplicates, an index on (a) already covered by one on (a, b), and secondary indexes that restate the primary key. Each comes with the exact DROP statement and the write cost it has been adding.
sixta_health_checkPaste diagnostics you run yourself.
Triage for the checkup queries: pg_stat_user_tables becomes a vacuum and bloat assessment graded A to F with ready-to-run fixes; a settings dump becomes a configuration review sized to your RAM, cores, and workload; SHOW ENGINE INNODB STATUS gets deadlock and buffer-pool triage. Called with nothing in hand, it gives you the exact queries to run.
sixta_quickstartNothing to paste yet?
A complete worked example on a realistic gnarly query, so you can see what a SIXTA report looks like before bringing your own SQL.