Bolt.new AI and MySQL integration: Step-by-Step Guide 2025

To integrate Bolt.new with MySQL, you simply build a normal backend inside Bolt.new (usually Node.js) and connect to MySQL using a standard MySQL driver with environment variables for credentials. Bolt.new doesn’t have a special or proprietary database connector — you use the same SDKs and patterns you would use in any local project. The integration works because Bolt.new runs your backend code in a sandboxed container, and that container can open outbound connections to your remote MySQL server. You store your DB credentials in Bolt.new environment variables, import a MySQL client, create a connection pool, and use it in your API routes.

 

What “Integrating MySQL with Bolt.new” Actually Means

 

You’re not integrating “Bolt AI” with MySQL. You’re integrating the backend you build inside the Bolt.new workspace with MySQL, the same way you would in any full-stack project: using a MySQL client library and environment variables.

Bolt.new provides:

• A browser-based editor (your code workspace)
• A runtime to execute your backend (Node.js)
• Environment variable settings so you can store DB credentials safely

You provide:

• A remote MySQL database (PlanetScale, AWS RDS, ClearDB, your server, etc.)
• Connection credentials (host, user, password, database)
• Your backend code using a MySQL client library

 

Environment Variables You Need

 

In Bolt.new, open the “Environment Variables” panel and set:

• MYSQL\_HOST
• MYSQL\_USER
• MYSQL\_PASSWORD
• MYSQL\_DATABASE

These values come from your actual MySQL provider.

 

Install MySQL Client in Bolt.new

 

npm install mysql2

 

mysql2 is the most commonly used modern driver. It works in Bolt.new’s Node runtime without issues.

 

Create a DB Connection (Node.js)

 

Inside Bolt.new, create something like /lib/db.js:

// lib/db.js
import mysql from "mysql2/promise";

// Create a connection pool (recommended)
export const pool = mysql.createPool({
  host: process.env.MYSQL_HOST,     // your environment variables
  user: process.env.MYSQL_USER,
  password: process.env.MYSQL_PASSWORD,
  database: process.env.MYSQL_DATABASE,
  waitForConnections: true,
  connectionLimit: 10,              // safe default for small dev setups
  queueLimit: 0
});

 

Use the DB Inside an API Route

 

Example: /api/users.js

// api/users.js
import { pool } from "../lib/db.js";

export default async function handler(req, res) {
  try {
    const [rows] = await pool.query("SELECT id, name FROM users"); // simple query
    res.json({ success: true, data: rows });
  } catch (err) {
    res.status(500).json({ success: false, error: err.message });
  }
}

 

This route runs in Bolt.new’s backend runtime and communicates with your external MySQL instance over the network.

 

Important Notes

 

• Bolt.new cannot host your MySQL database. You must use an external DB.
• Outbound connections only. Your MySQL server must be reachable from the internet (or via a public connection string).
• No local sockets. Use TCP hostnames, not unix sockets.
• Use connection pools. Bolt.new spins up processes on demand; pooling avoids repeated handshakes.

 

How to Harden This Later (Real Deployment)

 

• Move environment variables into your actual deployment platform (Vercel, Fly.io, etc.).
• Enforce SSL connections to MySQL.
• Restrict DB user permissions (never use a root account).
• Use a managed MySQL host that provides backups and logs.

But inside Bolt.new, during development, the workflow is exactly the same — you code normally, provide env vars, and connect through mysql2.