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

navagent-mcp

v0.1.3

Published

Ultra-light MCP browser navigation. Token-efficient & anti-bot. Works on any site (SPAs, shadow DOM, iframes).

Readme

navagent-mcp

Ultra-light MCP browser navigation. Token-efficient & anti-bot. Works on any site (SPAs, shadow DOM, iframes).

The AI sees a compact numbered list instead of screenshots or verbose accessibility trees:

AI sees:                   AI does:
────────────               ─────────────
📍 amazon.com              browse_click(6)
1. My Account [link]
2. Cart (0) [link]
3. Search [input]
4. Computers [link]
5. Electronics [link]
6. Books [link]

Quick Start

1. Install the Chrome extension

Chrome Web Store (recommended): Install NavAgent

Or sideload:

  1. Download/clone the repo
  2. Open chrome://extensions/
  3. Enable Developer mode
  4. Click Load unpacked → select the chrome-extension/ folder

2. Configure the MCP server

Claude Desktop

Edit claude_desktop_config.json:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "navagent": {
      "command": "npx",
      "args": ["-y", "navagent-mcp"]
    }
  }
}

Claude Code

Add to .mcp.json (project or global ~/.claude.json):

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

Cursor

Edit ~/.cursor/mcp.json:

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

OpenClaw

Add to openclaw.jsonmcp.servers:

{
  "mcp": {
    "servers": {
      "navagent": {
        "command": "npx",
        "args": ["-y", "navagent-mcp"],
        "transport": "stdio"
      }
    }
  }
}

Available tools (12)

| Tool | Description | |------|-------------| | browse_scan | Scan the page → zones or flat list of clickable elements | | browse_zone | Drill into a zone to see its elements | | browse_click | Click an element by number + auto-rescan | | browse_type | Type into an [input] field + Enter | | browse_more | Pagination (next batch of elements/zones) | | browse_scroll | Physical scroll for lazy-loading / infinite scroll | | browse_read | Visible page text (max 2000 chars) | | browse_extract | Full page content as structured markdown with pagination | | browse_goto | Navigate to a URL + scan | | browse_back | Go back to previous page + rescan | | browse_list_tools | List WebMCP tools declared by the page (navigator.modelContext) | | browse_call_tool | Invoke a WebMCP tool — the AI calls site APIs directly |

Configuration

WebSocket port

By default, the WebSocket bridge uses port 61822. To change it:

  1. Set an environment variable in the MCP config:
{
  "mcpServers": {
    "navagent": {
      "command": "npx",
      "args": ["-y", "navagent-mcp"],
      "env": { "NAVAGENT_PORT": "61900" }
    }
  }
}
  1. Set the same port in the Chrome extension options.

Architecture

MCP Client (Claude, Cursor, etc.)
    ↓ stdio (Model Context Protocol)
navagent-mcp (this package)
    ↓ WebSocket localhost:61822
Chrome Extension NavAgent
    ↓ chrome.tabs.sendMessage
Content Script (DOM scanner)

The Chrome extension uses the user's own cookies and sessions — no cloud proxy, no anti-bot detection.

Author

Dimitri Bouriez — [email protected]

License

MIT