Skip to main content
Glama
mkseo1012-pixel

BrowserLemon

by mkseo1012-pixel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to BrowserLemon

No user-submitted related servers found.

    Related Servers

    • huashu-chrome

      alchaincyf
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables any MCP-compatible AI agent to drive your own Chrome browser with your existing login state, filling forms, clicking elements, fetching data, and handling captchas without API keys or re-authentication.
      402 npm
      545
      MIT

    • byob

      hannah5031
      A
      license
      Not graded
      quality
      A
      maintenance
      Lets AI coding tools directly control the user's already-open, logged-in Chrome to read pages, navigate, click, type, screenshot, inspect network/storage, and automate browser tasks through local MCP tools.
      1 npm
      ISC

    • Tabryn

      idugeni
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI agents to your Chrome browser via MCP, enabling real-time control of existing tabs, sessions, and application state for development workflows.
      MIT

    • better-browser-mcp

      alexsorokoletov
      A
      license
      Not graded
      quality
      B
      maintenance
      Gives any MCP-compatible AI agent control of the user's own Chrome profile with existing sign-ins, returning compact text snapshots and batched action results so browsing tasks finish in far fewer calls and tokens. Includes safety guards against unwanted purchases or posts, prompt-injection flagging, and isolated agent tab groups that never steal the user's focus.
      4 npm
      MIT
    Deploy Server
    Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

    TDQS

    B3.4/5.0

    Scored across 8 tools

    Disambiguation4/5

    Each tool has a generally distinct purpose: status, tab listing, page reading, navigation, typing, clicking, and social composing/publishing. There is mild overlap between type_text and draft_social_post, and click could theoretically be used in place of publish_social_post, but the descriptions clarify the intended specialized use.

    Naming Consistency3/5

    Most tools follow a verb_noun snake_case pattern (list_tabs, read_page, open_url, type_text, draft_social_post, publish_social_post), but browser_status is a noun phrase and click is a bare verb. The naming is readable and consistently lowercase, but the pattern is not uniform.

    Tool Count5/5

    Eight tools is well-scoped for a browser automation assistant. Each tool has a clear role with no obvious filler or redundant duplicates, making the count appropriate for the server's purpose.

    Completeness3/5

    The set covers core browsing actions like open, read, type, click, plus a guarded social-posting workflow. However, it lacks standard browser controls such as switching or closing tabs, scrolling, refreshing, and waiting for page conditions, which are notable gaps for browser automation.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources