bwb-browser-termux
Controls Google Chrome browser for web automation tasks such as navigation, screenshotting, element interaction, and JavaScript execution via Chrome DevTools Protocol.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
bwb-browser-termux
Browser Without Bloat — a lightweight browser automation MCP server using raw Chrome DevTools Protocol (CDP).
No Playwright. No Puppeteer. Just CDP.
Works on Termux/Android, Linux, macOS, and Windows.
Why bwb?
Feature | bwb | Playwright MCP | Puppeteer MCP |
Dependencies | 3 packages | 50+ packages | 30+ packages |
Install size | ~2MB | ~500MB+ | ~300MB+ |
Works on Termux | ✅ | ❌ | ❌ |
Works in CI | ✅ | ⚠️ Needs browser download | ⚠️ Needs browser download |
Uses existing Chrome | ✅ | ❌ Downloads its own | ❌ Downloads its own |
Related MCP server: tabby-mcp
Installation
npm install -g bwb-browser-termuxOr run directly:
npx bwb-browser-termuxPrerequisites
You need Chrome or Chromium installed. bwb will auto-detect it.
Termux/Android:
pkg install chromiumLinux (Debian/Ubuntu):
sudo apt install chromium-browser
# or
sudo apt install google-chromemacOS:
brew install --cask google-chromeWindows: Download and install Google Chrome normally.
Usage
With Claude Desktop / OpenCode / any MCP client
Add to your MCP client config:
{
"mcpServers": {
"bwb": {
"command": "npx",
"args": ["bwb-browser-termux"]
}
}
}For Termux, you may need the full path:
{
"mcpServers": {
"bwb": {
"command": "node",
"args": ["/path/to/bwb-browser-termux/server.js"]
}
}
}Command line
# Start the MCP server (stdio)
bwb
# With custom browser path
bwb --browser-path /usr/bin/chromium
# Custom CDP port
bwb --port 9333
# Visible browser (not headless)
bwb --headless false
# See all options
bwb --helpConfiguration
CLI flag | Env var | Default | Description |
|
| auto-detected | Path to Chrome/Chromium binary |
|
|
| Remote debugging port |
|
|
| Browser profile directory |
|
|
| Run headless ( |
Tools (11)
Tool | Description |
| Navigate to a URL |
| Take a screenshot |
| Get page/selector HTML |
| Get page/selector text |
| Click an element by CSS selector |
| Fill an input field |
| List interactive elements (links, buttons, inputs, headings) |
| Get current page title |
| Get current URL |
| Execute JavaScript in page context |
| Browser connection status |
License
MIT © krsh
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Official Browserless MCP server: browser automation, scraping, screenshots and PDFs for AI agents.
Browserless MCP — wraps the Browserless headless-Chromium REST API (browserless.io)
Web scraping, browser automation, screenshots and AI data extraction for AI agents via MCP.
A remote MCP server to convert HTML documents (URL or raw source) to PDF or screenshots
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides tools for interacting with Chrome through its DevTools Protocol, enabling remote control of Chrome tabs to execute JavaScript, capture screenshots, monitor network traffic, and more.96 npm52MIT
- AlicenseAqualityDmaintenanceA lightweight MCP server that enables control of the Tabby terminal via Chrome DevTools Protocol, allowing execution of JavaScript, DOM queries, and screenshots.47MIT
- AlicenseAqualityDmaintenanceMCP server for controlling Chromium/Chrome via Chrome DevTools Protocol. Supports cross-platform automation, auto-launch, and automatic reconnection.251MIT
- AlicenseNot gradedqualityDmaintenanceA lightweight MCP server that enables AI assistants to control Chrome DevTools via CDP for debugging tasks like navigation, screenshots, and JavaScript execution.MIT