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
Copy file name to clipboardExpand all lines: README.md
+1-3Lines changed: 1 addition & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@
13
13
14
14
<palign="center">
15
15
A development tool for visualizing and debugging NgRx state management in Angular applications.<br>
16
-
Real-time action monitoring, effect tracking, state visualization, diff viewer, and performance metrics no browser extensions needed.
16
+
Real-time action monitoring, effect tracking, state visualization, diff viewer, and performance metrics. No browser extensions needed.
17
17
</p>
18
18
19
19
<palign="center">
@@ -67,8 +67,6 @@ npx ngrx-devtool
67
67
68
68
Open **http://localhost:3000** and start your Angular app.
69
69
70
-
---
71
-
72
70
For full documentation, configuration options, troubleshooting, and more, visit the **[documentation site](https://amadeusitgroup.github.io/ngrx-devtool/)**.
Turn your live NgRx DevTool session into AI-ready debugging context with no API key, subscription, or extra install required.
9
+
10
+
## Copy a debugging prompt
11
+
12
+
Click **Debug with AI** in the toolbar. The DevTool assembles a focused prompt from the current session:
13
+
14
+
- Recent actions
15
+
- Effect errors with stack traces
16
+
- Slowest renders
17
+
- Latest state diff
18
+
19
+
Paste the prompt into GitHub Copilot Chat, Claude, ChatGPT, or another assistant. Pick a focus such as health check, debug errors, why slow, or explain flow, and the prompt adapts.
20
+
21
+
## Run locally with Ollama
22
+
23
+
If you have [Ollama](https://ollama.com) running, the dialog detects it automatically and lets you ask a local model right inside the DevTool. Answers stream in, and nothing leaves your machine.
24
+
25
+
```bash
26
+
ollama pull llama3
27
+
```
28
+
29
+
## Connect via MCP
30
+
31
+
The server exposes a [Model Context Protocol](https://modelcontextprotocol.io) endpoint at `http://localhost:3000/mcp`, so AI assistants can query your running NgRx session directly.
32
+
33
+
Add this to `.vscode/mcp.json` in your project:
34
+
35
+
```json
36
+
{
37
+
"servers": {
38
+
"ngrx-devtool": {
39
+
"type": "http",
40
+
"url": "http://localhost:3000/mcp"
41
+
}
42
+
}
43
+
}
44
+
```
45
+
46
+
Then ask Copilot Chat things like:
47
+
48
+
```text
49
+
Why is my loadBooks$ effect failing?
50
+
```
51
+
52
+
## MCP tools
53
+
54
+
| Tool | What it returns |
55
+
|---|---|
56
+
|`get_debug_summary`| Recent actions, effect errors and performance at a glance |
57
+
|`get_action_timeline`| Recent actions with source, render time and warnings |
58
+
|`get_effects` / `get_effect_errors`| Effect executions, plus errors with stack traces |
59
+
|`get_state_diff`| What changed in the store for a given action |
60
+
|`get_current_state`| The latest store snapshot |
61
+
|`get_performance_stats`| Average/max render time and the slowest actions |
62
+
63
+
:::info
64
+
The MCP server captures traffic in memory on the DevTool server and adds no new dependencies to the published package.
0 commit comments