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

@web-axag/bridge

v1.1.1

Published

Expose a browser tab's AXAG tools to MCP clients through a local relay

Readme

@web-axag/bridge

Gives an MCP client — Claude Desktop, Claude Code, anything that speaks MCP — access to the tools a browser tab has registered.

npx axag-bridge
[axag-bridge] listening on ws://127.0.0.1:53422
[axag-bridge] pairing code: 7f3a91c2

In the page:

import { installShim } from '@web-axag/shim';
import { connectBridge } from '@web-axag/bridge/client';

installShim();
connectBridge({ url: 'ws://127.0.0.1:53422', pairingCode: '7f3a91c2' });

The agent now lists and calls the tools that tab is offering, and the list changes as the person navigates.

Why a relay

A browser tab can't be an MCP server that a desktop agent dials into: it has no address, and it isn't running when the agent starts. So the tab connects out to a small local process, which is the MCP server the agent connects to.

browser tab  ──websocket──▶  axag-bridge  ──MCP (stdio)──▶  agent

Calls run in the tab, in the session the person is already signed into. No credentials pass through the relay, and the page's own safety enforcers wrap every call, so a bridged agent meets the same confirmation and tenant checks as one running in the browser.

What keeps it closed

  • Loopback only. The relay binds 127.0.0.1.
  • A pairing code, printed in the terminal and copied into the page. A tab that doesn't send it is refused.
  • An origin allowlist with --origin https://app.example.com, repeatable. Without it any origin may pair — fine while developing locally, not otherwise.
  • One tab at a time. A second connection is refused rather than silently taking over.
  • Calls expire. A tab that never answers fails the call rather than hanging the agent.

CLI

| Flag | Description | |------|-------------| | --port <n> | Port for the tab to connect to. Default: a free port | | --origin <url> | Origin allowed to pair; repeatable | | --pairing <code> | Fixed pairing code instead of a fresh one |

Configure it like any other MCP server:

{
  "mcpServers": {
    "axag-bridge": { "command": "npx", "args": ["axag-bridge", "--origin", "https://app.example.com"] }
  }
}

Embedding the relay

import { startBridgeServer } from '@web-axag/bridge';

const { mcp, relay, pairingCode, port, close } = await startBridgeServer({ allowedOrigins: ['https://app.example.com'] });
await mcp.connect(myTransport);

relay.listTools() and relay.status() are what an inspector renders.