You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rename to Performance Studio, add MCP docs and settings toggle (#7)
- Rename "SQL Performance Studio" to "Performance Studio" across all
user-facing strings: title bar, about dialog, help menu, app name,
macOS bundle, csproj product, MCP server name, docs
- Add MCP section to README with setup instructions, tool reference,
and example questions
- Add MCP enable/port toggle to About screen (interim until dedicated
settings UI)
- Fix MCP endpoint URL from /mcp to / in docs and instructions
- Fix MCP server name from sql-performance-studio to performance-studio
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: README.md
+50-7Lines changed: 50 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
-
# SQL Performance Studio
1
+
# Performance Studio
2
2
3
-
A cross-platform SQL Server execution plan analyzer. Parses `.sqlplan` XML, identifies performance problems, suggests missing indexes, and provides actionable warnings — from the command line or a desktop GUI.
3
+
A cross-platform SQL Server execution plan analyzer with built-in MCP server for AI-assisted analysis. Parses `.sqlplan` XML, identifies performance problems, suggests missing indexes, and provides actionable warnings — from the command line or a desktop GUI.
4
4
5
5
Built for developers and DBAs who want fast, automated plan analysis without clicking through SSMS.
-`query_name.sqlplan` — the raw execution plan XML (openable in SSMS or the SQL Performance Studio GUI)
142
+
-`query_name.sqlplan` — the raw execution plan XML (openable in SSMS or the Performance Studio GUI)
143
143
-`query_name.analysis.json` — structured analysis with warnings, missing indexes, and operator tree
144
144
-`query_name.analysis.txt` — human-readable text report
145
145
@@ -240,6 +240,7 @@ Features:
240
240
-**Copy Repro Script** — extracts parameters, SET options, and query text into a runnable `sp_executesql` script
241
241
-**Get Actual Plan** — connect to a server and re-execute the query to capture runtime stats
242
242
-**Query Store Analysis** — connect to a server and analyze top queries by CPU, duration, or reads
243
+
-**MCP Server** — built-in Model Context Protocol server for AI-assisted plan analysis (opt-in)
243
244
- Dark theme
244
245
245
246
```bash
@@ -248,14 +249,14 @@ dotnet run --project src/PlanViewer.App
248
249
249
250
## SSMS Extension
250
251
251
-
A VSIX extension that adds **"Open in SQL Performance Studio"** to the execution plan right-click context menu in SSMS 18-22.
252
+
A VSIX extension that adds **"Open in Performance Studio"** to the execution plan right-click context menu in SSMS 18-22.
252
253
253
254
### How it works
254
255
255
256
1. Right-click on any execution plan in SSMS
256
-
2. Click "Open in SQL Performance Studio"
257
+
2. Click "Open in Performance Studio"
257
258
3. The extension extracts the plan XML via reflection and saves it to a temp file
258
-
4.SQL Performance Studio opens with the plan loaded
259
+
4. Performance Studio opens with the plan loaded
259
260
260
261
### Installation
261
262
@@ -267,13 +268,55 @@ A VSIX extension that adds **"Open in SQL Performance Studio"** to the execution
267
268
268
269
### First run
269
270
270
-
On first use, if SQL Performance Studio isn't found automatically, the extension will prompt you to locate `PlanViewer.App.exe`. The path is saved to the registry (`HKCU\SOFTWARE\DarlingData\SQLPerformanceStudio\InstallPath`) so you only need to do this once.
271
+
On first use, if Performance Studio isn't found automatically, the extension will prompt you to locate `PlanViewer.App.exe`. The path is saved to the registry (`HKCU\SOFTWARE\DarlingData\SQLPerformanceStudio\InstallPath`) so you only need to do this once.
271
272
272
273
The extension searches for the app in this order:
273
274
1. Registry key (set automatically after first browse)
274
275
2. System PATH
275
276
3. Common install locations (`%LOCALAPPDATA%\Programs\SQLPerformanceStudio\`, `Program Files`, etc.)
276
277
278
+
## MCP Server (LLM Integration)
279
+
280
+
The desktop GUI includes an embedded [Model Context Protocol](https://modelcontextprotocol.io) server that exposes loaded execution plans and Query Store data to LLM clients like Claude Code and Cursor.
281
+
282
+
### Setup
283
+
284
+
1. Enable the MCP server in `~/.planview/settings.json`:
285
+
286
+
```json
287
+
{
288
+
"mcp_enabled": true,
289
+
"mcp_port": 5152
290
+
}
291
+
```
292
+
293
+
2. Register with Claude Code:
294
+
295
+
```
296
+
claude mcp add --transport streamable-http --scope user performance-studio http://localhost:5152/
297
+
```
298
+
299
+
3. Open a new Claude Code session and ask questions like:
300
+
- "What plans are loaded in the application?"
301
+
- "Analyze the execution plan and tell me what's wrong"
302
+
- "Are there any missing index suggestions?"
303
+
- "Compare these two plans — which is better?"
304
+
- "Fetch the top 10 queries by CPU from Query Store"
| Query Store |`check_query_store`, `get_query_store_top`|
315
+
316
+
Plan analysis tools work on plans loaded in the app (via file open, paste, query execution, or Query Store fetch). Query Store tools use a built-in read-only DMV query — no arbitrary SQL can be executed.
317
+
318
+
The MCP server binds to `localhost` only and does not accept remote connections. Disabled by default.
0 commit comments