Shiplight MCP server

Read from the package source without running it. The installed server may list more.

• attach_to_browser

  Connect to a browser for testing. Two modes: 1. Direct CDP: pass cdp_url (e.g. from a debugger's /api/browser-cdp endpoint) to connect directly via Chrome DevTools Protocol. 2. Extension relay: omit cdp_url to auto-discover Chrome tabs via the Shiplight AI Chrome extension. Returns session_id for use with inspect_page, act, get_page_info, switch_tab, etc.

• clear_execution_history

  Clear the execution history for a session. The execution history tracks past browser operations within a session. Clear it to start fresh or reduce memory usage.

• clear_logs

  Clear console and network logs for a session

• close_all

  Close all browser sessions

• close_session

  Close a browser session. Omit session_id entirely to close ALL open sessions.

• generate_html_report

  Generate a self-contained HTML session report. Can be called while the session is live OR after close_session. Embeds per-step screenshots, an optional video player, and a Playwright trace viewer link. The session must have been started with record_evidence: true. Pass local_video_path (returned by close_session) to embed the video. Pass local_trace_path (returned by close_session) to include trac

• get_browser_console_logs

  Get console logs from the browser (errors, warnings, etc.)

• get_browser_network_logs

  Get network request logs from the browser

• get_local_artifact

  Get a local artifact file (screenshot, DOM snapshot, etc.) from a live browser session. Only accepts local file paths, NOT S3 URIs. For test run artifacts, use get_step_artifacts instead.

• get_locators

  Extract Playwright locators for one or more elements by index. Call inspect_page first. Returns locator, xpath, frame path, tag name, and text for each element. Use this to collect locator data for building test flows without interacting with the page. Pass multiple indices in a single call to save round-trips.

• get_page_info

  Get basic page information (URL and title) without taking a screenshot. Use this as a lightweight way to check what page you're on. For visual inspection, use inspect_page.

• get_relay_status

  Get extension relay server status and tab mapping

• get_session_state

  Get current state of a session (URL, session type)

• inspect_page

  Inspect the current page: extracts the DOM tree and saves a Set-of-Mark screenshot. Returns the DOM file path (with element indices [0], [1], etc. for the act tool) and a screenshot file path. The DOM and screenshot are captured atomically so element indices always match. IMPORTANT: Read the DOM file to understand page state and decide actions. Only view the screenshot file when the DOM is insuffi

• new_sessionwrite action

  Create a new browser session with optional device emulation. Returns a session_id for subsequent operations. Use storage_state_path to restore a previously saved session (cookies, localStorage, IndexedDB). SCREEN RECORDING: Set browser_options.record_evidence=true only when you believe implementation is complete and are doing a final verification pass \u2014 not for exploration, investigation, or

• save_storage_state

  Save the browser session's storage state (cookies, localStorage, IndexedDB) to a file. Use this after logging in to cache the session for fast restores via new_session's storage_state_path.

• update_variableswrite action

  Update session variables for use in subsequent browser operations. Variables are key-value pairs that can be referenced in browser tasks. Mark sensitive values (passwords, tokens) with sensitive_keys to prevent logging. Example: variables: { username: "john", password: "secret123" } sensitive_keys: ["password"]

• Code scan6 source files scanned20/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 17 days ago15/15
• Maintainer identitynamespace and repository owner differ; GitHub account older than a year; website matches verified namespace8/10

Safety score

85/100

higher than 65% of 867 Scraping and browsing servers

Tools

17

the typical Scraping and browsing server has 6

Tools that change things

12%

typical: 0%. Fewer write tools means less an agent can break

Downloads a week

1,078

more than 92% of 312 Scraping and browsing servers with a package

Grade history

• 2026-10-16restoreC → Ascore 85: eval / new Function used

Shiplight: common questions

Is Shiplight MCP server safe?

Yes, by our scan: it is graded A (85/100). Read the Shiplight safety report

How do I install Shiplight?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Shiplight need an API key?

No secret keys are declared. It reads 1 setting from the environment.

Is Shiplight maintained?

The last commit was 37 days ago (2026-09-29). The latest release is v0.2.3.

What can I use instead of Shiplight?

Servers from other publishers that do the same job: GrowBlocks Dev Kit MCP server, SeleniumBase MCP server and Next AI Draw.io MCP server.

How does Shiplight compare with other Scraping and browsing MCP servers?

safety score 85/100 (higher than 65% of 867 Scraping and browsing servers); tools 17 (the typical Scraping and browsing server has 6); tools that change things 12% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.