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

statelode-bridge

v0.1.6

Published

stdio to Streamable HTTP MCP bridge for StateLode

Readme

statelode-bridge

npm version npm downloads license MCP Registry

statelode-bridge lets stdio-first MCP clients talk to StateLode's hosted Streamable HTTP MCP endpoint.

npx statelode-bridge --token statelode_live_...

Prefer environment variables in checked-in IDE config:

STATELODE_TOKEN=statelode_live_... npx statelode-bridge

The bridge forwards newline-delimited JSON-RPC from stdio to POST /mcp, keeps the Mcp-Session-Id header in sync, and relays GET /mcp server-sent events back to stdio as JSON-RPC notifications.

Teaching agents to use StateLode

Different IDEs auto-load different instruction files, so the bridge writes the StateLode rules where each agent will actually see them. There are two commands.

setup — once per machine

npx statelode-bridge setup        # add --dry-run to preview

Installs a global StateLode protocol into each installed IDE's global instruction file — ~/.claude/CLAUDE.md (Claude Code), ~/.codex/AGENTS.md (Codex), ~/.codeium/windsurf/memories/global_rules.md (Windsurf) — and prints a block to paste into the IDEs that keep global rules in app settings (Cursor → User Rules; VS Code → Copilot instructions). It only touches IDEs that are installed, and upserts a delimited block so it never clobbers your existing rules.

After setup, any agent:

  • uses a repo's StateLode project when the repo has a statelode.json, and
  • offers to set one up (with your permission) when it doesn't — so you don't have to initialize every project up front.

init — pin one repo to a project

npx statelode-bridge init <project-slug>   # defaults to the directory name

Writes statelode.json (the marker that maps this repo to a StateLode project) and a ## StateLode block into every IDE's repo guide file so the project is in context even without the global setup:

| File | IDE | | --- | --- | | AGENTS.md | Codex, Cursor | | CLAUDE.md | Claude Code | | .github/copilot-instructions.md | VS Code (Copilot) | | .cursor/rules/statelode.mdc | Cursor (project rule, alwaysApply) |

Re-running is the refresh path: npx statelode-bridge@latest init rewrites every guide block with the latest rules (we add agent hints over time) and keeps this repo's existing pin — no need to pass the slug again. Use @latest so npx doesn't serve a cached older bridge. For the global block, re-run setup the same way. --no-agents writes only the marker.

Keep your token in STATELODE_TOKEN (or the MCP server config) — never in statelode.json or any of the guide files.