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

@drbenedictporkins/tethernet-mcp

v1.3.1

Published

Tethernet MCP server — connects Claude Code and Claude Desktop to your live Firefox session. Claude sees your screen, reads page state, and guides you step by step through complex web workflows (App Store Connect, AWS, Stripe, DNS, etc.) in your real logg

Readme

Tethernet MCP Server

Claude browser co-pilot — guides you step by step through complex web workflows in your real logged-in Firefox session.

This is the MCP server component (1 of 2). It connects Claude Code or Claude Desktop to your Firefox browser via the Model Context Protocol (stdio transport).

The Firefox extension is also required. Install it from:

Quick Start

Claude Code

claude mcp add tethernet --scope user -- npx -y @drbenedictporkins/tethernet-mcp

Claude Desktop

Edit your config file and add to mcpServers:

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

Restart Claude Desktop after editing.

After installing

Install the Firefox extension, open the Tethernet popup, and enter the port shown by get_connection_info.

Development

npm run dev     # Hot reload (tsx watch)
npm run build   # Compile TypeScript
npm test        # Run tests (vitest)

MCP Tools

Connection

  • get_started — Returns behavioral instructions (call first in Claude Desktop sessions)
  • get_connection_info — WebSocket URL/port to enter in extension popup
  • get_connection_status — Extension connected status, tab count, port

Tab Management

  • list_tabs — List all open tabs
  • get_active_tab — Get current active tab
  • get_primary_tab — Get default tab for operations
  • set_primary_tab — Set default tab (avoids specifying tabId on every call)
  • switch_tab — Switch to a tab
  • create_tab — Open new tab
  • close_tab — Close a tab
  • list_frames — List iframes in a page

Navigation

  • navigate — Navigate to URL
  • reload_page — Reload page
  • go_back / go_forward — Browser history navigation
  • wait_for_navigation — Wait for navigation to complete
  • wait_for_element — Wait for element to appear in DOM

DOM Inspection

  • dom_stats — Page size, element count, depth — check this first before fetching HTML
  • get_dom_structure — Progressive DOM exploration at controlled depth (preferred over full HTML)
  • get_page_content — Full page HTML (only for pages < 50KB)
  • query_selector — Find elements by CSS selector
  • get_element_properties — Get properties of a specific element
  • get_dom_snapshot — Retrieve stored DOM snapshots

Script Execution

  • execute_script — Run JavaScript in page context (full DOM access)

Interaction

  • click_element — Click a DOM element
  • type_text — Type into an input
  • fill_form — Fill multiple form fields at once
  • scroll_to — Scroll to position or element

Buffered Data

  • query_buffer — Query console/network/errors/websocket data with JS transforms
  • get_network_request_detail — Full headers and body for a specific request
  • clear_buffer — Clear buffered data for a tab
  • get_buffer_stats — Buffer usage statistics

Screenshots

  • take_screenshot — Capture page (saves to /tmp, returns path — use Read to view in CC; or returnBase64: true for inline JPEG in Claude Desktop)
  • get_screenshots — Retrieve buffered screenshots

Storage & Cookies

  • get_local_storage / set_local_storage — localStorage
  • get_session_storage — sessionStorage
  • get_cookies / set_cookie — Cookies

Request Control

  • set_request_headers — Set custom headers for a tab
  • block_urls — Block URL patterns from loading

Ollama Integration

  • ollama_analyze_page — Send page HTML to local Ollama for analysis

Extension Debugging

  • check_debug_bridge — Check if a Firefox extension implements the Tethernet debug bridge
  • query_extension_debug — Query extension state via debug bridge (ping, getState, getErrors, getStorage, getManifest)

Buffer Schemas

// query_buffer types and their fields:
console:   { level, args, timestamp, url }
errors:    { message, source, lineno, colno, stack, timestamp }
network:   { requestId, url, method, statusCode, duration, timestamp,
             requestHeaders, responseHeaders, requestBody, responseBody }
websocket: { url, data, direction, timestamp }

Buffer limits (per tab): 1000 console, 500 network, 500 websocket, 200 errors, 10 snapshots, 5 screenshots.

Architecture

Claude Code/Desktop  ──stdio──►  MCP Server (Node.js)  ──WebSocket──►  Firefox Extension
                                 (dynamic port, OS-assigned)

Each session spawns its own server process with its own WebSocket port — explicit 1:1 binding.

Extension Protocol

Events (extension → server):

{ type: 'console_log' | 'network_request' | 'js_error' | ..., tabId: number, data: any }

Commands (server → extension):

{ action: string, params: Record<string, any>, requestId: string }

Responses (extension → server):

{ requestId: string, result?: any, error?: string }

Configuration

src/utils/config.ts — buffer limits, WebSocket settings, logging.

Session logs: server/logs/session-<timestamp>.jsonl

Ollama Setup

Set environment variables in your MCP config:

OLLAMA_BASE_URL=http://localhost:11434
OLLAMA_DEFAULT_MODEL=qwen2.5:7b