DEV Community

Rumblingb
Rumblingb

Posted on • Originally published at agentpay.so

The Chrome Extension That Turns Your Browser into an AI Tool Platform

#chrome #mcp #ai #browserextension

My browser already has 17 extensions. Tabs, passwords, dev tools, ad blockers — every one a walled garden that can't talk to anything else.

So I built the opposite: an MCP Bridge Chrome extension that lets any AI agent control your browser.

What It Does

From Cursor, Claude, Windsurf, or any MCP client, your agent can:

  • Open tabs — navigate to URLs programmatically
  • Scrape content — extract text, links, images from pages
  • Click elements — fill forms, submit, navigate
  • Execute scripts — run JavaScript in context of any page
  • Screenshot pages — capture full-page or element-level screenshots

The browser becomes a tool. The extension is the bridge.

Why This Matters

Right now, AI agents live in terminal windows and chat boxes. They're disconnected from the web — the one platform where 99% of real work happens.

With a browser bridge:

  • A research agent can open 10 tabs, scrape all of them, and synthesize findings — autonomously
  • A QA agent can navigate your app, fill forms, and screenshot errors — without Selenium
  • A data agent can log into dashboards, export CSVs, and feed them into analysis — no API needed

The browser IS the API. The extension makes it accessible to agents.

The Stack

  • Chrome Extension Manifest V3 — modern, secure, background service worker
  • MCP Server — TypeScript, stdio transport
  • Chrome DevTools Protocol — direct browser control, no Selenium overhead
  • WebSocket bridge — extension ↔ MCP server communication

Zero external APIs. Runs entirely on your machine.

Use Case: Autonomous Research 

Agent: "Research competitors for email verification APIs"
→ Opens 5 tabs (Google, Product Hunt, G2, Reddit, Twitter)
→ Scrapes pricing, features, reviews from each
→ Synthesizes into competitive analysis markdown
→ Total time: 45 seconds
Enter fullscreen mode Exit fullscreen mode

This isn't theoretical. The bridge handles the messy parts — authentication cookies, dynamic content, iframe sandboxing — so agents focus on the work.

Security First

Agents with browser access are dangerous. So the bridge has:

  • Permission gates — you approve every domain before an agent can access it
  • Operation allowlists — granular controls: read vs. write, navigation vs. script execution
  • Audit logging — every agent action recorded with timestamp and SHA-256 hash
  • Session scoping — agent sessions expire after inactivity

No wild-west agent browsing. Governed browser access, scoped per session.

What's Next

  • Firefox + Safari support — WebExtensions API makes ports straightforward
  • AgentPassport integration — governed tokens so agents can pay for premium browser tools
  • Shared sessions — multiple agents collaborating in the same browser context

Try It

Full source on GitHub: github.com/Rumblingb

Browse 61 MCP servers + Chrome extensions: smithery.ai/servers/vishar-rumbling

Building in public. AgentPassport — governed payments for autonomous AI agents — coming soon.

Top comments (0)