1. Conduid
  2. Browser
  3. DevTool MCP
MCP server · Browser

DevTool MCP

Development tooling MCP server with process management, proxy, and frontend diagnostics

Unclaimed browser
37Low

Scored 6 months ago · breakdown

About DevTool MCP

DevTool MCP is an MCP server in the Browser category: development tooling MCP server with process management, proxy, and frontend diagnostics.

Install

Claude Code
claude mcp add devtool-mcp -- npx -y @standardbeagle/devtool-mcp
npx
npx -y @standardbeagle/devtool-mcp
uvx
uvx devtool-mcp
pip
pip install devtool-mcp

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Tools (15)

api_auditAPI-efficiency audit: waterfall, N+1, duplicate, chatty-load

Parameters not published.

channel_replySend messages to developer's browser overlay (channel mode only)

Parameters not published.

currentpageView active page sessions with grouped resources

Parameters not published.

daemonManage background daemon service

Parameters not published.

detectAuto-detect project type and available scripts

Parameters not published.

get_incidentsAuthoritative pull from the always-active incident inbox

Parameters not published.

loading_auditLoading-UX audit: spinner cascade + concurrent fragmentation

Parameters not published.

procManage processes: status, output, stop, list

Parameters not published.

proxyReverse proxy: start, stop, exec, status

Parameters not published.

proxylogQuery logs: http, error, screenshot, sketch, panel_message

Parameters not published.

Show all 15 tools
responsive_auditResponsive audit across viewport sizes (layout/overflow/a11y)

Parameters not published.

runExecute scripts or commands (background/foreground)

Parameters not published.

snapshotVisual regression: baseline/compare screenshots

Parameters not published.

tunnelTunnel management: cloudflare/ngrok for mobile testing

Parameters not published.

watchStream daemon events via `agnt monitor`

Parameters not published.

Ask AI

✦

Ask AI about DevTool MCP

Powered by Claude · Grounded in docs

I know everything about DevTool MCP. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ✓README presentThe repository ships documentation.

5 checks have not been run yet.

README

agnt

Give your AI coding agent browser superpowers.

Go Version MCP npm PyPI License

What is agnt?

agnt is a new kind of tool designed for the age of AI-assisted development. It acts as a bridge between your AI coding agent and the browser, extending what's possible during vibe coding sessions.

When you're in the flow with Claude Code, Cursor, or other AI coding tools, agnt lets your agent:

  • See what you see - Screenshots, DOM inspection, and visual debugging
  • Hear from you directly - Send messages from the browser to your agent
  • Sketch ideas together - Draw wireframes directly on your UI
  • Debug in real-time - Capture errors, network traffic, and performance metrics
  • Test on any device - Tunnel to phones and BrowserStack with full instrumentation
  • Extend its thinking window - Structured data uses fewer tokens than your descriptions

Demo

Sketch Demo

Draw wireframes directly on your running app, then send them to your AI agent

The Vision: Extending Your Agent's Capabilities

Traditional AI coding assistants are blind to what's happening in the browser. They can write code, but they can't:

  • See the visual result of their changes
  • Know when JavaScript errors occur
  • Understand layout issues you're experiencing
  • Receive feedback without you typing it out

agnt changes this. It creates a bidirectional channel between your browser and your AI agent:

┌─────────────────┐      ┌─────────────────┐      ┌─────────────────┐
│   Your Browser  │ ←──► │      agnt       │ ←──► │   AI Agent      │
│                 │      │                 │      │                 │
│  - See changes  │      │  - Proxy traffic│      │  - Receives     │
│  - Send notes   │      │  - Capture errors│     │    context      │
│  - Draw sketches│      │  - Inject tools │      │  - Acts on      │
│  - Click to log │      │  - Route messages│     │    feedback     │
└─────────────────┘      └─────────────────┘      └─────────────────┘

Quick Start

Installation

npm (recommended):

npm install -g @standardbeagle/agnt

pip/uv:

pip install agnt
# or
uv pip install agnt

From source:

git clone https://github.com/standardbeagle/agnt.git
cd agnt
make build && make install-local

As MCP Server (Claude Code, Cursor, etc.)

Add to your MCP configuration:

{
  "mcpServers": {
    "agnt": {
      "command": "agnt",
      "args": ["mcp"]
    }
  }
}

Or install as a Claude Code plugin:

