What's Changed

• Fix browser_evaluate to show JavaScript errors instead of returning undefined (#34)

Full Changelog: v1.9.18...v1.9.19

Changes

• Fix Firefox service worker suspension causing popup errors (keepalive alarm)
• Make :has-text() selector fully case-insensitive
• Clean up extension locales to match Chrome Web Store supported list (53 locales)
• Force English 'for Firefox' in all locale extName fields to pass Mozilla validation

Downloads

• Chrome: blueprint-mcp-chrome-v1.9.18.zip
• Firefox: blueprint-mcp-firefox-v1.9.18.zip
• Opera: blueprint-mcp-opera-v1.9.18.zip
• Edge: blueprint-mcp-edge-v1.9.18.zip

Changes

• Fix Enter key not triggering form submission in textareas (#30)
  • Changed Input.dispatchKeyEvent to use Chrome debugger protocol for trusted keyboard events
  • Fixes issue where pressing Enter in Google search textarea would insert newline instead of submitting

Assets

• Chrome extension: blueprint-mcp-chrome-v1.9.15.zip
• Firefox extension: blueprint-mcp-firefox-v1.9.15.zip
• Opera extension: blueprint-mcp-opera-v1.9.15.zip
• Edge extension: blueprint-mcp-edge-v1.9.15.zip

Bug Fixes

• Fixed screenshot failures caused by Chrome debugger detachment

Details

When the Chrome debugger gets detached from a tab (e.g., user opens DevTools, navigates to certain pages, or extension reloads), the extension was not tracking this state change. The debuggerAttached flag would remain true even though the actual debugger connection was gone, causing screenshot attempts to fail with 'Debugger is not attached to the tab' errors.

This fix adds a listener for the chrome.debugger.onDetach event to properly reset the debugger state when detachment occurs. On the next screenshot attempt, the extension will automatically re-attach the debugger.

Common causes of debugger detachment:

• User opens DevTools on the tab
• Navigation to certain protected pages
• Extension reload
• Tab crash or suspension

Full Changelog: v1.9.13...v1.9.14

Bug Fixes

• Fixed custom browser names not appearing in browser list when using PRO mode with multiple browsers

Details

When users set a custom browser name in extension settings (PRO feature), the name wasn't being sent to the relay server during authentication. This caused the browser list to show generic names like 'Chrome' and 'Chrome' instead of the custom names users configured (e.g., 'Work Chrome' and 'Personal Chrome').

The fix ensures that custom browser names from storage are now properly sent during authentication, falling back to the default browser type if no custom name is set.

Full Changelog: v1.9.12...v1.9.13

Changes

• Updated extension manifest descriptions with clearer value proposition
• Added documentation for --port CLI option

Extension Descriptions

All browser extensions now have improved descriptions highlighting key benefits:

• Token efficiency (CSS selectors instead of snapshots)
• Open source transparency
• Zero telemetry/tracking
• Claude integration

Documentation

• Added --port option to Command Line Options section
• Enhanced troubleshooting guide for port conflicts

Installation

npm install @railsblueprint/blueprint-mcp@latest

Or for Claude Code:

claude mcp add browser npx @railsblueprint/blueprint-mcp@latest

Browser Extensions

• Chrome: https://chromewebstore.google.com/detail/blueprint-mcp-for-chrome/kpfkpbkijebomacngfgljaendniocdfp
• Firefox: https://addons.mozilla.org/firefox/addon/blueprint-mcp-for-firefox/

Changes

• Fixed README inclusion in npm package (now visible on npmjs.com)
• Release script now automatically copies README to server directory

Installation

npm install @railsblueprint/blueprint-mcp@latest

Or for Claude Code:

claude mcp add browser npx @railsblueprint/blueprint-mcp@latest

Browser Extensions

• Chrome: https://chromewebstore.google.com/detail/blueprint-mcp-for-chrome/kpfkpbkijebomacngfgljaendniocdfp
• Firefox: https://addons.mozilla.org/firefox/addon/blueprint-mcp-for-firefox/

Changes

• Added README to npm package
• Added post-install instructions with setup guide
• Fixed Firefox extension link
• Published deprecation package @railsblueprint/chrome-mcp v1.6.0
  • Automatically installs blueprint-mcp
  • Shows migration instructions
  • Maintains backward compatibility

Installation

npm install @railsblueprint/blueprint-mcp@latest

Or for Claude Code:

claude mcp add browser npx @railsblueprint/blueprint-mcp@latest

Browser Extensions

• Chrome: https://chromewebstore.google.com/detail/blueprint-mcp-for-chrome/kpfkpbkijebomacngfgljaendniocdfp
• Firefox: https://addons.mozilla.org/firefox/addon/blueprint-mcp-for-firefox/

Migration from chrome-mcp

If you're using @railsblueprint/chrome-mcp, please migrate to @railsblueprint/blueprint-mcp:

npm uninstall @railsblueprint/chrome-mcp
npm install @railsblueprint/blueprint-mcp

Fixes

• Fix full-page screenshots not capturing beyond viewport
• Add clear error message for file:// URL navigation without permission

Full-page Screenshots

Previously, the fullPage parameter was ignored and screenshots only captured the viewport. Now when fullPage: true is specified, screenshots correctly capture the entire scrollable page.

File URL Support

When attempting to navigate to file:// URLs without the required permission, users now receive a clear message:
"Cannot navigate to file:// URLs. Please enable 'Allow access to file URLs' in chrome://extensions/ for Blueprint MCP extension."

Downloads

Browser extension packages for store submissions:

• Chrome: releases/chrome/blueprint-mcp-chrome-v1.9.9.zip
• Firefox: releases/firefox/blueprint-mcp-firefox-v1.9.9.zip
• Opera: releases/opera/blueprint-mcp-opera-v1.9.9.zip
• Edge: releases/edge/blueprint-mcp-edge-v1.9.9.zip

Full Changelog

See CHANGELOG.md for detailed changes.

Fixes

• Fix WebSocket connection stability issues causing constant disconnections
• Reject duplicate connections when multiple browsers try to connect
• Add ping/pong keepalive to prevent Chrome service worker suspension
• Improve debug logging (ExtensionServer now uses file logger)
• Log WebSocket close codes and reasons for better debugging

Downloads

Browser extension packages for store submissions:

• Chrome: releases/chrome/blueprint-mcp-chrome-v1.9.8.zip
• Firefox: releases/firefox/blueprint-mcp-firefox-v1.9.8.zip
• Opera: releases/opera/blueprint-mcp-opera-v1.9.8.zip
• Edge: releases/edge/blueprint-mcp-edge-v1.9.8.zip

Full Changelog

See CHANGELOG.md for detailed changes.