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

@bytesbrains/mcp-textbrowser

v1.1.3

Published

MCP server — text-first headless browser with DOM + OCR. Zero image tokens by default. 5-15x cheaper than screenshot-based browser MCPs.

Readme

@bytesbrains/mcp-textbrowser

npm version license CI

MCP server — text-first headless browser for Claude Code and any MCP host. DOM + OCR text maps. Zero image tokens by default. 5-15x cheaper than screenshot-based browser MCPs.

browser_navigate(url)             → DOM elements + OCR text   (~200 tokens)
browser_navigate(url, visual=true) → text + PNG               (use for layout/color only)

Why

Every screenshot-based browser MCP sends a PNG to the AI on every action. At 1280×800 that's ~1,300 image tokens per page — 5-15x more expensive than reading the same content as text.

mcp-textbrowser captures a screenshot for OCR, extracts the text, then discards the image. Only structured DOM elements and OCR text reach the model. Switch to visual=true only when you genuinely need pixels (layout checks, color, design review).

| Mode | Tokens per action | When to use | |---|---|---| | text-only (default) | ~150–400 | Everything: navigation, forms, data extraction, workflows | | visual=true | ~1,500–3,000 | Layout, colors, CSS, design review |

Install

Step 1 — install Chromium (one-time, ~130MB):

npx playwright install chromium

Step 2 — add the MCP server:

Claude Code (CLI) — one command

claude mcp add textbrowser -- npx -y @bytesbrains/mcp-textbrowser

That's it. Restart Claude Code and the tools are ready.

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (Mac) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "textbrowser": {
      "command": "npx",
      "args": ["-y", "@bytesbrains/mcp-textbrowser"]
    }
  }
}

Restart Claude Desktop.

Manual (any MCP host)

Use command: npx, args: ["-y", "@bytesbrains/mcp-textbrowser"] in your host's MCP server config.

Tools

| Tool | What it does | |---|---| | browser_navigate | Open a URL, return page context | | browser_click | Click by CSS selector / XPath / visible text | | browser_type | Fill an input field | | browser_scroll | Scroll page or element into view | | browser_screenshot | Capture current page context | | browser_read | Read current page without navigating | | browser_evaluate | Run JS in the page (safe DOM ops only) |

All tools default to text-only — pass visual: true to any tool to also receive the PNG.

Example output

Page: https://example.com/
Title: Example Domain
Viewport: 1280x800

Elements (3 interactive of 14 total):
  [1] <a> href="https://iana.org/domains/example" bbox=(133,175,254,195)
      text: "More information..."

OCR (full page screenshot):
Example Domain
This domain is for use in illustrative examples in documents.
You may use this domain in literature without prior coordination or asking for permission.

Requirements

  • Node.js 18+
  • Chromium: npx playwright install chromium (one-time, ~130MB)

License

MIT © BytesBrains


Built by Agent, for Agents 🤖


Built and maintained by BytesBrains — AI automation & agents, engineered to production standards. The model proposes, code guarantees.