/plugin marketplace add standardbeagle/agnt
/plugin install agnt@agnt

As PTY Wrapper (Enhanced Terminal)

Wrap your AI tool for overlay features:

agnt run claude --dangerously-skip-permissions
agnt run cursor
agnt run aider

This adds a terminal overlay menu (Ctrl+P) and enables the browser-to-terminal message bridge.

Channel Mode (Beta — Claude Code only)

Beta / Experimental: Channel mode requires a forked MCP SDK and a development flag in Claude Code. Behavior and schema may change.

Claude Code v2.1.80+ can receive real-time browser errors, diagnostics, and user interactions as push events in context -- without the PTY wrapper. Add channel { enabled true } to .agnt.kdl and launch with claude --dangerously-load-development-channels server:agnt. See the Channel Mode section in CLAUDE.md for full schema, event format, and the channel_reply tool for sending messages back to the browser overlay.

Core Features

1. Browser Superpowers

Start a proxy and your agent gains eyes into the browser:

proxy {action: "start", id: "app", target_url: "http://localhost:3000"}

Now your agent can:

// Take screenshots
proxy {action: "exec", id: "app", code: "__devtool.screenshot('current-state')"}

// Inspect any element
proxy {action: "exec", id: "app", code: "__devtool.inspect('#submit-button')"}

// Audit accessibility
proxy {action: "exec", id: "app", code: "__devtool.auditAccessibility()"}

// Check what the user clicked
proxy {action: "exec", id: "app", code: "__devtool.interactions.getLastClickContext()"}

2. The Floating Indicator

Every proxied page gets a small floating bug icon. Click it to:

  • Send messages directly to your AI agent
  • Take screenshots of specific areas
  • Select elements to log their details
  • Open sketch mode for wireframing

No more alt-tabbing to describe what you see - just click and send.

3. Sketch Mode

Press the sketch button and draw directly on your UI:

  • Rectangles, circles, arrows, and freehand drawing
  • Wireframe elements: buttons, inputs, sticky notes
  • Save and send to your agent with one click

Perfect for saying "I want a button here" or "this layout is wrong" without typing a word.

4. Real-Time Error Capture

JavaScript errors are automatically captured and available to your agent:

proxylog {proxy_id: "app", types: ["error"]}
→ {message: "TypeError: Cannot read property 'map' of undefined",
   stack: "at ProductList (products.js:42)",
   timestamp: "..."}

Your agent sees errors as they happen, not when you remember to mention them.

5. Extending the Thinking Window

Structured data consumes fewer tokens than natural language descriptions:

  • Error summaries - proxylog {types: ["error"]} vs. "I'm seeing a TypeError on line 42 that says..."
  • Click context - interactions.getLastClickContext() vs. "I clicked the blue button in the header..."
  • DOM state - inspect('#element') vs. "there's a div with some nested spans and..."
  • Consolidated stack traces - Pre-processed React error walls into actionable summaries
  • Status at a glance - Structured JSON your agent can parse efficiently

Instead of dumping 100 lines of nested React errors into the context, agnt consolidates verbose output into concise, actionable data.

MCP Tools

Tool Description
detect Auto-detect project type and available scripts
run Execute scripts or commands (background/foreground)
proc Manage processes: status, output, stop, list
proxy Reverse proxy: start, stop, exec, status
proxylog Query logs: http, error, screenshot, sketch, panel_message
currentpage View active page sessions with grouped resources
tunnel Tunnel management: cloudflare/ngrok for mobile testing
daemon Manage background daemon service
channel_reply Send messages to developer's browser overlay (channel mode only)

Browser API (50+ Functions)

The proxy injects window.__devtool with powerful diagnostics:

Element Inspection

__devtool.inspect('#element')     // Full element analysis
__devtool.getPosition('#element') // Bounding box and position
__devtool.isVisible('#element')   // Visibility check

Visual Debugging

__devtool.highlight('.items')           // Highlight elements
__devtool.mutations.highlightRecent()   // Show recent DOM changes
__devtool.screenshot('name')            // Capture screenshot

Accessibility

__devtool.auditAccessibility()    // Full a11y audit with score
__devtool.getContrast('#text')    // Color contrast check
__devtool.getTabOrder()           // Tab navigation order

Interactions

__devtool.interactions.getLastClick()        // Last click details
__devtool.interactions.getLastClickContext() // Full click context
__devtool.selectElement()                    // Interactive picker

