Shiplight

ai.shiplightPublished by shiplight.aiv0.2.3Updated Oct 24, 2026

An MCP server that provides browser automation

VerifiedSTDIODesktop onlyBrowser Automation

Overview

AI-generated overview

Shiplight is a local MCP server that gives an AI assistant browser automation capabilities.

What you can do
Shiplight runs as a local MCP server over stdio and provides browser automation to an AI assistant. It is associated with Playwright-style locator generation: with the PWDEBUG environment variable set to "console", it can produce semantic locators such as getByRole and getByTestId for action entities; without it, only XPath locators are available. The manifest does not list individual tools.
When to use it
Consider it when you want an assistant to drive or inspect a browser on your own machine, for example to automate page interactions or generate locators for test actions. It is a desktop-only local process, so it is not suited to headless or remote-only setups.
Requirements
Runs as a local process on the user's machine via the npm package @shiplightai/mcp over stdio. Desktop only; no web executable. No authentication is declared. To get semantic locators (getByRole, getByTestId) rather than XPath only, the environment variable PWDEBUG must be set to "console".
Before you install
The server drives a browser on your machine, so it can act on pages and sessions you are logged into; review what it is allowed to do before running it. The manifest declares no authentication, so anyone who can start the process can use it. Setting PWDEBUG to "console" changes locator generation behavior.

Installation

In SourceWeft

  1. Open Shiplight in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.2.3LatestSep 29, 2026
  2. v0.2.2Sep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.