Supported Databases
DatabaseMCP provides MCP-oriented performance investigation workflows across major database engines—covering on-premises, self-hosted, and managed cloud deployments. The same investigation model applies regardless of which engine is causing the incident.
SQL Server and Azure SQL
Microsoft SQL Server and Azure SQL Database share a common diagnostic surface through DMVs, Query Store, and wait statistics. Investigation workflows cover wait analysis, blocking, query plan review, and resource utilisation for both on-premises and managed cloud instances.
- SQL Server performance investigation — on-premises and hosted SQL Server environments
- Azure SQL Database performance investigation — managed cloud, elastic pools, and DTU/vCore tiers
PostgreSQL
PostgreSQL investigation covers slow query analysis through pg_stat_statements, autovacuum health, lock contention, connection pressure, and checkpoint behaviour. Cloud deployments add RDS and Aurora-specific infrastructure metrics to the investigation workflow.
- PostgreSQL performance investigation — self-hosted and general PostgreSQL
- PostgreSQL RDS performance investigation — Amazon RDS for PostgreSQL
- PostgreSQL Aurora performance investigation — Amazon Aurora PostgreSQL
MySQL and MariaDB
MySQL and MariaDB investigation covers InnoDB buffer pool health, slow query patterns, lock contention, replication lag, and connection saturation. Aurora MySQL adds its own storage architecture diagnostics and Performance Insights data.
- MySQL performance investigation — self-hosted MySQL
- MySQL RDS performance investigation — Amazon RDS for MySQL
- MySQL Aurora performance investigation — Amazon Aurora MySQL
- MariaDB performance investigation — self-hosted and managed MariaDB
Oracle
Oracle investigation uses wait event analysis, AWR and ASH data, top SQL review from v$sql, and segment and space monitoring to diagnose both single-instance and RAC environments.
- Oracle performance investigation — single-instance and RAC environments
One investigation model across all engines
Teams managing mixed database estates—SQL Server alongside PostgreSQL, or MySQL alongside Oracle—can apply the same MCP investigation approach across all supported engines. This reduces tool sprawl, improves investigation consistency, and makes it easier to hand off incidents between team members regardless of which engine is involved.
Read the database MCP server overview to understand how the investigation model works across engines.