Skip to main content
Glama
lldartsll

browser-for-claude

by lldartsll
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to browser-for-claude

No user-submitted related servers found.

    Related Servers

    • claude-playwright

      smartlabsAT
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables browser automation and web interaction control through Playwright, allowing Claude Code to navigate, click, fill forms, take screenshots, and manage sessions.
      85 npm
      7
      MIT

    • mcp-playwright-automation

      pedro95nunes
      F
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to control a real Chromium browser through Playwright, allowing them to navigate pages, click elements, fill forms, extract text or HTML, and capture screenshots in a persistent session.
      6
      -

    • mcp-playwright-server

      Jens0110
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude Code to control a browser via Playwright for web scraping, automation, and research, with features like navigation, screenshots, form filling, and PDF export.
      6 npm
      MIT

    • Browser AI MCP Server

      qckfx
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables natural language browser automation through Claude, wrapping Playwright to execute commands like navigation, clicking, form filling, and screenshots.
      7 npm
      30
      MIT

    • Claude Chrome MCP

      nonsleepr
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables browser automation through the Claude Chrome Extension, allowing agents to navigate websites, fill forms, take screenshots, and debug web apps via standard MCP protocols.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: navigating, clicking, typing, reading text, evaluating JS, taking screenshots, getting the URL, and closing the browser. There is no ambiguity or overlap.

    Naming Consistency5/5

    All tools share the 'browser_' prefix and follow a consistent verb-based pattern (navigate, click, type, get_text, evaluate, get_url, close). 'browser_screenshot' is the only deviation but still reads as an action.

    Tool Count5/5

    With 8 tools, the set is appropriately scoped for browser automation, covering session management, navigation, interaction, inspection, and evaluation. Each tool earns its place.

    Completeness4/5

    The set covers core browser workflows, but lacks explicit back/forward/refresh or wait commands. However, browser_evaluate can compensate for these missing operations, making gaps minor.

    Resources