Skip to main content
Glama
sylin-org

Ghostlight

by sylin-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Related Servers

Alternatives to Ghostlight

No user-submitted related servers found.

    Related Servers

    • BRYG

      flexiblepackage
      F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that lets AI assistants drive real Chromium browsers — navigate, click, type, read pages, run OCR, and record network traffic. 43 tools, credentials stay local, zero telemetry.
      -

    • OpenBrowser

      dylansantwani
      A
      license
      Not graded
      quality
      A
      maintenance
      A zero-dependency MCP server that drives a real Chrome browser through a companion extension, enabling AI agents to automate real user sessions with trusted input events, compact accessibility-tree snapshots, and 14 tools for navigation, interaction, scripting, and inspection.
      207 npm
      MIT

    • Scout

      Lautrek
      A
      license
      B
      quality
      C
      maintenance
      Browser MCP server that connects to your existing browser, preserving sessions, passwords, and extensions, enabling AI agents to interact with web pages without bot detection.
      31
      4 npm
      1
      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

    A3.6/5.0

    Scored across 25 tools

    Disambiguation3/5

    Multiple tools have overlapping purposes (script vs browser_batch, file_upload vs upload_image, form_input vs form_fill), but descriptions include enough detail to distinguish them with careful reading. An agent may still hesitate on which to choose.

    Naming Consistency1/5

    Tool names follow no consistent pattern: some are verb_noun (read_page, upload_image), some are noun_verb (file_upload, form_fill), some are single verbs (navigate, find), and some nouns (computer, dialog). The _mcp suffix appears on only two tab-related tools, while tab_control omits it. This mix makes the naming chaotic.

    Tool Count3/5

    At 25 tools, the server is on the heavy side of the 16-25 borderline range. However, the broad scope of full browser automation justifies most tools, and each serves a distinct purpose within that domain.

    Completeness5/5

    The tool set comprehensively covers the browser automation lifecycle: navigation, reading, interaction, form filling, waiting, tab management, JavaScript execution, network/console inspection, screenshots, dialogs, and even recording. There are no obvious dead ends; the presence of update_plan and explain covers agent coordination and discoverability.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources