LaskoBOT

What is LaskoBOT about?

LaskoBOT delivers a unified automation platform built on the Model Context Protocol (MCP). It runs a WebSocket daemon (default port 8765) that can host many independent sessions—each mapped to its own browser tab—allowing concurrent interactions without cross‑talk. Chrome and Firefox extensions expose a rich set of tools (navigation, DOM actions, snapshots, JavaScript execution, tab management, etc.) that can be invoked from any MCP‑compatible client such as Claude Desktop.

How to use LaskoBOT?

1. Prerequisites: Node.js 20+, Chrome or Firefox, and an MCP‑compatible client (e.g., Claude Desktop).
2. Installation:
   • Clone the repository and run the deploy script:

     git clone https://github.com/david-strejc/browsermcp-enhanced.git
     cd browsermcp-enhanced
     ./scripts/deploy
     

   • Or install manually with npm:

     npm install
     npm run build
     

3. Start the daemon (systemd script or run the built server directly).
4. Load the browser extension:
   • Chrome: chrome://extensions → Load unpacked → chrome-extension/
   • Firefox: about:debugging#/runtime/this-firefox → Load Temporary Add‑on → firefox-extension/manifest.json
5. Configure the client to point to http://127.0.0.1:3000/mcp (HTTP front‑end) and let it communicate with the WS daemon on port 8765.
6. Invoke tools via MCP calls, e.g.:

   await browser_navigate({url: "https://example.com"})
   await js.execute({code: "return document.title"})
   

Key features of LaskoBOT

• Single WebSocket daemon serving unlimited concurrent sessions.
• Per‑session tab routing ensures each AI instance works with its own isolated tab.
• Unified API across Chrome and Firefox (navigation, clicks, typing, screenshots, JS execution, accessibility snapshots, etc.).
• Auto‑reconnect logic, especially for Firefox (alarms + online hooks).
• Safety modes: default sandboxed execution; optional unsafe mode toggled in extension.
• Environment‑driven configuration (allowed origins, custom ports).
• Comprehensive test suite, type‑checking, and development watch mode.

Use cases of LaskoBOT

• Multi‑agent web tasks: run several Claude instances concurrently, each filling separate forms or scraping different pages.
• Cross‑browser testing: execute the same automation script on Chrome and Firefox without code changes.
• Enterprise UI automation: automate internal tools behind strict CSP by enabling unsafe mode selectively.
• Rapid prototyping: spin up a local MCP server and control browsers directly from AI assistants.
• Continuous integration: integrate the daemon into CI pipelines to verify web‑app behaviours.

FAQ from LaskoBOT

Q: Do I need to run separate servers for Chrome and Firefox? A: No. The single daemon handles both browsers; the extensions negotiate the correct engine per session.

Q: How are sessions isolated? A: Each session is tied to a unique browser tab. The daemon routes MCP calls to the owning tab, preventing cross‑talk.

Q: Can I change the WebSocket port? A: Yes. Set BROWSER_MCP_PORT environment variable before starting the daemon.

Q: What if a site blocks script injection? A: Enable the unsafe mode in the Firefox extension options; use it only for trusted sites.

Q: Is there support for Safari? A: Safari support is planned for the upcoming v2.0.0 release.

LaskoBOT — Protocol v2, Multi‑Instance, Cross‑Browser

LaskoBOT v1.30.7

Modern MCP server + browser extensions for reliable, multi‑instance automation over a single WebSocket daemon.

✨ Features

✨ Highlights

• Single WS daemon (8765), many sessions (Claude instances)
• Per‑session tab routing and ownership (no cross‑talk)
• Unified tools across Chrome and Firefox
• Auto‑reconnect (Firefox adds alarms + online hooks)

🚀 Quick Start

Prerequisites

• Node.js 20+
• Chrome or Firefox
• Claude Code
• Also works with WSL2 and Windows Chrome

Installation

Step 1 - Deploy Script

git clone https://github.com/david-strejc/browsermcp-enhanced.git
cd browsermcp-enhanced
./scripts/deploy

Step 2 - install systemd services (HTTP + WS daemon):

• Option A: User services (recommended for nvm users, no sudo required):

  ./scripts/systemd-user-install.sh
  

