Ask your SQL Servers anything.Change nothing.
DB24 MCP connects your AI assistant to what DB24 knows about your SQL Server estate. You ask in plain language. It answers from last night's facts about your databases, never from the data inside them.
Early access opens for DB24 customers in November 2026.
Example answer. Real output follows from your DB24 data.
- 100+ Nordic organisations run DB24
- Installed in your environment
- Swedish company, Gothenburg
This is what it took to ask a simple question
SELECT bs.database_name, bs.backup_finish_date, bs.type
FROM msdb.dbo.backupset bs
WHERE bs.backup_finish_date < DATEADD(day, -1, GETDATE())
ORDER BY bs.backup_finish_date DESC;
SELECT j.name, h.run_status, h.run_date
FROM msdb.dbo.sysjobs j
JOIN msdb.dbo.sysjobhistory h ON j.job_id = h.job_id
WHERE h.run_status = 0;
-- then repeat on the other 13 instancesNow it takes a sentence.
Three questions people ask their SQL Servers every week
Which backups failed last week, and why?
One sentence back, with the cause and the instance.

Give me a one-page risk summary for the board.
A page in plain words with the AiQ score, written for people who do not run databases.

Why is the application slow this morning?
The instance, what it is waiting for, and since when.

Every answer comes from data DB24 collected last night. Nothing is guessed.
Nothing is written back. Not one row.
And nothing is read from inside your databases either.
DB24 runs inside your environment and knows nothing about the data in your databases. It only collects facts about them: which instances and databases exist, versions and security updates, whether the backups are complete, jobs, performance and settings, and every change. DB24 MCP gives your assistant a read-only view of those facts. The assistant never connects to your SQL Servers, never reads a row of your data, and cannot change anything. Your data and the AI are completely separate.
The assistant is yours to choose, and so is the model: a cloud service, or a model running on your own servers, whichever your organisation is comfortable with. DB24 MCP gives it the read-only view and nothing more.
Anyone on the team can work with the databases.
The DBA
A faster morning. The checks are already done, the questions are already answered.
The IT manager
A report without asking anyone. Ask for it, paste it, send it.
The board
A page they understand. The AiQ score and the three things that need a decision.

Plain answers about safety
- Does the assistant get access to my databases?
- No. Neither the assistant nor DB24 reads the data inside your databases. DB24 collects facts about them: versions, backups, jobs, performance, settings. The assistant sees only those facts.
- Can it change anything?
- No. The connection is read-only. It cannot run commands, change settings or write to any database.
- Where does the data go?
- DB24 and the facts it collects stay in your environment; the data inside your databases is never read at all. The question you ask, and the answer, go to the assistant you have chosen, so pick a client and a model your organisation is comfortable with. A model on your own servers keeps all of it inside.
- Who can ask questions?
- Whoever holds an API key. Administrators create keys in the DB24 portal under Settings > MCP and choose which tools and SQL Server instances each key can use, and every key has an expiry date. A key does not have to belong to one person; it can be used by a team. Every request is logged with the key, the client and the tool.
- Which AI assistant does it work with?
- Any assistant that supports MCP. You choose the client and the model, cloud or on your own servers, and DB24 MCP gives it the read-only view.
Get early access
Existing DB24 customers go first. If you are not a customer yet, we will show you DB24 MCP on a demo environment.
