Log inSubmit server
Ghostlight logo

Ghostlight

Drive a logged-in Chromium browser through MCP with visible tabs, governed actions, forms, uploads, and diagnostics.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Ghostlight

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "ghostlight": {
      "command": "npx",
      "args": [
        "-y",
        "ghostlight"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 23 tools correctly (Today).

Overview

The ghostlight MCP server lets agents operate a real, logged-in Chrome, Edge, Brave, or Chromium browser through a local service and browser extension. It exposes 24 catalog tools for reading pages, managing tabs, navigating, clicking, entering form data, uploading files, handling dialogs, running scripts, waiting for page state, and diagnosing failures. Use it when an agent needs an existing browser session, visible work that a person can pause or take over, or browser workflows that span tabs and popups. Optional policies can restrict capabilities and domains, while the default setup runs locally without a hosted control plane.

Use cases

  • Read pages in an existing signed-in browser session
  • Complete forms and upload files across a multi-step workflow
  • Investigate failed web tasks using page, console, and network evidence
  • Pause an agent and take over for sensitive browser steps
  • Apply domain and capability restrictions to browser automation

Key features

  • 24 catalog tools for browser work and policy inspection
  • Visible tab-group workspace in an existing Chromium browser
  • Form input, uploads, dialogs, scripts, waits, and short flows
  • Local browser connection with no hosted control plane
  • Optional capability and domain governance
  • Structured action results with recovery guidance

Tools23

What Ghostlight lets your agent do. Expand a tool for its parameters.

Verified live~6.9k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

7/7 checks healthy over the last 44d

What it can do

From the 23 tools this server returned when we ran it; 23 declare their own safety hints.

Runs commands · 1Can delete or modify data · 13Handles credentials · 2Makes network requests · 21Read-only tools · 10
Network at startup5 connections
Files written at startup17
Install scriptsNone
npm provenanceNot published
Package age105 days
Maintainers1

Observed 2026-10-22 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 6d ago via OSV.dev · ghostlight (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads1.5kPackage downloads in the last 30 days.
Last commit1d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed23Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Ghostlight works

What ghostlight does

The ghostlight MCP server gives an MCP client access to a tab group in an existing Chromium-based browser. It works with Chrome, Edge, Brave, or Chromium 125 and newer, using the browser profile selected by the user. This lets an agent use sessions and sign-ins already present in that browser instead of opening a separate empty browser.

The agent can read pages, navigate, inspect browser state, interact with semantic elements, complete forms, upload files, follow supported child tabs, resolve dialogs, wait for page changes, and investigate failed workflows. The work remains visible in the selected browser window. A desktop tray workbench shows activity and lets the user pause the workspace, take control for a delicate step, or stop it.

The ghostlight MCP server keeps ordinary browser tabs outside the agent-owned set and follows the workspace if its tabs are moved. It also reports what happened, what changed, whether the result is uncertain, and whether repeating the operation is considered safe. Its local record contains identifiers, decisions, and minimized measurements rather than page content, field values, screenshots, selectors, or dialog text.

How it works

An MCP client sends an intended browser operation to the local Ghostlight service. The service communicates with the browser through the installed extension over local IPC, performs the browser steps, and returns a structured result. The published release describes 23 browser tools and one policy tool covering tabs, navigation, page reads, screenshots, clicks, hovers, form input, uploads, scripts, waits, short flows, dialogs, diagnostics, and workspace switching.

Browser credentials remain in the chosen browser profile. Credential entry requires explicit acknowledgement for the request, and that acknowledgement cannot bypass policy or the user’s Pause or Stop controls. With no policy configured, HTTP and HTTPS browsing is allowed, including localhost, loopback, and link-local destinations; non-HTTP schemes and stale handles remain restricted.

Setup and configuration

Install the local service and register MCP clients discovered by the installer with:

Terminal
npx -y ghostlight install

Then install the Ghostlight in Browser extension from the Chrome Web Store and restart an MCP client if it does not reload tools automatically. A first read-only task against https://example.com/ can verify the connection without clicking, typing, submitting, or changing the page.

Run npx -y ghostlight doctor when setup needs diagnosis. It checks the MCP client entry, local service, browser connection, and extension, then identifies the next action. The ghostlight MCP server can also use optional policy layers to grant or restrict read, action, write, and execute capabilities by MCP identity and domain. Policies may add sacred domains, dry-run preflight, and structured audit information.

Tools and capabilities

The ghostlight MCP server supports these capability areas:

  • Managing workspaces, owned tabs, navigation, and supported child tabs
  • Reading pages, taking screenshots, and referencing page elements
  • Clicking, hovering, typing, filling forms, uploading files, and handling dialogs
  • Running scripts, waiting for page state, and executing short browser flows
  • Collecting page state, console messages, and network requests for diagnostics
  • Explaining the authority currently applied through a policy tool

Limitations and notes

The service operates on the local machine and does not require an account, telemetry, activation service, hosted control plane, or hidden second browser. Network traffic is limited to browsing requested by the agent. Local and managed policy layers can remove authority but cannot add it.

Closing a tab requires both orchestrator authority and the browser’s preserve-tabs setting; that setting is enabled by default. The user can always close a tab manually. Browser messages and animations are passive, while interactive runtime control is handled in the workbench. Non-HTTP URLs and stale element handles are restricted, and uncertain effects are reported instead of being presented as successful.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Ghostlight

ghostlight is an MCP server that connects MCP clients to a real logged-in Chrome, Edge, Brave, or Chromium browser through a local service and extension. Its main tools read pages, manage tabs, navigate, click, fill forms, upload files, handle dialogs, run scripts, wait for page state, and diagnose browser workflows.

Run `npx -y ghostlight install`, install the Ghostlight in Browser extension, and restart the MCP client if it does not reload tools. The installer registers MCP clients it finds. Use `npx -y ghostlight doctor` to check the client entry, local service, browser connection, and extension.

Yes, ghostlight works with Cursor. The README also names Codex, Claude Code, Claude Desktop, VS Code, Windsurf, Zed, OpenCode, and Crush as compatible clients, along with other compatible stdio MCP clients.

Yes, ghostlight uses the browser profile you choose, including sessions already signed in there. Credentials stay with the browser. Credential input requires explicit per-request acknowledgement and remains subject to configured policy and the user’s Pause or Stop controls.

Configure optional local or managed policies that grant `read`, `action`, `write`, and `execute` capabilities by MCP identity and domain. Policies can also define sacred domains, dry-run preflight, and structured audit information, and they can only reduce available authority.

Related MCP servers

All in Browser Automation All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewGhostlight AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/ghostlight?style=directory)](https://allmcps.com/mcp/ghostlight)
HTML Embed
<a href="https://allmcps.com/mcp/ghostlight"><img src="https://allmcps.com/api/badge/ghostlight?style=directory" alt="Ghostlight on AllMCPs" /></a>