PerformanceMonitor MCP server
Commit Nov 15, 2026Lets an AI client query collected SQL Server and PostgreSQL performance data, alerts, and execution plans for analysis.
Also known as erikdarlingdata/PerformanceMonitor
- Stars
- 536
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 15, 2026
- License
- MIT
What is PerformanceMonitor MCP?
PerformanceMonitor lets an AI client query collected SQL Server and PostgreSQL performance data, alerts, and execution plans for analysis.
Summary generated from the project's README
About PerformanceMonitor MCP server
Analyzing SQL Server and PostgreSQL performance data from inside an AI client is what PerformanceMonitor enables for database administrators and developers. By connecting an AI agent to the built-in MCP server, users can query collected performance metrics, real-time alerts, and execution plans to diagnose database issues. The system offers two distinct ways to operate: Lite, which is a single desktop application for remote on-demand monitoring using local DuckDB and Parquet files, and Darling, a service for continuous 24/7 collection into a central PostgreSQL store.
Depending on the edition used, the AI agent can perform more than just reading reports. While Lite focuses on investigation, the Darling edition allows an agent to take action by changing alert settings, forcing or unforcing Query Store plans, recompiling modules, or even killing sessions. All actions are subject to user-enabled switches to ensure control. This setup works across various environments including on-premises servers, Azure SQL Managed Instance, AWS RDS, and various PostgreSQL versions.
What you can do with it
- 1Remediate database issues automaticallyA developer can task an AI with managing execution plans or terminating problematic sessions.
- 2Manage database alert configurationsUsers can use an AI client to adjust how the monitoring system notifies them of issues.
Written from the project's README. Every use case is checked against a quote from it.
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachableerikdarlingdata/performancemonitor is public and reachablegithub.com/erikdarlingdata/performancemonitor ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-13github.com/erikdarlingdata/performancemonitor ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubSQL Server Performance Monitor
Free, open-source monitoring that replaces the tools charging you thousands per server per year. It includes specialized collectors, real-time alerts, and a built-in MCP server for AI analysis. Nothing phones home. Your data stays on your server and your machine.
If you pay for a monitoring tool now, read the comparison for yours.
Redgate SQL Monitor · SQL Sentry · SolarWinds DPA · Idera SQL Diagnostic Manager · Quest Spotlight · Datadog Database Monitoring · Database Health Monitor
It supports SQL Server 2016 SP2 to 2025. SQL Server 2017 needs CU3 or later. It also supports Azure SQL Managed Instance, AWS RDS for SQL Server, and Azure SQL Database (Lite and Darling). Darling also monitors PostgreSQL. It supports PostgreSQL 14 to 18, plus Amazon RDS, Aurora and Azure Database for PostgreSQL, and makes a best effort on PostgreSQL 10 to 13. See Supported PostgreSQL versions.

