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

workatomcp-bridge

v1.5.0

Published

WorkatoMCP native messaging host (Chrome ↔ MCP bridge)

Readme

workatomcp-bridge

The local bridge half of WorkatoMCP, published to npm as workatomcp-bridge.

A Fastify server on 127.0.0.1:12306 that terminates MCP transports and forwards tool calls to the Chrome extension over native messaging. Chrome launches it on demand — there is nothing to start by hand.

Install

npm install -g workatomcp-bridge

Postinstall attempts user-level native-messaging registration for detected browsers.

CLI

workatomcp-bridge doctor              # diagnose registration, ports, permissions
workatomcp-bridge doctor --fix        # repair what it can
workatomcp-bridge register --detect   # (re)register for detected browsers
workatomcp-bridge register --system   # system-level install (needs admin/sudo)
workatomcp-bridge fix-permissions     # repair wrapper-script permissions
workatomcp-bridge update-port 12307   # move off a conflicting port
workatomcp-bridge report --copy       # redacted diagnostic report for bug reports

Endpoints

| Route | Purpose | | ----------------------------- | ----------------------------------------- | | POST/GET/DELETE /mcp | Streamable HTTP transport | | GET /sse + POST /messages | Legacy SSE transport | | GET /ws-client | Per-Chrome-profile WebSocket registration | | GET /ping | Liveness check |

workatomcp-stdio is also installed, for MCP clients that require a spawned stdio process.

Development

pnpm --filter workatomcp-bridge build
pnpm --filter workatomcp-bridge test
pnpm --filter workatomcp-bridge dev     # rebuild + re-register on change

Layout

src/
├── server/
│   ├── index.ts             # Fastify routes and MCP transports
│   └── profile-registry.ts  # per-profile WebSocket connections
├── native-messaging-host.ts # stdio framing to/from Chrome
├── file-handler.ts          # local file read/write for the recipe & CSV round-trips
├── mcp/                     # MCP server and stdio entrypoint
├── cli.ts                   # doctor / register / report commands
└── scripts/                 # build, postinstall, registration

src/scripts/run_host.sh must ship with LF line endings or the host fails to execute on macOS and Linux; .gitattributes enforces this.

Architecture details: docs/ARCHITECTURE.md.