VantegrateNative API integrationIntegrate MySQL with AI agentsand ask your database questions in plain English
Metrix, Vantegrate's data agent, connects to your database through the native MySQL protocol: you ask in natural language, the agent turns the question into a query, runs it with a read-only user and gives you the answer with your real data. Your data stays in your MySQL instance.
How the data flows
What does it mean to integrate MySQL with Vantegrate's AI agents?
Integrating MySQL with Vantegrate's AI agents means that Metrix, the data agent, queries your database to answer business questions in natural language, instead of relying on manual reports or on an analyst who writes every SQL query. The connection uses the native MySQL protocol with a read-only user: the agent reads your data without modifying it.
That is different from a fixed decision-tree bot that always gives the same answer. The agent interprets the question, turns it into a query and answers with your real data, from the current state of the database. The information stays in your MySQL: the agent queries it and returns the answer; it doesn't take the database anywhere else. AI comes to your data, not your data to the AI.
What do you want to connect to your MySQL?
Pick what you need and we'll write the message for you.
1 · Pick what to solve
2 · What our team receives
Vantegrate
online
What Metrix queries in your MySQL
The agent works on your MySQL tables in real time: it turns your question into a query, runs it with read-only permissions and returns the answer, without you having to know table names or write SQL.
Tables and operational data
The agent queries your tables and schemas: it turns a request like "show me this month's sales by branch" into a query and runs it against your database, without exporting or copying the data.
Questions in natural language
Your team asks in plain English, not in SQL. The agent understands the intent, builds the query and answers with the number or the list you asked for, without waiting for someone to write the query.
Metrics and trends
On the same tables, the agent calculates business metrics and trends and explains them in natural language, with every figure backed by the current state of your database.
How the integration works, step by step
Vantegrate handles the setup and rollout. Your team authorizes, validates and starts using it.
Discovery and connection
We review your database and its schemas and define the technical connection path over the native MySQL protocol, case by case with your IT team. No scrapers and no fragile bridges.
Read-only user
We create a user with GRANT SELECT limited to the databases and tables it needs, restricted to specific hosts and following the least-privilege principle, as the MySQL documentation recommends.
Business context
We load what each table and each metric means, so the agent understands your data model and turns each natural-language question into the right query.
Validation with real data
We test with real questions against your tables, validate the answers with your data and IT teams, and roll out in phases.
Querying your MySQL live vs. requesting a report by hand
MySQL is one of the most widely used open source relational databases, especially in web applications and e-commerce. Metrix connects to that database through its native protocol and turns your natural-language question into a query, so you get your answer without knowing table names or writing a single line of SQL.
The difference from waiting on a manual report or exporting the data to another tool shows up in every question. The agent reads the current state of your database at that moment, not a copy that goes stale between snapshots. And because it connects with a read-only user, it queries to answer but doesn't modify your database or change its structure.
| Dimension | Manual report or export | Metrix on your MySQL |
|---|---|---|
| Connection | Export, copy or a request to the analyst | Native MySQL protocol, live |
| Authentication | Broad credentials or a manual dump | Read-only user (GRANT SELECT) |
| Reading data | A copy that drifts | Current state of your database, at that moment |
| How you ask | You need to know SQL or wait for the analyst | In natural language; the agent translates |
| Permissions | Broad access | Read-only, minimum tables and restricted hosts |
Comparison of integration patterns; the exact scope and the connection path are defined with your IT team based on your database.
Your data stays in your database: the agent queries your MySQL through the native protocol with a read-only user; it doesn't take the database anywhere else. Every query the agent runs is logged for auditing in your instance.
How the agent's access to your database is scoped
The recommended setup is a read-only user, created with a restricted host and the minimum privileges the use case needs. In MySQL, you do that by granting the SELECT privilege on the specific databases and tables, with syntax along the lines of GRANT SELECT ON database.table TO user, following the least-privilege principle the platform itself documents.
The connection uses the native protocol, which listens on port 3306 by default, with user authentication and encryption in transit. The exact path and the network access rules are validated with your IT team before you start, so the agent reaches only what you authorize and every query is traced for auditing.
About the agent's access: with a scoped SELECT privilege, the agent can read the tables you define but can't write to them or alter the database structure. You can limit exactly which tables it reaches, one table at a time.
You've seen how it connects. Want to walk through your case?
Tell us how your MySQL is set up and we'll tell you what data we need and where the agent connects.
An agent connected to your MySQL vs. a standalone tool
| Standalone AI tool | Agent connected to your MySQL | |
|---|---|---|
| Data source | A copy that drifts | Your source of truth, live |
| Where your data lives | In a third-party system | In your environment, encrypted end to end |
| Result of each operation | Stuck in another app | Written back to your MySQL |
| Permissions and audit | Broad and hard to audit | Least-privilege scope and an audit trail |
| Reaching production | Often stalls as a pilot | Validated, phased rollout |
Why add a conversational layer on top of your database
Third-party figures, each with its published source, to size up the context. None of them is a Vantegrate result.
#2
MySQL is the world's second most popular database in the overall ranking
SELECT
MySQL's documentation recommends least privilege, which for a read-only user means SELECT only
95%
Of generative AI pilots never reach production with measurable business impact
The DB-Engines Ranking is a third-party popularity measure, not a Vantegrate result, and it changes from month to month. The MIT NANDA figure reflects the gap between experimenting with AI agents and running them in production. The port and the network access rules are validated with your IT team before connecting.
Which agents run on your MySQL
The MySQL use case is conversational data querying: the agent reads your database in real time with read-only permissions and answers in natural language, with your data always in your instance.
Metrix
Data agent: your team asks in plain English about sales, inventory, customers or trends, and the agent turns the question into a query, runs it against your MySQL with read-only access and returns the answer, with no static reports and no waiting on IT.
Explore Metrix
Arconte
Document agent: when the data it extracts from invoices and receipts is headed for your MySQL database, it leaves that data structured and available there, ready for the rest of your operations.
Explore ArconteThe integration doesn't take your data anywhere
The principle is simple: AI comes to your data, not your data to the AI. The agent queries your MySQL through the native protocol, with a read-only user you authorize, and runs on certified cloud infrastructure.
- Connection through the native MySQL protocol with user authentication and encryption in transit; no scrapers and no fragile bridges.
- The agent queries with a read-only user (GRANT SELECT): it reads to answer, and it doesn't write or change your database structure.
- Access restricted by host with minimum permissions per table, and every query logged for auditing in your instance.
- The agents run on Salesforce or Oracle Cloud Infrastructure, whose SOC 2 and ISO 27001 certifications belong to those platforms, not to Vantegrate or to your MySQL instance, which you operate and certify.
Frequently asked questions about the MySQL integration
What data and IT teams usually ask before connecting an AI agent to their MySQL database.
Can the agent modify my MySQL database?
Can the agent modify my MySQL database?
Not with the recommended setup. The agent connects with a user that only has the SELECT privilege, with no write access and no structural changes: it queries to answer and doesn't alter anything. You can scope access table by table and restrict the host, following the least-privilege principle MySQL documents. Meet Metrix, the data agent.
Where does my data stay?
Where does my data stay?
In your MySQL database. The agent queries it and returns the answer; the database isn't copied or moved to another environment. The information stays in your instance, the agent reads it with minimum read-only permissions, and every query is logged for auditing. The principle is that AI goes to your data, not your data to the AI.
Which port does the agent use to connect to MySQL?
Which port does the agent use to connect to MySQL?
MySQL listens on port 3306 by default for its native protocol. The exact connection path and the network access rules are validated with your IT team before you start, with user authentication and encryption in transit, so access stays limited to what you authorize.
Can I limit which tables the agent can access?
Can I limit which tables the agent can access?
Yes. The SELECT privilege can be scoped to the specific databases and tables you define, table by table, following the least-privilege principle. The agent reaches only what you authorize with that read-only user, and it doesn't see the rest of the database.
Metrix, the data agent
How the agent turns your question into a query, reads your database and answers in natural language.
Learn moreAll integrations
The full map: the databases, ERPs, CRMs and tools the AI agents connect to.
Learn moreAI agents for enterprises
The map of the Vantegrate suite: sales, marketing, documents, data and logistics.
Learn moreLet's connect AI agents to your MySQL
Tell us how your database is set up and we'll show you what the agent queries, which read-only user and permissions we request, and how querying your data in natural language works. A 30-minute conversation, no commitment.
Francisco Morales, co-founder, takes your call. We reply on WhatsApp within 4 business hours, no strings attached.
