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

@soulsniper-v2/browser-sdk-mcp

v0.1.1

Published

MCP server for Browser SDK provider-neutral browser tools.

Readme

@soulsniper-v2/browser-sdk-mcp

npm version

MCP server for Browser SDK. It gives Codex, Claude Code, Cursor, and other MCP clients a small browser tool surface backed by the same provider runway as the TypeScript client.

npm install @soulsniper-v2/browser-sdk-mcp
npx -y @soulsniper-v2/browser-sdk-mcp
{
  "mcpServers": {
    "browser-sdk": {
      "command": "npx",
      "args": ["-y", "@soulsniper-v2/browser-sdk-mcp"],
      "env": {
        "BROWSERBASE_API_KEY": "bb_...",
        "CLOUDFLARE_API_TOKEN": "...",
        "CLOUDFLARE_ACCOUNT_ID": "...",
        "BROWSERLESS_API_KEY": "...",
        "STEEL_API_KEY": "...",
        "ANCHOR_API_KEY": "...",
        "HYPERBROWSER_API_KEY": "...",
        "BROWSER_USE_API_KEY": "...",
        "BROWSER_SDK_EXTENDED_PROVIDERS": "true"
      }
    }
  }
}

Read tools are browser_markdown, browser_extract, browser_links, browser_route, browser_snapshot, and browser_crawl when a crawl-capable provider is configured.

For agents that need to operate a browser, the server also provides a stateful runtime:

browser_session_start
browser_session_navigate
browser_session_snapshot
browser_session_action
browser_session_read / browser_session_screenshot
browser_session_close

Snapshots return short-lived e1, e2, and similar refs. Re-snapshot after navigation or an action. Session actions are explicit side effects and are never retried, replayed, or failed over. The MCP process keeps provider CDP URLs and credentials private and returns only an opaque runtime id.

Optional safety controls:

BROWSER_SDK_ALLOWED_DOMAINS=example.com,docs.example.com
BROWSER_SDK_MAX_SESSIONS=4
CHROMIUM_EXECUTABLE_PATH=/path/to/chromium

The default MCP route is Browserbase → Cloudflare Browser Run → Browserless → Steel → local. BROWSER_SDK_EXTENDED_PROVIDERS=true adds Anchor Browser → Hyperbrowser → Browser Use Cloud before local.

For application-owned browser work, use withSession() directly where authorization and cleanup are visible in application code.

Provider credentials are read from the environment and are never returned in tool output.