Skip to main content
Glama
Intrect-io

lyra-browser

Official
by Intrect-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to lyra-browser

No user-submitted related servers found.

    Related Servers

    • Bosun

      The-Glassy
      A
      license
      Not graded
      quality
      A
      maintenance
      A self-hosted MCP browser service that lets AI agents drive a real headful Chromium, patchright, or camoufox session — navigating, reading accessibility snapshots, clicking, typing, and taking screenshots — with scheduled keepalive visits and Google Meet notetaking. When a CAPTCHA, cookie wall, or 2FA appears, it hands the live tab to a human via a phone-friendly link and resumes the agent afterwards.
      Apache 2.0

    • Remote Browser

      syntropika
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to drive a live, persistent self-hosted Chromium session over MCP, running browser actions via Playwright/CDP, capturing page snapshots, screenshots and videos, and managing uploads and downloads in the same tabs and signed-in accounts a human user can take over at any time.
      3 npm
      Apache 2.0

    • duplex

      Eric-huang799
      A
      license
      B
      quality
      A
      maintenance
      A desktop browser shared by a human and an AI — same tabs, same live session. It bundles a stdio MCP server with 24 tools (page snapshot, click, type, screenshot, tabs, annotations, evaluate) so any MCP client can drive the browser the human is watching.
      24
      25,198 npm
      6
      MIT

    • Pagewright (browser-mcp)

      zamansheikh
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to see and control the user's real Chrome/Brave/Edge profile over MCP, so they can read pages, click, type, take screenshots, audit layouts, debug CSS, and scrape paginated or infinite-scroll data. Because it drives the normal browser via the DevTools protocol with real input events, it works on modern JavaScript apps and on sites where the user is logged in.
      8 npm
      1
      MIT

    • Orvima

      Sachitt-AV-08
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables any MCP-capable AI client to drive the user's own Chrome or Edge browser through a set of browse_* tools — navigating, clicking, typing, extracting, and managing tabs with their existing logins on their own machine. Runs locally and self-hosted with a live viewport and pause/approve controls so every verified step stays under user watch.
      4
      MIT

    • guarded-browser-mcp

      mickadoua
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to drive a self-hosted Chromium through MCP tools for opening pages, reading content, taking screenshots, clicking, filling forms, and triggering final submissions, while a human watches the same browser live and can take over for logins or captchas. Server-side guardrails enforce per-session domain allowlists and denylists, refuse password, payment card, IBAN and one-time-code fields, isolate each token in its own browser context, and route submits, payments and orders through a separate final-action tool that can require human approval.
      MIT
    Deploy Server
    Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

    TDQS

    B3.4/5.0

    Scored across 29 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes within a browser-automation domain. Some potential for confusion exists between read_page (text/tree reading) and read_form (form field listing), or between navigate/go_back/reload_page. However, the detailed descriptions strongly clarify when to use each, keeping overlap manageable.

    Naming Consistency3/5

    Mix of verb_noun (open_browser, close_browser, read_page, read_form, read_image) and verb-only (click, type_text, navigate, scroll, hover) patterns. The conventions are still readable and the verbs are clear, but there is no single predictable pattern across all 29 tools.

    Tool Count2/5

    29 tools is at the high end for a browser automation server, especially since many are fine-grained actions (click, type_text, press_key, hover, scroll) that could be combined into a more general 'interact' tool. The count feels heavy for the domain, though each tool does have a specific role.

    Completeness4/5

    Covers a wide range of browser automation needs: navigation, reading, interaction, downloads, forms, tabs, dialogs, and session control. A few gaps remain (e.g., no explicit tool for executing JavaScript or managing cookies/local storage, no direct window resizing), but these are minor for most agent workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources