npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

weblens-mcp

v0.5.1

Published

MCP server for web scraping, page rendering, and content extraction — renders any URL (including SPAs) with Playwright, extracts readable content, downloads images locally, and returns clean markdown. Built for Claude, Cursor, Copilot, and any MCP-compati

Readme

WebLens MCP

Web scraping and content extraction MCP server for AI agents. Renders any URL — including JavaScript-heavy SPAs — with headless Chromium via Playwright, extracts readable content with Mozilla Readability, captures the page's navigation links, downloads images locally, and returns a clean markdown file. Works with Claude, Claude Code, Cursor, Copilot, VS Code, Codex, and any MCP-compatible client.

npx -y weblens-mcp — runs as a local stdio MCP server. Playwright downloads its own Chromium on install, so there's nothing else to set up.

Key Features

  • Single tool — one fetch_page call does everything: render, extract, download, return
  • Bundled browser — Chromium is auto-installed by Playwright; no system Chrome required
  • Markdown output — returns a local .md file path with images embedded as local paths
  • Article extraction — uses Mozilla Readability for clean content
  • Navigation links — captures the site's menu/sidebar/header links (same-host, deduped)
  • Asset download — page images are downloaded to a local tmp directory automatically
  • Auto cleanup — downloaded files are purged after 6 hours

Requirements

  • Node.js 20 or newer

That's it. On install, Playwright downloads a matching Chromium build automatically (~90 MB, cached globally and reused across projects). No system Chrome needed.

Browser

You normally don't need to do anything — Chromium is downloaded on npm install / first npx. If the automatic download was skipped (offline, firewall, or --ignore-scripts), you have two options:

# 1. Install the bundled browser manually with the Playwright CLI
npx playwright install chromium
# 2. Or point WebLens at a Chrome/Chromium you already have
CHROMIUM_PATH="/Applications/Google Chrome.app/Contents/MacOS/Google Chrome"

If CHROMIUM_PATH is unset and the bundled browser is missing, WebLens also falls back to any Chrome/Chromium/Edge found in standard OS install locations.

Getting started

Standard config works in most MCP clients (no environment variables needed — Chromium is bundled):

{
  "mcpServers": {
    "weblens": {
      "command": "npx",
      "args": ["-y", "weblens-mcp"]
    }
  }
}

Add an "env": { "CHROMIUM_PATH": "..." } block only to use a specific browser instead of the bundled Chromium.

claude mcp add weblens -- npx -y weblens-mcp

Or add to your project's .mcp.json:

{
  "mcpServers": {
    "weblens": {
      "command": "npx",
      "args": ["-y", "weblens-mcp"]
    }
  }
}

Follow the MCP install guide, use the standard config above.

Create or edit ~/.codex/config.toml:

[mcp_servers.weblens]
command = "npx"
args = ["-y", "weblens-mcp"]

# Optional — only to override the bundled Chromium:
# [mcp_servers.weblens.env]
# CHROMIUM_PATH = "/Applications/Google Chrome.app/Contents/MacOS/Google Chrome"

Go to Cursor SettingsMCPAdd new MCP Server. Use command type with the command npx -y weblens-mcp.

code --add-mcp '{"name":"weblens","command":"npx","args":["-y","weblens-mcp"]}'

Configuration

| Environment Variable | Description | Default | |---|---|---| | CHROMIUM_PATH | Override the browser. By default WebLens uses Playwright's bundled Chromium; set this to use a specific Chrome/Chromium/Edge executable. | Bundled Chromium | | INSECURE_TLS | Set to 1 to accept self-signed certificates. | 0 (disabled) |

Browser resolution order: CHROMIUM_PATH (if set) → Playwright's bundled Chromium → a system Chrome/Chromium/Edge found in standard OS install locations (/Applications/... on macOS, C:\Program Files\... on Windows, /usr/bin/... on Linux).

Tool

fetch_page

Fetch and render a web page. Returns the absolute path to a local markdown file containing the page content with downloaded images embedded as local file paths.

Parameters:

| Parameter | Type | Required | Description | |---|---|---|---| | url | string | yes | Target page URL |

Returns: Absolute path to a .md file in the system temp directory.

Example response:

/var/folders/lp/.../T/weblens-mcp/327c3fda87ce286848a574982ddd0b7c7487f816.md

Generated markdown format:

# Page Title

Source: https://example.com/article

> Article excerpt or description

Article body text content...

## Navigation

- [Docs](https://example.com/docs)
- [Pricing](https://example.com/pricing)
- [Blog](https://example.com/blog)

## Images

![alt text](/var/folders/lp/.../T/weblens-mcp/abc123.png)
![another image](/var/folders/lp/.../T/weblens-mcp/def456.jpg)

Behavior:

  • Renders the page with Playwright (headless Chromium)
  • Blocks media and font requests for faster loading
  • Extracts article content using Mozilla Readability when possible
  • Captures navigation links from nav/header/aside/menu regions (same-host, deduped, up to 50)
  • Downloads page images (skips icons smaller than 50x50px)
  • Writes markdown with local image paths to the system temp dir (<os-tmp>/weblens-mcp/)
  • Files older than 6 hours are automatically cleaned up

Local development

npm install
npm run build
node dist/index.js

How it works

URL
 └→ Playwright renders page (headless Chromium)
     └→ Extract title, text, HTML, images, navigation links from DOM
         └→ Mozilla Readability extracts clean article content
             └→ Download images to <os-tmp>/weblens-mcp/
                 └→ Compose markdown with local image paths
                     └→ Write .md file, return path

Tmp directory

Downloaded assets and markdown files are stored in your system temp directory under weblens-mcp/ (e.g. /tmp/weblens-mcp/ on Linux, /var/folders/.../T/weblens-mcp/ on macOS). Cleanup runs automatically:

  • On every fetch_page call (throttled to every 5 minutes)
  • Files older than 6 hours (by mtime) are deleted
  • No external cron or scheduler needed

Docker

{
  "mcpServers": {
    "weblens": {
      "command": "docker",
      "args": [
        "run", "-i", "--rm", "--init",
        "-v", "/tmp/weblens-mcp:/tmp/weblens-mcp",
        "weblens-mcp"
      ]
    }
  }
}

License

ISC