Editions
- Lite is a single desktop app that monitors your servers remotely, on demand. Nothing is installed on your server. It stores data in local DuckDB and Parquet files.
- Darling is a service on Windows or Linux that collects 24/7 into a central PostgreSQL store. The Windows viewer and the web dashboard read that store from any seat.
Both editions can hand an alert to an AI agent that you run, and Lite lets the agent read and report. Darling can also let it change alert settings (mutes, custom alert rules and thresholds). On a server, it can force or unforce a Query Store plan or evict a cached plan. It can recompile a module, create or drop a plan guide, or kill a session. Each of these has its own switch per server, and all are off until you turn them on. Darling records every change. A person can undo alert-setting changes, plan forces and plan guide changes. A plan eviction, a recompile or a session kill cannot be undone. Agent dispatch explains the levels.
The Dashboard edition is deprecated. Existing installs keep working, but we recommend Lite or Darling for new deployments. Choosing an edition compares all three.
Each release ships these downloads. For Lite, a Setup.exe and a portable ZIP. For Darling, the service ZIP (with the viewer inside), a Viewer Setup.exe for a remote seat, and the Linux and Compose tarballs. The Full Dashboard and its CLI installer ship nothing. Their last builds are in the v3.2.0 release.
Not sure which one? Start with Lite. It is one download, nothing is installed on your server, and data starts to flow in under 5 minutes.
Quick start: Lite
- Download
PerformanceMonitorLite-lite-Setup.exe. It is a self-contained build, so you do not install a .NET runtime first. - Run the installer. It adds Start Menu and Desktop shortcuts.
- Start Lite from the Start Menu or the Desktop shortcut.
- Click + Add Server, enter the connection details, test, and save.
- Double-click the server in the sidebar to connect.
Data starts to flow within 1 to 5 minutes. The monitoring login needs VIEW SERVER STATE (Permissions).
Before you upgrade an older install with Setup.exe, read the warning in the Lite guide. On versions older than 3.4.0, Setup.exe deletes the data in the install directory (see Upgrading an install older than 3.4.0). The Lite guide also covers the portable ZIP, collectors, storage, and configuration.
Quick start: Darling
- Download
PerformanceMonitorDarling-<version>.zipandSHA256SUMS.txtfrom the latest release. Check the zip hash againstSHA256SUMS.txt. The zip carries its own .NET runtime, so there is nothing to install first. - Extract the zip to
C:\Program Files\PerformanceMonitorDarling. Do not use your Desktop, Downloads, or any folder underC:\Users\. The service runs as a virtual account that cannot read a user profile (why). - Double-click
Install-Darling.cmdin the install folder. It asks Windows for administrator rights and runsinstall-darling.ps1. You can also run.\install-darling.ps1from an elevated PowerShell. It installs the Windows service and creates a Darling Viewer shortcut. With nodarling.jsonit writes a minimal one, and the service starts with no monitored servers. - Wait about two minutes for the first start, then open Darling Viewer. It opens on the fleet.
- Add your first server in the viewer.
darling.jsonis only a seed. The service reads it on its first start, so a server added to the file later is ignored (why). - The service log is in
%ProgramData%\PerformanceMonitorDarling\logs.
Install Darling gives each step with the log line or screen that proves it worked. To upgrade, run upgrade-darling.ps1. To remove the service, run uninstall-darling.ps1. Both are in the install folder. For Linux and the web dashboard, read the Darling quick start. The Darling operator guide is the configuration reference.
Documentation
| Page | What it covers |
|---|---|
| Choosing an edition | Lite, Darling, and Dashboard side by side |
| Features and screenshots | What you get, with screenshots |
| Lite guide | Install, upgrade, where Lite keeps its files, configuration, appearance, collectors |
| Lite Extended Events sessions | The sessions Lite creates on a monitored server, and how to remove them |
| Darling quick start | Install on Windows, Linux notes, web dashboard |
| Darling operator guide | Darling configuration, permissions, operations |
| Darling store sizing | Disk, RAM and vCPU for a store host, by number of servers |
| Back up, restore and move the store | Back up a Darling store, restore it, or move it to another machine |
| Darling guides | Install, viewer, web dashboard, MCP, day-to-day admin and command line reference |
| PostgreSQL target runbook | Point Darling at a PostgreSQL target, with a proof point at each step |
| Retention Held runbook | Clear a Retention Held alert |
| How collection works | A tour of the collection pipeline, for people who read the code |
| Documentation index | Every page in docs/, grouped by audience |
| Tabs | What each tab shows |
| Alerts and notifications | Alert types, channels, routes, email |
| Agent dispatch | Hand an alert to your own AI agent: levels, the brief and report, undo, the remediation login |
| Signed webhooks | Verify that a generic webhook post came from Darling |
| Agent job monitoring | Running SQL Agent jobs and jobs that run longer than expected |
| MCP server | Setup, the tool list and the Lite investigation tools for AI analysis |
| Authentication | Authentication types and credential profiles |
| Permissions | Grants for on-premises, Azure, and AWS RDS. The optional agent remediation login is in Agent dispatch |
| Platform notes | AWS RDS and Aurora configuration |
| Performance impact | Load on monitored servers, and local resources for Lite |
| Troubleshooting | Common problems for Lite and Darling |
| Building from source | Folder structure and build commands |
| Support and sponsorship | Commercial support tiers and sponsorship |
| Third-party components | Third-party components and their licenses |
| Changelog | Changes in each release |
Support
Performance Monitor is free and open source under the MIT License, with no features withheld. The tools that it replaces charge thousands of dollars per server per year. A support subscription covers all of your SQL Server instances.
| Tier | Cost per year | Email response | Includes |
|---|---|---|---|
| Supported | $500 | Within 2 business days | Guaranteed compatibility updates for new SQL Server versions, priority feature requests, a support agreement and invoices, unlimited instances |
| Priority | $2,500 | By the next business day | Everything in Supported, plus a quarterly live Q&A session, early access to new features, and direct input on the roadmap |
Support and sponsorship says what support gets you and has the link to buy. You can also sponsor on GitHub.
Sponsors
License
Copyright (c) 2026 Darling Data, LLC. Licensed under the MIT License. See LICENSE for details.
Author
Erik Darling: erikdarling.com and Darling Data, LLC
PerformanceMonitor MCP questions
Which databases can PerformanceMonitor monitor?
It monitors SQL Server 2016 SP2 through 2025, Azure SQL Managed Instance, AWS RDS for SQL Server, and PostgreSQL 14 to 18 including RDS, Aurora and Azure Database for PostgreSQL.
Do the AI agents need special permissions to change alert settings?
They only get that ability if you enable it per server; all such switches are off by default and every change is recorded.
What editions does PerformanceMonitor offer?
Two main editions: Lite, a single desktop app storing data locally, and Darling, a service that collects 24/7 into a central PostgreSQL store.
Is PerformanceMonitor free?
Yes, it is free and open source under the MIT License with no features withheld; paid support subscriptions are optional.
How do I get started with PerformanceMonitor?
Start with Lite: one download, nothing installed on your server, and data starts flowing within a few minutes.