Sketch Mode

__devtool.sketch.open()    // Enter sketch mode
__devtool.sketch.save()    // Save and send to agent
__devtool.sketch.toJSON()  // Export sketch data

Configuration

Create .agnt.kdl in your project root to auto-start scripts, proxies, and configure browser notifications:

// Scripts to run via daemon process manager
scripts {
    dev {
        run "npm run dev"           // Shell command (recommended)
        autostart true
        url-matchers "(Local|Network):\\s*{url}"
    }

    api {
        command "go"                // Or use command + args
        args "run" "./cmd/server"
        autostart true
        env {
            GIN_MODE "debug"
        }
        cwd "./backend"
    }
}

// Reverse proxies with traffic logging
proxies {
    frontend {
        script "dev"               // Link to script for URL auto-detection
    }

    backend {
        target "http://localhost:8080"
        autostart true
        max-log-size 2000
    }
}

// Browser notifications when AI responds
hooks {
    on-response {
        toast true                 // Show toast notification
        indicator true             // Flash bug indicator
        sound false                // Play notification sound
    }
}

// Toast appearance
toast {
    duration 4000
    position "bottom-right"        // top-right, top-left, bottom-right, bottom-left
    max-visible 3
}

Run /setup-project in Claude Code to interactively generate this configuration.

Framework-specific URL matchers:

Framework url-matchers
Next.js / Vite / React "(Local|Network):\\s*{url}"
Wails "DevServer URL:\\s*{url}"
Astro "Local\\s+{url}"
Jekyll "Server address:\\s*{url}"
Hugo "Web Server.*available at {url}"

Architecture

agnt uses a daemon architecture for persistent state:

┌─────────────────────┐       ┌─────────────────────────────────────┐
│  AI Agent           │       │              agnt                   │
│  (Claude Code, etc.)│◄─────►│                                     │
│                     │ MCP   │  ┌────────────────┐                 │
└─────────────────────┘       │  │  MCP Server    │                 │
                              │  └───────┬────────┘                 │
                              │          │ socket                   │
                              │          ▼                          │
┌─────────────────────┐       │  ┌────────────────────────────────┐ │
│  Browser            │◄──────┼──│        Daemon                  │ │
│                     │ proxy │  │  ProcessManager │ ProxyManager │ │
│  __devtool API      │       │  └────────────────────────────────┘ │
│  Floating Indicator │       └─────────────────────────────────────┘
│  Sketch Mode        │
└─────────────────────┘

Key design decisions:

  • Lock-free concurrency with sync.Map and atomics
  • Bounded memory with ring buffers
  • Processes and proxies survive client disconnections
  • Zero-dependency frontend JavaScript

Documentation

Full Documentation →

# Run docs locally
cd docs-site
npm install && npm start

Use Cases

  • Vibe coding - Stay in flow while your agent sees everything
  • Visual debugging - Show don't tell - sketch what's wrong
  • Mobile testing - Tunnel your dev server for real device testing with Cloudflare/ngrok + BrowserStack integration
  • Accessibility testing - Automated a11y audits during development
  • Error tracking - Catch frontend errors before users do
  • UI reviews - Annotate designs directly on the live app
  • Remote collaboration - Share visual context with your agent

Requirements

  • Node.js 18+ or Go 1.24+
  • MCP-compatible AI assistant

Migrating from devtool-mcp

agnt is the new name for devtool-mcp. Existing users:

# npm
npm uninstall -g @standardbeagle/devtool-mcp
npm install -g @standardbeagle/agnt

# pip
pip uninstall devtool-mcp
pip install agnt

Update your MCP config to use agnt command with ["mcp"] args.

License

MIT

Contributing

Contributions welcome! See the documentation for architecture details.

README copy captured when this server was indexed; it may lag the repository. The original is authoritative.

Questions

About DevTool MCP

How do I install DevTool MCP?

Run claude mcp add devtool-mcp -- npx -y @standardbeagle/devtool-mcp, then add the server to your MCP client's configuration.

Is DevTool MCP safe to use with an AI agent?

Its trust score is 37 out of 100 (low). It passes 1 of the 1 static security checks run so far. It has no ConduID identity yet, so agent calls to it are not receipted.

Is DevTool MCP still maintained?

Conduid hasn't recorded a commit date for this repository yet. Check the repository directly for recent activity.