bwb-browser
With this server, you can:
Navigate to URLs, go back, and retrieve the current page URL and title.
Extract page content: full HTML, visible text, or list interactive elements (links, buttons, inputs, headings) by CSS selector.
Interact with pages: click elements, fill forms, execute JavaScript, and wait for elements to appear or disappear.
Monitor live page events: capture console logs, network requests, navigations, and JavaScript exceptions in real time.
Manage browser sessions: save and load cookies to preserve login state across restarts.
Diagnose page health: get performance metrics, console errors, broken images, and an overall health score.
Work with multiple tabs: create, close, switch, and list tabs.
Capture screenshots with full-page and quality options, and adjust the viewport size for responsive testing.
Use natural language commands (via
browser_act) to instruct the browser with plain English, like 'search for X' or 'click the login button'.Normalize browser fingerprints for realistic testing, and restart the browser when needed.
Integrate with any MCP-compatible AI agent (e.g., Claude Code, OpenCode) for seamless automation.
All this runs with minimal footprint (zero dependencies, ~1MB total install) on Linux, macOS, Windows, Android (Termux), Docker, and CI environments.
Supports Android/Termux with native Chromium installation, enabling browser automation on mobile devices.
Uses Google Chrome via Chrome DevTools Protocol for browser automation, including navigation, screenshots, and live event capture.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@bwb-browseropen https://example.com and capture network events"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
bwb-browser
Browser Without Bloat — 76KB. 25 tools. Zero dependencies. Runs on your phone.
A lightweight MCP server that gives any AI agent browser superpowers. Written by a guy in India on Termux because the existing tools were 200MB of "why."
The Pitch (60 seconds)
Every other MCP browser tool ships a full browser binary. Playwright MCP? ~250MB. Puppeteer MCP? ~400MB. Chrome DevTools MCP? ~350MB.
bwb uses raw Chrome DevTools Protocol (CDP) — the same protocol Chrome speaks natively. It auto-detects the browser already on your system. No downloads. No binary mismatches. No "why is my disk full" panic.
Factor | bwb | Playwright MCP | Puppeteer MCP |
Source size | 76KB | ~50MB+ | ~100MB+ |
Total install | ~1MB | ~250MB | ~400MB |
Bundled browser | None | Chromium (~200MB) | Chromium (~300MB) |
Works on Termux/Android | ✅ Yes | ❌ | ❌ |
Zero deps (no node_modules hell) | ✅ Yes | ❌ | ❌ |
Live event streaming | ✅ | ❌ | ❌ |
Natural language interaction | ✅ | ❌ | ❌ |
Persistent sessions | ✅ | ❌ | ❌ |
CPU profile at idle | Basically nothing | 🐌 | 🐌 |
Related MCP server: Browser Jet Pilot
🔥 The Features That Actually Matter
1. browser_act — Talk to the Browser Like a Human
browser_act({instruction: "search for laptops under a thousand dollars"})No findElement hell. No chaining 10 calls. bwb parses what you want, finds the right elements, interacts, and returns the result. Pure DOM heuristics — no LLM dependency, no API costs, no "the AI is thinking..." spinner.
2. browser_watch — See What the Page Is Doing
This is the one feature nobody else has. Your agent can listen to the page:
browser_watch({action: "start", events: ["console", "network"]})
// ... do stuff ...
const events = browser_watch({action: "poll"})
// → [{type: "console", text: "React mounted"}, {type: "network", url: "https://api.example.com/data", status: 200}]Console logs. Network requests. JS exceptions. Page navigations. Your agent isn't flying blind anymore.
3. "Login Once, Agent Works for Days"
// Monday: Login
browser_saveCookies({name: "gmail"})
// Wednesday: Still logged in. Fresh browser. Zero fuss.
browser_loadCookies({name: "gmail"})
browser_goto({url: "https://gmail.com"}) // Already authenticatedSessions persist across agent restarts, server restarts, even across different machines.
4. browser_diagnose — Lighthouse for Your AI Agent
One call gets you: performance metrics, console errors, broken images, meta tags, interaction count, and a health score. Your agent can self-diagnose instead of guessing.
5. Multi-Tab & Sessions
Create tabs, close them, switch between them, save cookies, load them back. Like a real browser. Because it is one.
6. Realistic Browser Profile
Normalizes navigator.webdriver, plugins, languages, and user-agent for testing environments. Not "stealth mode" — just honest fingerprint normalization so your tests actually match real user conditions.
Quick Install
npm install -g bwb-browser
bwb --version
# → bwb-browser 3.1.1Done. If you have Chrome/Chromium anywhere on your system, bwb finds it. No config files. No environment variables. Just works.
On Termux/Android:
pkg install chromium # One-time
npm install -g bwb-browser
bwbYes, this runs on a phone. Yes, it's fully functional. Yes, I built it this way on purpose.
All 25 Tools
Tool | Description |
| 🔥 Natural language — "search for X", "click the button", "what's on this page" |
| 🔥 Live event capture — console, network, errors, navigation |
| 🔥 Full page health check — perf, errors, broken images, score |
| 🔥 Realistic browser profile for testing |
| Navigate to a URL |
| Take a screenshot |
| Get page/selector HTML |
| Get page/selector text |
| Get page title |
| Get current URL |
| Go back in history |
| Click an element (native CDP) |
| Fill an input field (native CDP) |
| List interactive elements |
| Execute JavaScript |
| Change viewport size |
| Wait for element to appear/disappear |
| Create new tab |
| Close a tab |
| Switch to a tab |
| List all tabs |
| Save session to disk |
| Load session from disk |
| List saved sessions |
| Browser connection info |
| Restart the browser |
Where It Runs
Platform | Status | Notes |
Termux/Android | ✅ Verified |
|
Linux | ✅ Verified | Auto-detects Chrome/Chromium |
macOS | ✅ Verified | Auto-detects Chrome.app |
Windows | ✅ Verified | Auto-detects Chrome.exe |
CI (GitHub Actions) | ✅ Verified | Uses system Chrome |
Docker | ✅ Verified | Just need Chrome in container |
Your Raspberry Pi | ✅ Why not | Same npm install |
MCP Agent Integration
Add this to any MCP-compatible agent's config:
{
"mcpServers": {
"bwb": {
"command": "bwb"
}
}
}Works with: Claude Code, OpenCode, Antigravity CLI, Cline, Continue.dev, Aider, Codex CLI, Cody, Windsurf, Cursor — literally anything that speaks MCP.
See AGENTS.md for copy-paste configs for each one.
The Backstory
I built this because I was tired of every browser automation tool assuming you have 400MB to spare and a desktop-class machine. I work from my phone sometimes. Termux exists. Why shouldn't browser automation work there too?
So I did what any reasonable person would do: I ignored all the existing solutions and wrote my own, using nothing but raw CDP — the protocol Chrome speaks natively. No wrappers. No abstractions. Just JSON messages over WebSocket.
The result is 76KB of source code that does what 400MB of dependencies do. It's not better code — it's less code. And sometimes less is all you need.
— Krish Tiwari (@krshforever), somewhere on an Indian train, writing code on a phone
Roadmap
bwb Cloud — hosted browser instances so your agent has a browser even when your laptop's asleep
browser_actv2 — multi-step with feedback loops (not just "search for X" but "research this topic and summarize")Recording & Replay — record sessions, replay them, debug them
Browser pool — multiple isolated instances for CI parallelization
Support
If bwb saves you time, money, or a few brain cells:
No gating. No "pro" tier. No bait-and-switch. The code is MIT forever. If you can't or won't pay, that's genuinely fine — I built this because I wanted it to exist.
License
MIT — Krish Tiwari (@krshforever)
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityBmaintenancesingle-binary MCP server that gives AI agents a browser. 66 tools for navigation, form filling, data extraction, screenshots, and DOM diffing — built on pure Chrome DevTools Protocol.Last updated7MIT
- AlicenseAqualityDmaintenanceSelf-hosted MCP server for AI browser automation. Connects to your own Chromium instance via CDP, providing tools for browser control, navigation, interaction, and content extraction.Last updated191MIT
- FlicenseBqualityBmaintenanceUltra-fast browser automation server over Chrome DevTools Protocol (CDP), exposed as MCP, enabling AI agents to control a real Chrome browser with low latency and minimal token usage.Last updated21
- Flicense-qualityDmaintenanceMCP server that connects AI agents to browser DevTools via CDP, enabling real-time access to console logs, network requests, and page state.Last updated
Related MCP Connectors
Live browser debugging for AI assistants — DOM, console, network via MCP.
A paid remote MCP for AI agent browser DevTools MCP, built to return verdicts, receipts, usage logs,
Screenshot, diff, audit and sitemap-capture any web page — 5 MCP tools for AI agents.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/krshforever/bwb-browser'
If you have feedback or need assistance with the MCP directory API, please join our Discord server