SIXTA Connect MCP Server
Database Reliability Engineer-grade SQL analysis inside any MCP client
Documentation
Free in beta · MySQL & PostgreSQL · Claude · Cursor · VS Code · Windsurf · Codex
Ship SQL like you have a DBA
The database engineer you'd call at 11pm, on demand.
No DBA on your team, or one who's far too busy to ask? SIXTA Connect reviews your queries, plans, and migrations right inside your editor. Paste the SQL: it tells you what's wrong, how bad it is, and gives you a safer version to run. Or tells you it's clean. No database access, no tickets, no waiting.
Get your free key
Add it to your editor once, in about 30 seconds. Email sign-in, no password.
You know the moment your cursor hovers over Run and you think, "this probably won't lock the whole table"? That's where SIXTA sits. Paste it first.
0%
unsafe migrations approved when connected, every model tier (0 of 75 trial runs each). On its own a model approves 5–7%.
75% → 97%
a small model's critical-issue recall, on its own vs connected.
~30% cheaper
than asking a frontier model directly, at matching accuracy and zero unsafe migrations.
Measured with SIXTA and without, averaged across runs of our 129-case suite. See how we measure →
Ask it what you'd ask a DBA
“Is this migration safe?”
The exact lock, what it blocks, and a safe rollout for your engine and version.
“Why is this query slow?”
The anti-pattern or plan problem, with a ready-to-run, self-checked rewrite.
“Can I drop this index?”
Which indexes are dead weight, with the exact DROP and what it saves.
Paste any SQL artifact. It picks the right tool.
A slow query
The index it needs, plus a self-verified rewrite.
An EXPLAIN plan
Full scans, spilling sorts, bad estimates.
A migration
Lock level and the safe online path, version-aware.
A slow query log
Ranked by total time: where your DB time goes.
A deadlock dump
The lock cycle, the victim, the ordering fix.
Schema DDL
Redundant indexes to drop, with the statements.
An ORM trace
N+1 patterns with the eager-load fix.
SQL to review
GRANT ALL, SECURITY DEFINER, CVV storage.
AI sounds confident about SQL. Your database isn't impressed.
Let your assistant draft SQL freely. SIXTA sits between the model and your database, putting every query, plan, and migration it suggests through the same deterministic checks a DBA would. In our offline tests, that takes "unsafe but marked safe" decisions to zero. A very fast junior dev, with a very strict reviewer.
Every report signs its work.
Every rewrite is self-checked.
If we can't prove it, we won't call it safe.
Every migration you run bets your reputation on what it does in production. SIXTA is built to be the part of your stack that keeps its promise: named findings, a severity, the stakes in plain numbers, and exactly what to change. Deterministic, grounded in the plan, and honest when it doesn't know. You don't get vibes. You get a report.
In your editor in three steps
- 1. Add the SIXTA URL to your editor.
- 2. Sign in once when it pops up. One click with Google, or an email link.
- 3. Ask about any SQL. It calls SIXTA on its own.
Add this one URL as a remote MCP server. Your editor opens a sign-in once (email link, no password), then you're connected. Nothing to copy and paste.
Cursor
One click. Cursor opens its add-server dialog pre-filled, then you sign in:
Or add https://connect.sixta.ai/mcp by hand as an MCP server (just the url, no headers).
Claude Code
claude mcp add --transport http sixta https://connect.sixta.ai/mcp
Claude web / Desktop
Settings → Connectors → Add custom connector → paste the URL → sign in.
VS Code / Windsurf
Add https://connect.sixta.ai/mcp as an MCP server (just the url, no headers). The sign-in opens automatically.
Prefer an API key? (clients without the sign-in popup, or CI)
Create a free key and paste it into the connector config. Works in any MCP client.
Claude Code
claude mcp add --transport http sixta https://connect.sixta.ai/mcp --header "Authorization: Bearer "
Cursor: ~/.cursor/mcp.json
{ "mcpServers": { "sixta": { "url": "https://connect.sixta.ai/mcp", "headers": { "Authorization": "Bearer " } } } }
VS Code (Copilot): .vscode/mcp.json
{ "servers": { "sixta": { "type": "http", "url": "https://connect.sixta.ai/mcp", "headers": { "Authorization": "Bearer " } } } }
Windsurf: ~/.codeium/windsurf/mcp_config.json
{ "mcpServers": { "sixta": { "serverUrl": "https://connect.sixta.ai/mcp", "headers": { "Authorization": "Bearer " } } } }
Codex CLI: ~/.codex/config.toml
experimental_use_rmcp_client = true
[mcp_servers.sixta] url = "https://connect.sixta.ai/mcp" bearer_token_env_var = "SIXTA_KEY" # then in your shell: export SIXTA_KEY=
Claude web / Desktop (add a custom connector)
The connector UI can't send headers, so the key goes in the URL:
Your key goes in the config above. Get a free key → if you don't have one yet.
Safe to try, safe to trust
No connection to set up. The free Connect tier works from the SQL you paste: no database credentials, no access to your systems. Connecting to your live database for data-grounded analysis is the paid SIXTA platform.
Nothing stored. What you paste is analyzed in memory and never persisted. See the data-handling statement.
Deterministic verdicts. The same artifact gives the same answer every time, from version-aware rules. The model relays the findings, it doesn't invent them.
Self-checked fixes. Every rewrite is re-analyzed against the same rules before it reaches you, and flagged if it isn't clean.
We built SIXTA Connect so you don't have to tiptoe around SQL. The goal: turn the developer who inherited the database by accident into the one their team trusts with the scary stuff.
Ready for a DBA that watches your live systems?
SIXTA Connect is free for any SQL you bring it. The full SIXTA platform is an autonomous DBRE that joins your team: it plugs into your live databases and observability, investigates incidents on its own, and posts root cause and a fix to Slack for your approval. From $40/db/mo.
See the SIXTA platform →
Free while in beta: best-effort, no SLA; limits may change or it may be discontinued at any time. The AI synthesis in sixta_diagnose runs on a limited daily budget; when it's exhausted, SIXTA falls back to its deterministic analysis and the other tools are unaffected. Benchmark figures are from our own 129-case suite, averaged across runs; method on the Benchmarks page.