MySQL in Claude, ChatGPT and any MCP client. For your whole team.
Ask your MySQL or MariaDB tables questions in plain language, read-only unless you allow changes. One technical login in Loopthink, one login per person, roles per tool and an audit entry for every call.
Free for 2 connectors, no card · Pro €19 · EU-hosted · 3 read tools, 1 write tools off by default
“How many orders did we get per month this year?”
Orders per month since July, from the orders table:
| Month | Orders | Revenue |
|---|---|---|
| July | 1,284 | €212,480 |
| August | 1,107 | €183,950 |
| September | 1,392 | €236,710 |
| October | 1,451 | €248,300 |
- read-only
- masked
Shops, CRMs, booking systems and a lot of in-house tools keep their data in MySQL or MariaDB. Getting a number out of it usually means asking the one colleague who writes SQL, or exporting a table to a spreadsheet.
With the MySQL connector, Sales, Finance and Management ask in Claude or ChatGPT, or in the ChatGPT app "MySQL by Loopthink". The assistant looks up the tables and columns, writes one SELECT and answers from the rows. Loopthink holds one database login, every person signs in with their own identity, and every statement is logged under their name.
Three read tools list the tables, describe a table and run a query. Every query runs inside a read-only transaction, so a statement that would change data is refused by the database itself. The fourth tool, execute, changes rows one statement at a time and stays off until you allow changes on the connection and grant it to a member group.
- Management
“How many orders did we get per month this year?”
Answered by
query - Sales
“Who are our ten largest customers by revenue?”
Answered by
query - Operations
“Which products have not been ordered in the last 90 days?”
Answered by
query - Finance
“Compare this quarter's revenue with the same quarter last year.”
Answered by
query - Data
“Which tables hold customer data, and which columns do they have?”
Answered by
describe_table - Support
“Set the status of order 4711 to shipped.”
Answered by
execute
What the MySQL connector can do.
| Tool | What it does | Access | Default |
|---|---|---|---|
| list_tables | Lists the tables and views of the database with their schema. Start here, then call describe_table for the ones you need before writing SQL. | Read | On |
| describe_table | Returns the columns of one table: name, data type, whether it can be empty, and its default. Call it before query, so column names are read and not guessed. | Read | On |
| query | Runs one read-only SQL SELECT and returns the rows. It runs inside a read-only transaction, so a statement that changes data is refused by the database. | Read | On |
| execute | Changes data with one SQL statement: INSERT, UPDATE or DELETE. Confirm the statement with the user before you run it. | Write | Off |
Write tools are off for every role until you switch them on, one tool for one role. The names are what the model sees; it also gets the full parameter description of each tool.
Setting up access to MySQL.
Five minutes, once. Nobody on your team ever sees the credentials.
- 1
Create a user of its own for the assistant: CREATE USER 'loopthink_reader'@'%' IDENTIFIED BY '…';
- 2
Let it read, and nothing else: GRANT SELECT ON crm.* TO 'loopthink_reader'@'%'; (replace crm with your database).
- 3
Only when the assistant should also change data: grant INSERT, UPDATE and DELETE on the tables it may change, and allow changes on the connection.
- 4
Make sure the database is reachable from the internet. For a hosted database (AWS RDS, Azure, Google Cloud SQL, your hoster) keep "Encrypt the connection (SSL)" ticked.
- 5
In ChatGPT, add "MySQL by Loopthink": right after sign-in a form asks for the fields below, logs in once and lists the tables. In the Loopthink web app, tick "Schema and read-only query tools" on the connection instead.
- 6
In Loopthink, add MySQL from the catalog and enter the password. It also asks for host, port, database and user. Your team sees the tools a minute later.
Every query runs inside a read-only transaction, so even a user with more rights cannot change data through it. The user that may only read is the second safeguard, and the one that is entirely in your hands.
What we suggest masking in MySQL.
Customer tables carry names, e-mail addresses, phone numbers and bank details in columns of their own. Rows come back with the column names as fields, so a masking rule on a field such as email or iban removes or masks that column for a role, and the e-mail and IBAN patterns catch those values wherever they appear in a row. Give Finance the full rows and other roles the totals.
- phone
- iban
- name
- address
MySQL and Loopthink
- Can the assistant change or delete data?
- Not with the query tool: every query runs inside a read-only transaction, and MySQL itself refuses a statement that writes. Changes need the execute tool, which is off until a workspace admin allows changes on the connection. Even then it runs one INSERT, UPDATE or DELETE per call and asks you first, UPDATE and DELETE need a WHERE clause, a statement that would change more than 1000 rows is rolled back, and the schema cannot be changed.
- Does it work with MariaDB?
- Yes. MariaDB speaks the same protocol, and the connector treats it like MySQL: same fields, same tools, same read-only transaction. Hosted MySQL works too (AWS RDS and Aurora, Azure, Google Cloud SQL, most web hosters), as long as it accepts a user with a password from the internet.
- How does it know our tables and columns?
- It asks the database: list_tables first, then describe_table for every table the question touches, and only then it writes the SELECT. Nothing about your schema has to be described beforehand.
- How much comes back per question?
- 100 rows unless the assistant asks for more, at most 500 per query, and a query is stopped after 20 seconds. That is why the assistant counts and sums in SQL instead of reading every row.
- Is this the same as the ChatGPT app "MySQL by Loopthink"?
- Yes. The app is the quickest way in from ChatGPT: you add it, sign in, and a form on our page asks for host, port, database, user and password, then logs in once to test it. In ChatGPT the tools are called mysql_list_tables, mysql_describe_table, mysql_query and mysql_execute. Claude and other MCP clients reach the same database through your Loopthink connector, with the same roles and the same log.
- Does the database have to be reachable from the internet?
- Yes. Loopthink connects from the cloud, so the host has to answer from outside. Hosted databases usually do. Use a user that may only read, and keep the connection encrypted.
- Does every team member need their own MySQL account?
- No. Loopthink holds one key or token for MySQL. Your people sign in to Loopthink with their own identity, and every call to MySQL is logged under their name. Seats in MySQL stay where they are today.
- Where does the MySQL key live?
- In Loopthink, encrypted, in the EU. It never reaches the AI client and never reaches the people using the connector. Rotate it in MySQL whenever you like and paste the new one once.
- Can somebody write to MySQL from the chat?
- Not unless you switch it on. Write actions are a separate row in the permission matrix and are off for every role by default. If a role needs one write tool, you grant that one tool to that one role.
- What does the model see?
- The result of the tool call, after masking. Fields you mark as personal, such as emails, names or card details, are masked before the answer travels to the AI client. The model gets the numbers, not the people.
- What does it cost?
- Free for one person and two connectors, no card. Pro is €19 a month for up to five people and every connector on the site, with roles, field masking and a 30-day audit. Team is €49 for ten people and adds your own REST APIs and SQL databases, your own domain and your own identity provider. No call needed.
Stuck, or a tool you need is missing? A person who knows this connector answers within one working day.