• Option B: System services (requires sudo):

  sudo ./scripts/systemd-install.sh --user "$USER" \
    --install-dir "/home/$USER/.local/lib/browsermcp-enhanced" \
    --http-port 3000 --ws-port 8765
  

Step 3 - Load extension (one browser at a time):

• Chrome: chrome://extensions → Developer mode → Load unpacked → chrome-extension/
• Firefox: about:debugging#/runtime/this-firefox → Load Temporary Add‑on → firefox-extension/manifest.json

Step 4 - Configure MCP

  {
    "mcpServers": {
      "browsermcp": {
        "type": "http",
        "url": "http://127.0.0.1:3000/mcp"
      }
    }
  }

For detailed architecture and troubleshooting information, see ADVANCE_INFO.md

🐛 Known Issues

• WebSocket reconnection may require Chrome restart
• Some sites with strict CSP may require unsafe mode
• Safari and Firefox support coming in v2.0.0
• Behind proxy: If you're behind a proxy, set NO_PROXY=localhost,127.0.0.1 to allow local connections

📖 Usage

Basic Navigation

// Navigate to a URL
await browser_navigate({ url: "https://example.com" })

// Snapshot
await snapshot.accessibility({ mode: 'scaffold' })

// Click an element
await browser_click({ ref: "button-1", element: "Submit button" })

JavaScript Execution

// Plain DOM
await js.execute({ code: "return document.title" })

// Safe operation (no code)
await js.execute({ method: 'query', args: ['h3', { attrs: ['textContent'], limit: 10 }] })

// Unsafe (enable in extension options first)
await js.execute({ code: "(function(){ return location.href })()", unsafe: true })

Form Automation

// Multi-step form filling
await browser_multitool({
  intent: "form_fill",
  snapshot: snapshotData,
  fields: {
    "username": "john.doe",
    "email": "john@example.com",
    "message": "Hello world"
  }
})

Debugging & Logs

Daemon: /tmp/browsermcp-daemon.log, /tmp/browsermcp-events.log Chrome: chrome://extensions → Inspect (background) Firefox: about:debugging → Inspect (background)

🔧 Advanced Configuration

Environment Variables

# Allow all origins (development)
BROWSER_MCP_ALLOWED_ORIGINS="*"

# Specific origins (production)
BROWSER_MCP_ALLOWED_ORIGINS="https://example.com,https://app.example.com"

# Custom WebSocket port
BROWSER_MCP_PORT=8765

Extension Options (Firefox)

• Unsafe mode toggle (required for unsafe: true)

📚 API Reference

Core Tools

• browser_navigate, browser_go_back, browser_go_forward
• dom.click, dom.type, dom.hover, dom.select
• snapshot.accessibility
• tabs.list, tabs.select, tabs.new, tabs.close
• console.get, screenshot.capture, js.execute

🧪 Testing

# Run tests
npm test

# Quick test
npm run test:quick

# With coverage
npm run test:coverage

🛠️ Development

# Watch mode
npm run watch

# Type checking
npm run typecheck

# Inspector
npm run inspector

📝 Changelog

See CHANGELOG.md for detailed version history.

v1.0.0 (Latest)

• 🚀 First production-ready release
• ✅ RPC-based safe mode execution
• ✅ Sandboxed iframe isolation
• ✅ Comprehensive testing suite
• ✅ Full documentation

🤝 Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

1. Fork the repository
2. Create your feature branch (git checkout -b feature/AmazingFeature)
3. Commit your changes (git commit -m 'Add some AmazingFeature')
4. Push to the branch (git push origin feature/AmazingFeature)
5. Open a Pull Request

📄 License

This project is licensed under the MIT License - see the LICENSE file for details.

🙏 Acknowledgments

• Model Context Protocol team for the MCP specification
• Playwright for browser automation inspiration
• Claude and the o3 model for architectural guidance
• All contributors and testers

🐛 Known Issues

• WebSocket reconnection may require Chrome restart
• Some sites with strict CSP may require unsafe mode
• Safari and Firefox support coming in v2.0.0

📞 Support

• Issues
• Discussions
• Release Notes

---

Made with ❤️ by the LaskoBOT Contributors