@mcpc-tech/unplugin-dev-inspector-mcp 0.1.32 → 0.1.34

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.
package/README.md CHANGED
@@ -3,11 +3,11 @@
3
3
  [![npm version](https://img.shields.io/npm/v/@mcpc-tech/unplugin-dev-inspector-mcp.svg)](https://www.npmjs.com/package/@mcpc-tech/unplugin-dev-inspector-mcp)
4
4
  [![npm downloads](https://img.shields.io/npm/dm/@mcpc-tech/unplugin-dev-inspector-mcp.svg)](https://www.npmjs.com/package/@mcpc-tech/unplugin-dev-inspector-mcp)
5
5
 
6
- **AI-powered visual debugging for React, Vue, Svelte, SolidJS, Preact & Next.js via MCP and ACP.**
6
+ **The missing runtime context for AI coding agents.**
7
7
 
8
- DevInspector connects your web app directly to your AI agent. Click any element to instantly send its source code, style, and network context to the AI for analysis and fixing.
8
+ AI can read your code, but can't see what's happening at runtime. DevInspector provides the missing context: source code location, DOM state, styles, network, console, terminal output, and screenshots.
9
9
 
10
- Works with any MCP-compatible AI client. Supports ACP agents: **Claude Code**, **Codex CLI**, **Gemini CLI**, **OpenCode**, and [more](https://agentclientprotocol.com/overview/agents).
10
+ **Two modes**: Use with your IDE's AI (Cursor, VSCode) via MCP, or run AI agents directly in the browser via ACP (**Claude Code**, **Codex CLI**, **Gemini CLI**, **OpenCode**, [more](https://agentclientprotocol.com/overview/agents)).
11
11
 
12
12
  ## Table of Contents
13
13
 
@@ -47,15 +47,14 @@ Works with any MCP-compatible AI client. Supports ACP agents: **Claude Code**, *
47
47
 
48
48
  Click any element to inspect it, or **drag to select a region**. AI gets the full context: source code location, computed styles, component hierarchy, IDs, classes, text content, and **automatically captures screenshots** for pixel-perfect visual understanding.
49
49
 
50
+ ### Page Overview & Accessibility Tree
51
+
52
+ `get_page_info` provides AI with a semantic understanding of the page: URL, viewport, and an **accessibility tree** showing landmarks, headings, forms, and links. AI can navigate the page structure without screenshots.
50
53
 
51
54
  ### Universal DevTools Access
52
55
 
53
56
  AI can access Network and Console logs from **any browser** (via client-side interception) or full Chrome DevTools (via chrome devtools mcp). It sees what you see, regardless of your environment.
54
57
 
55
- ### Smart Select
56
-
57
- Let AI do the heavy lifting. "Smart Select" automatically analyzes recent console errors and failed network requests to construct the perfect context for your debugging session.
58
-
59
58
  ### Multi-Agent Workflow
60
59
 
61
60
  Switch between agents (Claude Code, Codex, Gemini, Opencode...) and track their debugging progress visually with a **floating status bar**.
@@ -555,21 +554,47 @@ DevInspector offers two ways to interact with your AI, depending on your prefere
555
554
 
556
555
  ### `capture_element_context`
557
556
 
558
- Activates visual selector. Returns source location, DOM hierarchy, styles, dimensions, and user notes.
557
+ Capture single element context. Two modes:
558
+ - **Interactive (default)**: User clicks element to select
559
+ - **Automated**: Use `selector` param for programmatic capture
560
+
561
+ Returns: source location, DOM hierarchy, computed styles, dimensions, user notes, screenshot.
562
+
563
+ ### `capture_area_context`
564
+
565
+ Capture multiple elements in an area. Two modes:
566
+ - **Interactive (default)**: User draws rectangle to select area
567
+ - **Automated**: Use `containerSelector` or `bounds` param
568
+
569
+ Returns: array of element contexts (max 50).
570
+
571
+ ### `get_page_info`
572
+
573
+ Get page overview with accessibility tree. Returns URL, title, viewport, document size, and semantic structure (landmarks, headings, forms, links). Start here to understand the page.
559
574
 
560
575
  ### `list_inspections`
561
576
 
562
- Shows all inspections with ID, element details, notes, and status (pending/in-progress/completed/failed).
577
+ List all captured inspections with ID, element details, source location, notes, and status (pending/in-progress/completed/failed).
563
578
 
564
579
  ### `update_inspection_status`
565
580
 
566
- Updates inspection status with optional progress steps.
567
-
568
- **Parameters:** `status`, `message` (required for completed/failed), `progress`, `inspectionId` (optional)
581
+ Update inspection status. Parameters: `inspectionId` (optional, auto-detects), `status` ('in-progress'|'completed'|'failed'|'deleted'), `message` (required for completed/failed).
569
582
 
570
583
  ### `execute_page_script`
571
584
 
572
- Executes JavaScript in browser context. Access to window, document, React/Vue instances, localStorage.
585
+ Execute JavaScript in browser context. Access: window, document, DOM APIs, React/Vue instances, localStorage. Must return a value.
586
+
587
+ ### `get_network_requests`
588
+
589
+ Get network requests from browser. Returns list with reqid, method, URL, status. Use `reqid` param to get full request/response details (headers, body, timing).
590
+
591
+ ### `get_console_messages`
592
+
593
+ Get console messages from browser. Returns list with msgid, level (log/warn/error), message. Use `msgid` param to get full message details.
594
+
595
+ ### `get_stdio_messages`
596
+
597
+ Get dev server stdout/stderr. Returns list with stdioid, stream type, content. Use `stdioid` param to get full message.
573
598
 
574
599
  ### `chrome_devtools`
575
600
 
@@ -615,33 +640,35 @@ These custom tools are automatically discovered and made available to the connec
615
640
 
616
641
  ## MCP Prompts
617
642
 
618
- ### `capture_element`
643
+ ### `capture_element_context`
644
+
645
+ Capture single element context. Interactive (user clicks) or automated (selector param).
619
646
 
620
- Capture and analyze UI element context.
647
+ ### `capture_area_context`
621
648
 
622
- ### `view_inspections`
649
+ Capture multiple elements in area. Interactive (user draws rectangle) or automated (containerSelector/bounds param).
623
650
 
624
- View all pending, in-progress, and completed inspections.
651
+ ### `list_inspections`
625
652
 
626
- ### `launch_chrome_devtools`
653
+ View all element inspections in the queue with their status.
627
654
 
628
- Opens Chrome with DevTools API. Unlocks network analysis, console logs, performance metrics.
655
+ ### `launch_chrome_devtools`
629
656
 
630
- **Parameter:** `url` (defaults to dev server)
657
+ Launch Chrome DevTools and navigate to a specified URL for debugging and inspection.
631
658
 
632
- 💡 Optional if Chrome is already open. Use when you need to launch a new Chrome instance.
659
+ **Parameter:** `url` (required) - The URL to navigate to (e.g., http://localhost:3000)
633
660
 
634
661
  ### `get_network_requests`
635
662
 
636
663
  List network requests or get details of a specific one. Always refreshes the list first.
637
664
 
638
- **Parameter:** `reqid` (optional) - If provided, get details for that request. If omitted, just list all requests.
639
-
640
665
  ### `get_console_messages`
641
666
 
642
667
  List console messages or get details of a specific one. Always refreshes the list first.
643
668
 
644
- **Parameter:** `msgid` (optional) - If provided, get details for that message. If omitted, just list all messages.
669
+ ### `get_stdio_messages`
670
+
671
+ List stdio (stdout/stderr) messages from the server process. Always refreshes the list first.
645
672
 
646
673
  ## Architecture
647
674