Live problem drilldown
Ask which servers show the strongest signs of pressure, then investigate sessions, blocking, I/O, waits, queries, alerts or execution plans for the affected systems.
Mini DBA MCP Server lets compatible AI clients query the database performance and monitoring evidence already collected by Mini DBA. Ask questions across an entire server estate from your local AI tool of choice instead of opening every server and assembling the evidence by hand.
A connected AI client can combine several Mini DBA tools in one investigation, moving from a broad question to the evidence behind it.
Ask which servers show the strongest signs of pressure, then investigate sessions, blocking, I/O, waits, queries, alerts or execution plans for the affected systems.
Ask about worsening trends, repeated alerts, capacity pressure or recurring workload patterns that deserve attention before they become a service incident.
Use collected history to explore when a problem started, what changed around the event and whether the same signature has appeared elsewhere.
Support companies and MSPs can ask consistent questions across monitored client estates while keeping each investigation grounded in Mini DBA evidence.
Copy the endpoint from Mini DBA MCP Server settings into a compatible local or managed AI client, then authenticate with a dedicated API key. Your client discovers the database monitoring tools exposed by Mini DBA and can call the relevant tools as you ask questions.
This makes Mini DBA monitoring data available in the AI workflow your engineers already use, subject to that client's MCP support, network access and security policy.
Create separate keys for individual clients or integrations so access can be rotated or removed without disrupting every MCP connection.
Choose which trusted AI clients can reach the MCP endpoint. Monitoring data can include server names, database names, query text and operational history.
Use MCP answers to guide investigation and verify important conclusions against Mini DBA screens, operational policy and normal change control.
Community Edition can expose its available live and historical monitoring tools through MCP, so you can ask an approved AI client about the server it monitors. Community Engines do not evaluate or retain alerts, so Community alert records are not exposed through MCP.
Licensed Engines add their licensed alert data and can monitor the number of database connections included by the licence. In a mixed Console, entitlement is applied by the Engine that owns each monitored server.
Read the MCP Server setup guide or explore the in-page AI Assistant.