AI2sql is a SQL assistant that turns a plain-English request into SQL for your schema, then explains, fixes, formats, or runs it. The homepage says it reads the live schema so column names are yours, and that read-only is enforced before a statement reaches the database. You can point it at several warehouses and engines, or use a desktop Connector when the database is on localhost. A Free plan and a 7-day trial sit next to Start, Pro, and Team prices, while the gateway page publishes a separate monthly list.
Official website · ai2sql.io
AI2sql fits someone who knows the question and needs SQL in the dialect of a database they can connect. The homepage says a general chat is enough when you can paste the schema, and that the gap opens when the database is real. Two free caps disagree: 3 queries a day on a demo database, and 5 SQL requests a day on the MCP page. Paid plans are Start ($9/month), Pro ($19/month) and Team ($39/month). The trial charges $0 today, but a card is required to start it.
AI2sql turns a plain-English request into SQL for your schema, fixes failing queries and explains existing ones. Generate returns SQL in the dialect you picked, using real table and column names. Explain walks a query clause by clause. Optimize returns a rewrite and a reason. Fix covers syntax, dialect mismatches, and wrong column names. Format adjusts casing and indentation. Run executes on a live read-only connection and shows the rows. AI2SQL reads the live schema, so joins and column names are yours, not a textbook's. The homepage says a general chat is enough when you can paste a small schema, and that the gap opens when the database is real and someone will act on the rows.
Official documentationThe connect step names Postgres, MySQL, SQL Server, Snowflake, BigQuery, MongoDB, and Oracle, with read-only credentials encrypted at rest. A second list adds Redshift, SQLite, and Firebird for people facing several dialects. The databases page splits live connectors, which connect and execute, from dialect tools that generate, explain, optimize, and fix. SQLite, MariaDB, Redshift, and ClickHouse appear on the dialect side. A name there is not automatically a live connection. Read-only is enforced before the statement reaches your database, not requested politely in a prompt. Writes, DROP, and DDL are refused by default. On the MCP path only a single SELECT or WITH runs, and writes, DDL, and multi-statement batches are rejected on the server, capped at 1,000 rows and 10 seconds. The pages do not describe a control that allows writes.
Official documentationThe MCP page hosts a server for Claude, ChatGPT, Cursor, and VS Code. You sign in, and the assistant writes SQL on the real schema and runs it read-only. Live querying there is PostgreSQL, MySQL, MariaDB, and SQL Server. Free on that page is schema browsing plus 5 SQL requests a day, shared with the web app. Running queries against a connected database is part of the paid plans. The gateway is a separate agent endpoint: read-only, rate-limited, logged, and revocable, with PostgreSQL live and MySQL described as rolling out. Its prices are not the SQL list. The Connector is for localhost or a private address. A small app reads names on your machine. The page says credentials, rows, and connection details stay there, while the question and the table names you pick are sent. It names SQL Server, PostgreSQL, and MySQL on Windows, macOS, and Linux, and generations count against your plan. The desktop page still says to sign in, even though its zero cloud dependency.
Official documentationRole notes on the homepage stay concrete. An analyst asks in English and reads rows without leaving the page. A developer pastes a slow or rejected query and gets an explanation, a rewrite, and a fix. An agent gets a governed MCP endpoint, read-only by default, with queries logged and keys scoped per agent. A learner is told each generated query includes an explanation. A shared query library is marked as present, without a seat count. The gateway says plans differ by connections, audit retention, and team features, and that the free tier has a fair-use call cap it does not number.
Official documentationA suggested analyst pass uses the demo database or a read-only connection and asks for one result in English. Read the SQL before Run. Names should come from your schema, and the dialect from the connection you picked. If a table looks wrong, Explain is the documented reading of each clause.
A suggested developer pass pastes the statement that fails, or the one that is slow, and uses Fix or Optimize instead of starting over. Fix is described as covering syntax, dialect mismatches, and wrong column names. Keep the original beside the rewrite. That comparison is the suggested check before anything leaves the read-only path.
A suggested agent setup uses the hosted MCP path rather than a password pasted into a local file. Expect a single SELECT or WITH, with the row and time bounds on the MCP page, and a key you can revoke. The suggested check is the audit log the gateway says it keeps.
A suggested Connector session runs on the computer that already reaches the database, with no port opened. Load the schema and ask in English. Generations count against the plan, including free plans, within their limit. The page says rows stay on the machine and that the question plus chosen table names are sent.
Read both caps: 3 demo queries a day, or 5 MCP requests a day. The paid trial still requires a card.
Use a named live engine with read-only credentials, or the Connector for localhost, SQL Server, PostgreSQL, or MySQL.
Generate, Explain, Fix, or Optimize first. Treat the statement as unreviewed until you have read it.
Run only where writes, DROP, and DDL are refused. The MCP path rejects them on the server.
Homepage figures for Free, Start, Pro, and Team are below. The gateway list is separate and is quoted in the caveat.
Demo questions or MCP schema browsing.
Not verified.
Daily cap, two figures on the site.
The entry paid SQL plan.
$9.
Per month, after a 7-day trial.
The middle SQL plan, not gateway PRO.
$19.
Per month, after a 7-day trial.
The highest SQL plan on the homepage.
$39.
Per month, after a 7-day trial.
A card is required to start the 7-day trial. $0 is charged today, and you can cancel in one click before it ends. Gateway lines show PRO $29 per month and TEAM $99 per month, plus a free connection with an unnumbered fair-use cap. No annual SQL price was published. Review-site amounts were not used.
You can paste a small schema and need one query.
The homepage says a general assistant is fine when you can paste the schema. Choose ChatGPT for that pasted case.
Both appear, and they differ. The homepage FAQ says the Free plan includes 3 queries a day on a demo database. The MCP page says 5 SQL requests a day with schema browsing. Paid plans add a 7-day trial.
SourcePaid plans are Start ($9/month), Pro ($19/month) and Team ($39/month). The MCP page says those paid plans add run_query on connected databases. No annual price is shown on the public pages.
Source$0 is charged today, but a card is required to start it, and you can cancel in one click before the trial ends. The page says you then pay nothing. It does not describe a trial without a card.
SourceThe connect step names Postgres, MySQL, SQL Server, Snowflake, BigQuery, MongoDB, and Oracle. The MCP page limits live querying to PostgreSQL, MySQL, MariaDB, and SQL Server. Other engines on the databases page are listed for generation and repair, not necessarily for a live run.
SourceRead-only is enforced before the statement reaches your database. Writes, DROP, and DDL are refused by default. The MCP path allows a single SELECT or WITH and rejects writes, DDL, and multi-statement batches on the server. No write switch is documented.
SourceThe Connector runs on the machine that can already see the database, because the cloud product has no route to localhost. Credentials and rows are said to stay local. The question and chosen table names are said to be sent. Generations count against your plan.
SourceThe product FAQ says 3 queries a day on a demo database. The MCP page says 5 SQL requests a day, shared with the web app, and puts connected run_query on paid plans.
SourceThey do not state a license for generated SQL. The gateway mentions audit history, including 7 days on its free tier, and says retention differs by plan. A full retention table is not in the public text.
SourceOct 6, 2026 · NavHunt editorial
NavHunt did not run AI2sql. No database was connected, no trial card was entered, and no SQL was generated or executed. Caps and prices come from AI2sql pages reviewed on 6 October 2026. This description is based on AI2sql's official materials reviewed on 2026-10-06, including AI2sql product page, MCP server, AI2sql Gateway, Local Connector.
Connect a read-only schema, or use the demo database, and cancel the trial before the card is charged.