@programinglive/dev-workflow-mcp-server 1.3.7 → 1.3.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,542 @@
1
+ <h1>Troubleshooting Dev-Workflow MCP Server in Antigravity</h1>
2
+ <p>Common issues and solutions when using dev-workflow MCP server with Antigravity.</p>
3
+ <h2>Table of Contents</h2>
4
+ <ul>
5
+ <li><a href="#mcp-server-not-appearing">MCP Server Not Appearing</a></li>
6
+ <li><a href="#workflow-state-conflicts">Workflow State Conflicts</a></li>
7
+ <li><a href="#git-conflicts-with-automated-commits">Git Conflicts with Automated Commits</a></li>
8
+ <li><a href="#path-resolution-issues-on-windows">Path Resolution Issues on Windows</a></li>
9
+ <li><a href="#sqlite-database-locking">SQLite Database Locking</a></li>
10
+ <li><a href="#multi-user-workflow-isolation-problems">Multi-User Workflow Isolation Problems</a></li>
11
+ <li><a href="#windsurf-editor-conflicts">Windsurf Editor Conflicts</a></li>
12
+ <li><a href="#tests-not-running">Tests Not Running</a></li>
13
+ <li><a href="#commit-and-push-failures">Commit and Push Failures</a></li>
14
+ </ul>
15
+ <hr>
16
+ <h2>MCP Server Not Appearing</h2>
17
+ <h3>Symptoms</h3>
18
+ <ul>
19
+ <li>Dev-workflow tools not visible in Antigravity</li>
20
+ <li>MCP server commands not available</li>
21
+ <li>No response when trying to use workflow tools</li>
22
+ </ul>
23
+ <h3>Solutions</h3>
24
+ <h4>1. Verify Configuration Path</h4>
25
+ <p>Check that <code>mcp_config.json</code> is in the correct location:</p>
26
+ <p><strong>Windows:</strong></p>
27
+ <pre><code class="language-powershell"># Check if file exists
28
+ Test-Path &quot;C:\Users\$env:USERNAME\.gemini\antigravity\mcp_config.json&quot;
29
+
30
+ # Or alternative location
31
+ Test-Path &quot;$env:APPDATA\Antigravity\mcp_config.json&quot;
32
+ </code></pre>
33
+ <p><strong>macOS/Linux:</strong></p>
34
+ <pre><code class="language-bash"># Check config file
35
+ ls -la ~/.gemini/antigravity/mcp_config.json
36
+ # or
37
+ ls -la ~/Library/Application\ Support/Antigravity/mcp_config.json
38
+ </code></pre>
39
+ <h4>2. Validate JSON Syntax</h4>
40
+ <p>Ensure <code>mcp_config.json</code> has valid JSON:</p>
41
+ <pre><code class="language-json">{
42
+ &quot;mcpServers&quot;: {
43
+ &quot;dev-workflow&quot;: {
44
+ &quot;command&quot;: &quot;node&quot;,
45
+ &quot;args&quot;: [
46
+ &quot;d:\\code\\dev-workflow-mcp-server\\index.js&quot;
47
+ ]
48
+ }
49
+ }
50
+ }
51
+ </code></pre>
52
+ <p>Common mistakes:</p>
53
+ <ul>
54
+ <li>❌ Missing quotes around strings</li>
55
+ <li>❌ Trailing commas</li>
56
+ <li>❌ Single quotes instead of double quotes</li>
57
+ <li>❌ Unescaped backslashes on Windows</li>
58
+ </ul>
59
+ <p>Use a JSON validator: <code>node -e &quot;console.log(JSON.parse(require(&#39;fs&#39;).readFileSync(&#39;path/to/mcp_config.json&#39;)))&quot;</code></p>
60
+ <h4>3. Check Node.js Path</h4>
61
+ <p>Verify Node.js is accessible:</p>
62
+ <pre><code class="language-bash">node --version
63
+ </code></pre>
64
+ <p>If not found, specify full Node.js path in config:</p>
65
+ <pre><code class="language-json">{
66
+ &quot;mcpServers&quot;: {
67
+ &quot;dev-workflow&quot;: {
68
+ &quot;command&quot;: &quot;C:\\Program Files\\nodejs\\node.exe&quot;,
69
+ &quot;args&quot;: [&quot;d:\\code\\dev-workflow-mcp-server\\index.js&quot;]
70
+ }
71
+ }
72
+ }
73
+ </code></pre>
74
+ <h4>4. Verify Server Path</h4>
75
+ <p>Check that <code>index.js</code> exists:</p>
76
+ <pre><code class="language-powershell"># Windows
77
+ Test-Path &quot;d:\code\dev-workflow-mcp-server\index.js&quot;
78
+ </code></pre>
79
+ <pre><code class="language-bash"># macOS/Linux
80
+ ls -la /path/to/dev-workflow-mcp-server/index.js
81
+ </code></pre>
82
+ <h4>5. Restart Antigravity</h4>
83
+ <p>After configuration changes, <strong>fully restart Antigravity</strong>:</p>
84
+ <ol>
85
+ <li>Close all Antigravity windows</li>
86
+ <li>Quit from system tray if present</li>
87
+ <li>Reopen Antigravity</li>
88
+ </ol>
89
+ <h4>6. Check Server Logs</h4>
90
+ <p>Run the server manually to see errors:</p>
91
+ <pre><code class="language-bash">cd d:\code\dev-workflow-mcp-server
92
+ node index.js
93
+ </code></pre>
94
+ <p>Look for error messages. Common issues:</p>
95
+ <ul>
96
+ <li>Missing dependencies (<code>npm install</code>)</li>
97
+ <li>Permission errors</li>
98
+ <li>Port conflicts</li>
99
+ </ul>
100
+ <hr>
101
+ <h2>Workflow State Conflicts</h2>
102
+ <h3>Symptoms</h3>
103
+ <ul>
104
+ <li>Workflow shows incorrect phase</li>
105
+ <li>History from different projects appearing</li>
106
+ <li>State not persisting between sessions</li>
107
+ </ul>
108
+ <h3>Solutions</h3>
109
+ <h4>1. Check State File Location</h4>
110
+ <p>Verify state file exists:</p>
111
+ <pre><code class="language-bash"># In your project directory
112
+ ls -la .state/workflow-state.json
113
+ </code></pre>
114
+ <p>If missing, the server creates it on first use.</p>
115
+ <h4>2. Reset Workflow State</h4>
116
+ <p>If state is corrupted:</p>
117
+ <pre><code class="language-bash"># Backup existing state
118
+ cp .state/workflow-state.json .state/workflow-state.json.backup
119
+
120
+ # Start fresh (server recreates on next use)
121
+ rm .state/workflow-state.json
122
+ </code></pre>
123
+ <p>Re-run <code>get_workflow_status</code> to initialize.</p>
124
+ <h4>3. Per-Project Isolation</h4>
125
+ <p>Ensure each project has its own state:</p>
126
+ <pre><code class="language-bash"># Project A
127
+ cd ~/projects/app-frontend
128
+ npm install @programinglive/dev-workflow-mcp-server
129
+ # Creates .state/ in app-frontend/
130
+
131
+ # Project B
132
+ cd ~/projects/app-backend
133
+ npm install @programinglive/dev-workflow-mcp-server
134
+ # Creates .state/ in app-backend/
135
+ </code></pre>
136
+ <h4>4. Custom State File Path</h4>
137
+ <p>Override state location with environment variable:</p>
138
+ <pre><code class="language-json">{
139
+ &quot;mcpServers&quot;: {
140
+ &quot;dev-workflow&quot;: {
141
+ &quot;command&quot;: &quot;node&quot;,
142
+ &quot;args&quot;: [&quot;d:\\code\\dev-workflow-mcp-server\\index.js&quot;],
143
+ &quot;env&quot;: {
144
+ &quot;DEV_WORKFLOW_STATE_FILE&quot;: &quot;d:\\projects\\my-app\\.state\\workflow-state.json&quot;
145
+ }
146
+ }
147
+ }
148
+ }
149
+ </code></pre>
150
+ <hr>
151
+ <h2>Git Conflicts with Automated Commits</h2>
152
+ <h3>Symptoms</h3>
153
+ <ul>
154
+ <li><code>commit_and_push</code> fails with merge conflicts</li>
155
+ <li>Diverged branch errors</li>
156
+ <li>Uncommitted changes blocking workflow</li>
157
+ </ul>
158
+ <h3>Solutions</h3>
159
+ <h4>1. Pull Before Committing</h4>
160
+ <p>Always pull latest changes first:</p>
161
+ <pre><code class="language-bash">git pull origin main
162
+ </code></pre>
163
+ <p>Then run workflow commands.</p>
164
+ <h4>2. Resolve Conflicts Manually</h4>
165
+ <p>If conflicts occur:</p>
166
+ <pre><code class="language-bash"># See conflicts
167
+ git status
168
+
169
+ # Resolve conflicts in files
170
+ # Then:
171
+ git add .
172
+ git commit -m &quot;resolve conflicts&quot;
173
+ git push
174
+ </code></pre>
175
+ <p>Then resume workflow with <code>get_workflow_status</code>.</p>
176
+ <h4>3. Use Correct Branch</h4>
177
+ <p>Ensure you&#39;re on the right branch:</p>
178
+ <pre><code class="language-bash">git branch # Check current branch
179
+ git checkout your-feature-branch
180
+ </code></pre>
181
+ <p>Then specify in workflow:</p>
182
+ <pre><code>commit_and_push:
183
+ commitMessage: &quot;feat: add feature&quot;
184
+ branch: &quot;your-feature-branch&quot;
185
+ </code></pre>
186
+ <h4>4. Stash Uncommitted Changes</h4>
187
+ <p>If you have uncommitted changes blocking the workflow:</p>
188
+ <pre><code class="language-bash"># Stash changes
189
+ git stash
190
+
191
+ # Run workflow
192
+ # ...
193
+
194
+ # Restore changes
195
+ git stash pop
196
+ </code></pre>
197
+ <hr>
198
+ <h2>Path Resolution Issues on Windows</h2>
199
+ <h3>Symptoms</h3>
200
+ <ul>
201
+ <li>&quot;Cannot find module&quot; errors</li>
202
+ <li>Path not found errors</li>
203
+ <li>Server fails to start</li>
204
+ </ul>
205
+ <h3>Solutions</h3>
206
+ <h4>1. Use Escaped Backslashes</h4>
207
+ <p>In JSON, escape backslashes:</p>
208
+ <pre><code class="language-json">{
209
+ &quot;args&quot;: [&quot;d:\\code\\dev-workflow-mcp-server\\index.js&quot;]
210
+ }
211
+ </code></pre>
212
+ <p>Not:</p>
213
+ <pre><code class="language-json">{
214
+ &quot;args&quot;: [&quot;d:\code\dev-workflow-mcp-server\index.js&quot;] // ❌ Wrong
215
+ }
216
+ </code></pre>
217
+ <h4>2. Use Forward Slashes</h4>
218
+ <p>Alternative: use forward slashes (works on Windows):</p>
219
+ <pre><code class="language-json">{
220
+ &quot;args&quot;: [&quot;d:/code/dev-workflow-mcp-server/index.js&quot;]
221
+ }
222
+ </code></pre>
223
+ <h4>3. Use Absolute Paths</h4>
224
+ <p>Always use full paths, not relative:</p>
225
+ <pre><code class="language-json">{
226
+ &quot;args&quot;: [&quot;C:\\Users\\Username\\Projects\\dev-workflow-mcp-server\\index.js&quot;]
227
+ }
228
+ </code></pre>
229
+ <h4>4. Avoid Spaces in Paths</h4>
230
+ <p>If path has spaces, ensure proper escaping:</p>
231
+ <pre><code class="language-json">{
232
+ &quot;args&quot;: [&quot;C:\\Program Files\\My Project\\dev-workflow-mcp-server\\index.js&quot;]
233
+ }
234
+ </code></pre>
235
+ <p>Or move to path without spaces.</p>
236
+ <hr>
237
+ <h2>SQLite Database Locking</h2>
238
+ <h3>Symptoms</h3>
239
+ <ul>
240
+ <li>&quot;Database is locked&quot; errors</li>
241
+ <li>Cannot save workflow state</li>
242
+ <li>Timeouts when updating workflow</li>
243
+ </ul>
244
+ <h3>Solutions</h3>
245
+ <h4>1. Close Other Processes</h4>
246
+ <p>Ensure no other processes have the database open:</p>
247
+ <pre><code class="language-powershell"># Windows: Find processes with file open
248
+ handle .state\users\
249
+
250
+ # macOS/Linux
251
+ lsof .state/users/*/workflow-state.db
252
+ </code></pre>
253
+ <p>Close conflicting processes.</p>
254
+ <h4>2. One MCP Server Per User</h4>
255
+ <p>Don&#39;t run multiple MCP server instances for same user:</p>
256
+ <ul>
257
+ <li>Close other editors using the MCP server</li>
258
+ <li>Ensure only one Antigravity instance is active</li>
259
+ </ul>
260
+ <h4>3. Use Different User IDs</h4>
261
+ <p>If multiple users/editors need simultaneous access:</p>
262
+ <pre><code class="language-json">{
263
+ &quot;mcpServers&quot;: {
264
+ &quot;dev-workflow&quot;: {
265
+ &quot;command&quot;: &quot;node&quot;,
266
+ &quot;args&quot;: [&quot;d:\\code\\dev-workflow-mcp-server\\index.js&quot;],
267
+ &quot;env&quot;: {
268
+ &quot;DEV_WORKFLOW_USER_ID&quot;: &quot;antigravity-user&quot;
269
+ }
270
+ }
271
+ }
272
+ }
273
+ </code></pre>
274
+ <p>In Windsurf:</p>
275
+ <pre><code class="language-json">{
276
+ &quot;env&quot;: {
277
+ &quot;DEV_WORKFLOW_USER_ID&quot;: &quot;windsurf-user&quot;
278
+ }
279
+ }
280
+ </code></pre>
281
+ <h4>4. Repair Database</h4>
282
+ <p>If database is corrupted:</p>
283
+ <pre><code class="language-bash">cd .state/users/your-user-id/
284
+
285
+ # Backup
286
+ cp workflow-state.db workflow-state.db.backup
287
+
288
+ # Check integrity
289
+ sqlite3 workflow-state.db &quot;PRAGMA integrity_check;&quot;
290
+
291
+ # If corrupted, start fresh
292
+ rm workflow-state.db
293
+ </code></pre>
294
+ <hr>
295
+ <h2>Multi-User Workflow Isolation Problems</h2>
296
+ <h3>Symptoms</h3>
297
+ <ul>
298
+ <li>Users see each other&#39;s workflows</li>
299
+ <li>History mixing between developers</li>
300
+ <li>State conflicts on shared machines</li>
301
+ </ul>
302
+ <h3>Solutions</h3>
303
+ <h4>1. Set Unique User IDs</h4>
304
+ <p>Each developer should have unique <code>DEV_WORKFLOW_USER_ID</code>:</p>
305
+ <p><strong>Developer Alice:</strong></p>
306
+ <pre><code class="language-json">{
307
+ &quot;mcpServers&quot;: {
308
+ &quot;dev-workflow&quot;: {
309
+ &quot;command&quot;: &quot;node&quot;,
310
+ &quot;args&quot;: [&quot;d:\\code\\dev-workflow-mcp-server\\index.js&quot;],
311
+ &quot;env&quot;: {
312
+ &quot;DEV_WORKFLOW_USER_ID&quot;: &quot;alice&quot;
313
+ }
314
+ }
315
+ }
316
+ }
317
+ </code></pre>
318
+ <p><strong>Developer Bob:</strong></p>
319
+ <pre><code class="language-json">{
320
+ &quot;env&quot;: {
321
+ &quot;DEV_WORKFLOW_USER_ID&quot;: &quot;bob&quot;
322
+ }
323
+ }
324
+ </code></pre>
325
+ <h4>2. Verify User Isolation</h4>
326
+ <p>Check that separate DB files exist:</p>
327
+ <pre><code class="language-bash">ls -la .state/users/
328
+ # Should see:
329
+ # alice/workflow-state.db
330
+ # bob/workflow-state.db
331
+ </code></pre>
332
+ <h4>3. View Specific User History</h4>
333
+ <p>In web dashboard:</p>
334
+ <pre><code class="language-bash">npm run web
335
+ # Open: http://localhost:3111?user=alice
336
+ # Or: http://localhost:3111?user=bob
337
+ </code></pre>
338
+ <hr>
339
+ <h2>Windsurf Editor Conflicts</h2>
340
+ <h3>Symptoms</h3>
341
+ <ul>
342
+ <li>Workflow state corrupted when switching between Antigravity and Windsurf</li>
343
+ <li>Both editors showing different workflow phases</li>
344
+ <li>SQLite locking errors</li>
345
+ </ul>
346
+ <h3>Root Cause</h3>
347
+ <p>Both editors try to use the same workflow state file simultaneously.</p>
348
+ <h3>Solutions</h3>
349
+ <h4>Solution 1: Use Different User IDs (Recommended)</h4>
350
+ <p>Most reliable approach - complete isolation:</p>
351
+ <p><strong>Antigravity config:</strong></p>
352
+ <pre><code class="language-json">{
353
+ &quot;mcpServers&quot;: {
354
+ &quot;dev-workflow&quot;: {
355
+ &quot;command&quot;: &quot;node&quot;,
356
+ &quot;args&quot;: [&quot;d:\\code\\dev-workflow-mcp-server\\index.js&quot;],
357
+ &quot;env&quot;: {
358
+ &quot;DEV_WORKFLOW_USER_ID&quot;: &quot;antigravity&quot;
359
+ }
360
+ }
361
+ }
362
+ }
363
+ </code></pre>
364
+ <p><strong>Windsurf config:</strong></p>
365
+ <pre><code class="language-json">{
366
+ &quot;mcpServers&quot;: {
367
+ &quot;dev-workflow&quot;: {
368
+ &quot;command&quot;: &quot;node&quot;,
369
+ &quot;args&quot;: [&quot;d:\\code\\dev-workflow-mcp-server\\index.js&quot;],
370
+ &quot;env&quot;: {
371
+ &quot;DEV_WORKFLOW_USER_ID&quot;: &quot;windsurf&quot;
372
+ }
373
+ }
374
+ }
375
+ }
376
+ </code></pre>
377
+ <p>This creates:</p>
378
+ <ul>
379
+ <li><code>.state/users/antigravity/workflow-state.db</code> for Antigravity</li>
380
+ <li><code>.state/users/windsurf/workflow-state.db</code> for Windsurf</li>
381
+ </ul>
382
+ <h4>Solution 2: Use One Editor at a Time</h4>
383
+ <p>If you want shared state:</p>
384
+ <ol>
385
+ <li><strong>Close Windsurf completely</strong> before opening Antigravity</li>
386
+ <li>Or <strong>close Antigravity</strong> before opening Windsurf</li>
387
+ <li>Only ONE editor should access workflow at a time</li>
388
+ </ol>
389
+ <h4>Solution 3: Separate Projects</h4>
390
+ <p>Use the MCP server in different projects:</p>
391
+ <ul>
392
+ <li>Antigravity → Project A</li>
393
+ <li>Windsurf → Project B</li>
394
+ </ul>
395
+ <p>Each project has isolated <code>.state/</code> directory.</p>
396
+ <h4>Solution 4: Disable in One Editor</h4>
397
+ <p>Keep MCP server active in only one editor:</p>
398
+ <p>Remove or comment out from one config:</p>
399
+ <pre><code class="language-json">{
400
+ &quot;mcpServers&quot;: {
401
+ // &quot;dev-workflow&quot;: { ... } // Disabled
402
+ }
403
+ }
404
+ </code></pre>
405
+ <hr>
406
+ <h2>Tests Not Running</h2>
407
+ <h3>Symptoms</h3>
408
+ <ul>
409
+ <li><code>run_tests</code> accepts any input</li>
410
+ <li>Tests marked as passed but didn&#39;t actually run</li>
411
+ <li>No test output shown</li>
412
+ </ul>
413
+ <h3>Explanation</h3>
414
+ <p>The MCP server <strong>records</strong> test results; it doesn&#39;t execute tests. You must run tests manually first.</p>
415
+ <h3>Solution</h3>
416
+ <h4>1. Run Tests Manually</h4>
417
+ <pre><code class="language-bash"># Run your test suite
418
+ npm test
419
+ # or
420
+ npm run test
421
+ # or
422
+ yarn test
423
+ </code></pre>
424
+ <h4>2. Record Results</h4>
425
+ <p>Then record in workflow:</p>
426
+ <pre><code>run_tests:
427
+ passed: true
428
+ testCommand: &quot;npm test&quot;
429
+ details: &quot;127 tests passed&quot;
430
+ </code></pre>
431
+ <h4>3. Workflow Blocking</h4>
432
+ <p>The workflow <strong>blocks commits if you record <code>passed: false</code></strong>:</p>
433
+ <pre><code>run_tests:
434
+ passed: false
435
+ testCommand: &quot;npm test&quot;
436
+ details: &quot;3 tests failed&quot;
437
+ </code></pre>
438
+ <p>Response:</p>
439
+ <pre><code>❌ Tests FAILED!
440
+ 🚫 Cannot proceed with failing tests
441
+ </code></pre>
442
+ <p>Fix tests, re-run, then record:</p>
443
+ <pre><code>run_tests:
444
+ passed: true
445
+ testCommand: &quot;npm test&quot;
446
+ details: &quot;All 127 tests now pass&quot;
447
+ </code></pre>
448
+ <hr>
449
+ <h2>Commit and Push Failures</h2>
450
+ <h3>Symptoms</h3>
451
+ <ul>
452
+ <li><code>commit_and_push</code> fails</li>
453
+ <li>No changes committ push rejected</li>
454
+ <li>Authentication errors</li>
455
+ </ul>
456
+ <h3>Solutions</h3>
457
+ <h4>1. Verify Git Configuration</h4>
458
+ <pre><code class="language-bash">git config --list
459
+
460
+ # Should have:
461
+ # user.name=Your Name
462
+ # user.email=your@email.com
463
+ </code></pre>
464
+ <p>If missing:</p>
465
+ <pre><code class="language-bash">git config --global user.name &quot;Your Name&quot;
466
+ git config --global user.email &quot;your@email.com&quot;
467
+ </code></pre>
468
+ <h4>2. Ensure Changes Exist</h4>
469
+ <p>MCP server stages files with <code>git add .</code>. Verify changes:</p>
470
+ <pre><code class="language-bash">git status
471
+ </code></pre>
472
+ <p>If no changes, the commit will fail.</p>
473
+ <h4>3. Check Remote Configuration</h4>
474
+ <pre><code class="language-bash">git remote -v
475
+ </code></pre>
476
+ <p>Should show:</p>
477
+ <pre><code>origin https://github.com/user/repo.git (fetch)
478
+ origin https://github.com/user/repo.git (push)
479
+ </code></pre>
480
+ <p>If missing:</p>
481
+ <pre><code class="language-bash">git remote add origin https://github.com/user/repo.git
482
+ </code></pre>
483
+ <h4>4. Authentication Issues</h4>
484
+ <p><strong>GitHub HTTPS:</strong></p>
485
+ <pre><code class="language-bash"># Use personal access token
486
+ git config --global credential.helper store
487
+ git push # Enter token when prompted
488
+ </code></pre>
489
+ <p><strong>GitHub SSH:</strong></p>
490
+ <pre><code class="language-bash"># Verify SSH key
491
+ ssh -T git@github.com
492
+
493
+ # Change remote to SSH
494
+ git remote set-url origin git@github.com:user/repo.git
495
+ </code></pre>
496
+ <h4>5. Branch Protection</h4>
497
+ <p>If branch is protected:</p>
498
+ <ul>
499
+ <li>Create a feature branch</li>
500
+ <li>Push to feature branch instead:</li>
501
+ </ul>
502
+ <pre><code>commit_and_push:
503
+ commitMessage: &quot;feat: add feature&quot;
504
+ branch: &quot;feature/my-feature&quot;
505
+ </code></pre>
506
+ <hr>
507
+ <h2>Getting More Help</h2>
508
+ <h3>Enable Debug Logging</h3>
509
+ <p>Run server with debug output:</p>
510
+ <pre><code class="language-bash">NODE_ENV=development node index.js
511
+ </code></pre>
512
+ <h3>Check Server Health</h3>
513
+ <p>Test manually:</p>
514
+ <pre><code class="language-bash">cd dev-workflow-mcp-server
515
+ node index.js
516
+
517
+ # Type to test:
518
+ # get_workflow_status
519
+ </code></pre>
520
+ <h3>Community Support</h3>
521
+ <ul>
522
+ <li><strong>GitHub Issues:</strong> <a href="https://github.com/programinglive/dev-workflow-mcp-server/issues">Report bugs</a></li>
523
+ <li><strong>Discussions:</strong> <a href="https://github.com/programinglive/dev-workflow-mcp-server/discussions">Ask questions</a></li>
524
+ </ul>
525
+ <h3>Documentation</h3>
526
+ <ul>
527
+ <li><a href="./GETTING-STARTED.md">Getting Started</a></li>
528
+ <li><a href="./EXAMPLES.md">Examples</a></li>
529
+ <li><a href="./WORKFLOW-TEMPLATES.md">Workflow Templates</a></li>
530
+ <li><a href="../../README.md">Main README</a></li>
531
+ </ul>
532
+ <hr>
533
+ <p><strong>Still having issues?</strong> Open a GitHub issue with:</p>
534
+ <ol>
535
+ <li>Your <code>mcp_config.json</code> (redact sensitive paths)</li>
536
+ <li>Error messages</li>
537
+ <li>Steps to reproduce</li>
538
+ <li>Antigravity version</li>
539
+ <li>Node.js version (<code>node --version</code>)</li>
540
+ <li>Operating system</li>
541
+ </ol>
542
+ <p>We&#39;re here to help! 🛠️</p>