Agentsql

Natural Language to SQL for MySQL: Ask Your MySQL Database in Plain English

Connect Agentsql to MySQL or MariaDB with a read-only user, ask in plain English, and get the SQL, the chart, and the answer in one pass.

See pricing

Read-only by design · shows the SQL every time · never trains on your data

Connected · demo_shop · Postgres · read‑only

Ask your data a question:

›_

Writing SQL… Running (read‑only)… SQL Agentsql wrote

Refine: refined ✓

Click a question. Agentsql writes the SQL, runs it read-only, and answers.

Direct answer

Natural language to SQL for MySQL lets anyone on your team ask a MySQL database a question in plain English and get a real answer. Agentsql connects with a read-only MySQL user, writes the query against your actual schema, runs it, and returns a chart, a result table, and a one-line answer. The SQL it wrote is shown with every result, so the number is checkable rather than something you take on faith.

Why teams do this

MySQL runs an enormous share of the ecommerce and SaaS applications people ask questions about, and the schema is usually the one the app grew into, not a clean analytics model. That is exactly where non-engineers get stuck: they know the question, but not which of four order tables holds the truth. Agentsql grounds itself in your live schema, writes the join, and shows it. Your engineers stop being a query service, and the people closest to the business get their own answers.

What you get back

  • The SQL. The exact MySQL query Agentsql wrote, on screen, every time.
  • The result. A table of rows straight from your database, not a summary of a summary.
  • The chart. The right visual for the shape of the answer.
  • The answer. One plain-English line you can paste into Slack and defend.

›_ connect it safely

Connect MySQL read-only.

Give the tool its own read-only MySQL user rather than reusing the application account:

  1. 1

    Create a dedicated user for the tool, for example an 'agentsql' user with its own password.

  2. 2

    Grant only SELECT on the database or the specific tables it should read.

  3. 3

    Do not grant INSERT, UPDATE, DELETE, DROP, ALTER, or any administrative privilege.

  4. 4

    Point the user at a read replica if you have one, so analytical queries stay off the primary.

  5. 5

    Require TLS on the connection and restrict the user to the host or network range you expect.

  6. 6

    Add the connection in Agentsql. From that point every query it issues is a read.

The boundary is enforced by your database, not by our promise. Read more about how Agentsql stays read-only by design, or how it connects to your database.

›_ ask it anything

Questions you can ask MySQL in plain English.

Type the question the way you would ask a teammate. Agentsql writes the MySQL query, runs it read-only, and shows you both the SQL and the answer.

Plain-English question What the SQL does
What were our top 10 products by revenue last quarter? Joins order lines to products, sums revenue, ranks and limits.
How many orders were refunded in the last 30 days? Filters orders by refund status over a rolling date window.
What is the average order value by customer segment? Groups orders by segment and averages the order total.
Which customers ordered more than three times this year? Counts orders per customer with a HAVING clause on the count.
Show me abandoned carts by day for the last two weeks. Buckets carts with no matching order by day.

›_ the honest comparison

Four ways to answer a MySQL question.

Every option below is legitimate. The right one depends on who is asking and how fast they need the number.

Approach Who can use it Time to an answer The SQL Safety note
Write SQL in a MySQL client Engineers and analysts Minutes to hours You write it Depends on the account used
Build a dashboard for every question Data team builds, others read Days per new question Hidden in the dashboard Low, but slow and rigid
Export a CSV and open it in a spreadsheet Anyone Fast, then stale immediately None Data leaves the database
Agentsql connected read-only Anyone on the team Seconds Written, run, and shown to you Read-only user, no writes possible

›_ frequently asked

MySQL questions, answered.

Can AI write MySQL queries?

Yes. An AI grounded in your real MySQL schema writes correct SELECT queries, including joins across the tables your application actually uses. The accuracy depends on schema awareness rather than clever prompting. Agentsql writes the MySQL query, runs it read-only, and shows it with the answer so you can confirm it used the right tables.

How do I query MySQL without knowing SQL?

Connect a natural-language analyst to MySQL with a read-only user and ask your question in plain English. Agentsql translates it into MySQL SQL, executes it, and returns a chart, a table, and a written answer. You get the result without opening a client, and the query stays visible for anyone who wants to check it.

Does it work with MariaDB and Amazon RDS?

Yes. MariaDB speaks the MySQL protocol, and managed MySQL such as Amazon RDS or Aurora connects the same way as a self-hosted instance. You provide a read-only user and a host the tool can reach, and allow the connection through your security group or firewall rules.

Will running queries slow down my application database?

Analytical queries can compete with application traffic, which is why the standard practice is to point read-only tools at a replica. If you connect directly to the primary, keep the tool on a read-only user and use query timeouts. Agentsql only issues reads, so it can never lock rows for a write.

What if my table and column names are cryptic?

It still works, but naming drives accuracy. When a column is called col_4, no tool can know it means lifetime value. Agentsql shows the SQL it wrote, so you immediately catch a wrong table choice, and clearer names or a short description of the key tables lift accuracy considerably.

Ask MySQL your first question.

Connect read-only in minutes. Every answer arrives with the SQL that produced it.