BrowserDebug 1.1.0

BrowserDebug v1.1.0

BrowserDebug v1.1.0 adds a local stdio MCP Server so Codex and other MCP clients can discover and invoke the existing BrowserDebug control plane through a narrow, startup-scoped interface.

Highlights

• Added the browserdebug-mcp executable and src/mcp/ adapter over the existing run, catalog, event, profile, Doctor, Stop, confirmation, and cleanup modules.
• Added nine strict tools, eight static resources, one verified run resource template, stable annotations, and a common structured success/error envelope.
• Added a path-independent manifest command and schemas/browserdebug.mcp-manifest.schema.json for machine-readable discovery.
• Added focused unit coverage and a real official-client stdio integration test that starts the server, runs a local target, reads evidence, and closes cleanly.
• Added an independent Simplified Chinese user manual at README.zh-CN.md with reciprocal language switching.
• Added the canonical MCP contract in docs/API.md and synchronized architecture, development, changelog, progress, and documentation indexes.

Safety Boundaries

• Each MCP process is permanently scoped to one explicit startup target root and an in-root configuration.
• MCP exposes no arbitrary root, file access, physical run/profile path, owner PID, control token, native browser object, raw artifact bytes, reusable approval, or confirmation bypass.
• Runs always finalize. Real external writes, isolated profiles, and destructive profile reset retain separate fresh visible confirmation requirements.
• Stop continues to use authenticated normal cleanup and has no PID fallback.

Validation

• The focused MCP suite covers manifest validation, strict inputs, annotations, error redaction, resources, official-client stdio negotiation, real local execution, evidence reading, and cleanup.
• The full resolver-backed regression, legacy MV3 probe, dual-runtime Doctor, full-stack command/API/page/MV3 fixture, dependency audit, release hygiene scan, and residue checks are part of the v1.1.0 acceptance gate.
• A live Codex MCP connection discovered all nine tools and completed the full-stack fixture with verified evidence and cleanup.
• No real external-write validation is performed.

Compatibility

• Existing CLI, graphical console, configuration versions 1 and 2, Artifact v1/v2 readers, shared general profile behavior, and compatible legacy MV3 probe remain supported.
• The MCP protocol starts at manifest schema version 1 and requires Node.js 20 or newer.

Upgrade

Pull v1.1.0, run npm install, resolve the browser environment, and register browserdebug-mcp in the MCP client with an explicit --root target. Existing non-MCP workflows require no migration.