Frequently Asked Questions
Common questions about Oh My Browser, MCP, Site Memory, and how to get started.
01.What is MCP and why does it matter for AI agents?
MCP (Model Context Protocol) is an open standard that lets AI agents call external tools in a structured way. Oh My Browser implements an MCP server so agents in Claude Code, Cursor, Codex, Windsurf, and other MCP clients can control a real Chrome browser with a single tool call. No custom code, no brittle Playwright wrappers — just drop the connection config and start browsing.
02.What is Site Memory?
Site Memory is Oh My Browser's learning layer. After your agent successfully interacts with a page, the extension caches the CSS selectors and page structure it used. On the next visit to the same site, it skips the discovery step and goes straight to execution. Memory is private to your account and is deleted when you delete your account.
03.What is the difference between Lite and Oh My Browser?
Lite is the Chrome Web Store build — useful for managed Chrome environments where unpacked extensions are blocked. It supports reading and acting on web pages with your logged-in sessions, but Web Store sandbox limits cap it at one concurrent tab and exclude Site Memory. Oh My Browser (the curl-installed default build) unlocks the full capability set: Site Memory, up to 8 concurrent tabs, and CDP-level browser control. It's the recommended build for production agent workflows.
04.Does Oh My Browser share my browsing data with the AI agent?
No. The extension does not stream your browsing history or session tokens to the agent. The agent sends a task (e.g., 'read this URL') and receives only the result of that task. Your cookies and credentials stay in Chrome. The extension does cache anonymized site-structure signals (selectors, page layout) to power Site Memory — these are private to your account and never shared across users.
05.How do I install Oh My Browser for Claude Code or Cursor?
Install the Chrome extension from the Chrome Web Store, then run `npx @omb/cli --mcp` in your terminal. The CLI prints an MCP config block — paste it into your Claude Code or Cursor MCP settings file and restart the client. Full step-by-step instructions are on the Install page.