@ironbee-ai/devtools weekly downloads statistics

IronBee DevTools

A powerful Model Context Protocol (MCP) server that provides AI coding assistants with comprehensive automation and debugging capabilities across multiple platforms. This server enables both execution-level debugging (logs, network requests) and visual debugging (screenshots, accessibility snapshots) to help AI assistants understand and interact with applications effectively.

Overview

IronBee DevTools is a platform-extensible MCP server designed to give AI agents deep inspection and control over application runtimes. The architecture supports multiple platforms through a unified interface, with each platform providing specialized tools for its environment.

Supported Platforms

| Platform | Description | Status |

| Browser | Playwright-powered browser automation with full DevTools integration | ✅ Available | | Node | Non-blocking debugging for Node.js backend processes via Inspector Protocol | ✅ Available | | Backend | Runtime- and language-agnostic backend verification (HTTP / gRPC / GraphQL / WebSocket) + log capture (file / docker / kubernetes) + database verification (Postgres / MySQL / SQLite) | ✅ Available |

The Browser Platform exposes a Playwright-powered browser runtime to AI agents, enabling deep, bidirectional debugging and interaction with live web pages. It supports both visual understanding and code-level inspection of browser state, making it ideal for AI-driven exploration, diagnosis, and automation.

The Node Platform provides non-blocking debugging for Node.js backend processes. It connects to running Node.js processes via the Inspector Protocol (Chrome DevTools Protocol over WebSocket) and offers tracepoints, logpoints, exceptionpoints, watch expressions, and source map support—ideal for debugging APIs, workers, and server-side code.

The Backend Platform binds to wire protocols, not specific frameworks: agents drive backend services via HTTP/1.1, HTTP/2, gRPC (unary + 3 streaming modes), GraphQL, and stateful WebSockets, with automatic W3C trace propagation so every request becomes a verifiable correlation root. Paired with the log_* domain, agents capture server-side log lines (from files, docker containers, or kubernetes pods) for the same trace; paired with the db_* domain, agents inspect database state directly (schema discovery, parameterized reads, before-vs-after snapshot diffs, polling change feeds) against Postgres / MySQL / SQLite — closing the "trigger and verify" loop without locking in to any framework, language, or runtime.

Platform Selection

Choose the platform by running the appropriate MCP server or CLI:

| Use Case | MCP Server | CLI |

| Browser automation & debugging | ironbee-devtools-mcp | ironbee-devtools-cli | | Node.js backend debugging | ironbee-node-devtools-mcp | ironbee-node-devtools-cli | | Backend verification (HTTP/gRPC/GraphQL/WS) + log capture + database (Postgres/MySQL/SQLite) | ironbee-backend-devtools-mcp | ironbee-backend-devtools-cli |

Browser Platform Capabilities

• Visual Inspection: Screenshots, ARIA snapshots, HTML/text extraction, PDF generation • Design Comparison: Compare live page UI against Figma designs with similarity scoring • DOM & Code-Level Debugging: Element inspection, computed styles, accessibility data • Browser Automation: Navigation, input, clicking, scrolling, viewport control • Execution Monitoring: Console message capture, HTTP request/response tracking • OpenTelemetry Integration: Automatic trace injection into web pages, UI trace collection, and backend trace correlation via trace context propagation • JavaScript Execution: Use the execute tool to batch-execute tool calls and run custom JavaScript; on the browser platform the VM receives \page\ (Playwright Page) so you can use \page.evaluate()\ or the Playwright API • Session Management: Long-lived, session-based debugging with automatic cleanup • Closed tab: If the MCP session’s browser tab was closed, the next tool run opens a new tab for that session (previous element refs are invalid until you take a new snapshot). Session network-idle / in-flight tracking state is also reset for the new tab. • Multiple Transport Modes: Supports both stdio and HTTP transports

Node Platform Capabilities

• Connection: Connect to Node.js processes by PID, process name, port, WebSocket URL, or Docker container • Non-Blocking Debugging: Tracepoints, logpoints, exceptionpoints without pausing execution • Source Map Support: Resolves bundled/minified code to original source locations; debug_resolve-source-location translates stack traces and bundle locations to original source • OpenTelemetry Integration: When the Node process uses @opentelemetry/api, tracepoint/logpoint snapshots automatically include traceContext (traceId, spanId) for correlating backend traces with browser traces • Docker Support: Connect to Node.js processes running inside Docker containers (containerId / containerName)

Backend Platform Capabilities…

Description from the npm listing.