Real Browser MCP vs Weavetab

A side-by-side look at the Real Browser MCP and Weavetab MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Real Browser MCP logoReal Browser MCPBrowser Automation · Local subprocess (stdio)MCP server + Chrome extension that gives AI agents control of the user's real browser with existing sessions, logins, and cookies. No headless browser, no re-authentication.68GreatAuth: no auth requiredWeavetab logoWeavetabBrowser Automation · Local subprocess (stdio)Open automation engine for AI agents. Control live browsers and desktop apps locally.64GoodAuth: no auth required

Verdict: choose Real Browser MCP for browser automation work as a local process; choose Weavetab for browser automation as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Real Browser MCP logoChoose Real Browser MCP when

  • You need dedicated capabilities in the Browser Automation domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like browser_navigate, browser_click, browser_type.
Explore Real Browser MCP

Weavetab logoChoose Weavetab when

  • You need dedicated capabilities in the Browser Automation domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like browser_map, browser_navigate, browser_click.
Explore Weavetab

Feature & specification comparison

Rows where the two servers differ are marked.

SpecReal Browser MCP logoReal Browser MCPWeavetab logoWeavetab
CategoryBrowser AutomationBrowser Automation
Quality signal68/100 · Great64/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNo auth required
PricingFreeFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars583
Directory activity 11 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
Tools1841

Tools & capabilities

Real Browser MCP tools 18

  • browser_navigateNavigate to a URL in the active browser tab
  • browser_clickClick an element on the page using a ref from snapshot or a CSS selector
  • browser_typeType text into an input element
  • browser_scrollScroll the page or an element. Supports pixel offsets, scrolling to elements, and named positions (top/bottom). Works with virtual scroll containers used by social media sites.
  • browser_press_keyPress a keyboard key or combination (Enter, Escape, Tab, ArrowDown, etc). Supports modifiers like Ctrl+A, Cmd+C.
  • browser_waitWait for a condition: element to appear, element to disappear, or a fixed delay. Useful for SPAs and dynamic content.
  • browser_snapshotGet an accessibility tree snapshot of the page. Returns element refs you can use with click, type, and other tools. Use compact mode (default) for smaller output - only interactive elements.
  • browser_screenshotCapture a screenshot of the visible page area
  • browser_consoleRead console messages (log, warn, error) from the browser
  • browser_networkRead network requests made by the page. Filter by URL pattern.
  • browser_tabsManage browser tabs: list, create, close, or focus
  • browser_findFind elements on the page using natural language (e.g. "login button", "search input"). Returns refs you can use with click/type.
  • +6 more on the listing page

Weavetab tools 41

  • browser_mapSnapshot interactive DOM with volatile ref IDs that invalidate after DOM mutations. For complex SPAs (e.g. GitHub dashboards), use `scope` or `query` to reduce tokens. For forms/pagination/sequential loops, ALWAYS use `delta: true` to save 97% tokens. For canvas/WebGL/Figma pages where the DOM has < 5 interactive elements, use `visual: "auto"` to get a numbered screenshot — then use browser_click({ mark: N }) to interact.
  • browser_navigateNavigate to a URL or launch/focus a configured Electron app.
  • browser_clickClick a DOM element. Use browser_canvas for charts/canvas. If stuck_warning=true, stop and use browser_map. Pass mark: N to click a numbered element from browser_map({ visual: true/"auto" }) without any DOM re-scan.
  • browser_typeType text into an input field or currently focused element. If id/selector/label is omitted, automatically types directly into document.activeElement without needing a redundant click or browser_map. If target is already focused, skips click to prevent unfocus bugs.
  • browser_type_secretInject a secret from an environment variable.
  • browser_keyPress a keyboard key.
  • browser_scrollScroll the page.
  • browser_dialogAccept or dismiss JS dialogs (alert, confirm, prompt). Browser sessions only.
  • browser_burstHIGH-SPEED MULTI-ACTION PIPELINE: Executes 2 or more sequential browser actions in a single round-trip without waiting for LLM turns between steps. PREFER THIS over individual single-action calls (e.g. typing + pressing Enter, filling multiple form fields, clicking tabs/buttons then waiting, searching, navigating + reading) to drastically slash latency and token burn. Supports native primitives (browser_click, browser_fill, browser_type, browser_type_secret, browser_navigate, browser_key, browser_scroll, browser_wait, browser_map, etc.) plus ergonomic macro steps (type_and_send, click_and_wait, navigate_and_read, scroll_and_read, fill_form). If compile_from_history: true is passed, automatically compiles recent successful session trail actions into a burst macro.
  • browser_tabsManage browser and Electron app tabs/windows (open, switch, close, list). Specify 'app' when targeting desktop apps (e.g. app: 'discord') to avoid opening web browser.
  • browser_waitPause until a condition is met.
  • browser_captchaAutonomous CAPTCHA detection and solving.
  • +29 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Real Browser MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "ofershap-real-browser-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "real-browser-mcp"
      ]
    }
  }
}

Weavetab

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "weavetab": {
      "command": "npx",
      "args": [
        "-y",
        "@weavetab/mcp"
      ]
    }
  }
}

Frequently asked questions

Real Browser MCP is categorized under Browser Automation and uses a local stdio subprocess. Weavetab belongs to Browser Automation and uses a local stdio subprocess. Pick Real Browser MCP for browser automation work and Weavetab for browser automation.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Real Browser MCP is listed as free. Auth: no auth required. Weavetab is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add ofershap-real-browser-mcp and weavetab as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Real Browser MCP has a quality signal of 68/100 (Great) with 11 views, 0 installs and 58 GitHub stars. Weavetab has 64/100 (Good) with 0 views, 0 installs and 3 GitHub stars.