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

lainbridge

v1.0.1

Published

Claude Code bridge for Roblox Studio — read, edit, and build inside Studio through 30+ MCP tools

Downloads

175

Readme

lainbridge

lets claude code build stuff directly in roblox studio. it reads your game, edits scripts, creates instances and UI, runs lua, takes screenshots — 30+ tools. everything is undoable with ctrl+z.

you need

install

  1. install node.js if you don't have it (click the big green LTS button)
  2. download LainbridgeSetup.exe and run it
  3. in your project folder, add the tools to claude code:
    claude mcp add lainbridge -- npx -y lainbridge@latest

how to use

  1. double-click "Lainbridge" on your desktop (starts the bridge — leave it open)
  2. open studio, go to Home > Game Settings > Security, turn on "Allow HTTP Requests"
  3. click Connect in the Lainbridge panel in studio
  4. open claude code — the tools are ready

every time after that

  1. double-click "Lainbridge" on your desktop
  2. open studio, click Connect in the lainbridge panel
  3. open claude code — it just works

what can it do

just tell claude what you want. some examples:

  • "add a sprint system to my game"
  • "fix the gun not doing damage"
  • "build a shop UI with 3 tabs"
  • "make the NPC walk between waypoints"
  • "show me a screenshot of the game"
  • "find all scripts that use RemoteEvents"

claude reads your game state, understands how your scripts connect, makes the changes, and verifies they work.

tools

readingget_context, read_script, get_instance, get_status, get_errors, get_console

analysisanalyze_system, get_script_deps, search_scripts

creatingcreate_script, create_instance, create_ui, batch_create

editingedit_surgical, edit_lines, edit_regex, edit_script, set_properties

executionrun_lua, run_in_playtest, execute_command

visualscreenshot, capture_viewport

troubleshooting

"commands aren't working" — make sure the bridge window is open and studio shows "Connected" in the lainbridge panel.

"Allow HTTP Requests" — you need to enable this in studio every time you open a new place. Home > Game Settings > Security.

"tools not showing up in claude code" — make sure you ran claude mcp add lainbridge -- npx -y lainbridge@latest in your project folder.

"node is not recognized" — install node.js from https://nodejs.org and restart your terminal.

how it works

claude code <-> mcp server <-> bridge <-> studio plugin <-> roblox studio

the bridge keeps a copy of your game state in memory so reads are instant. edits go through the plugin which wraps everything in studio's undo system.

multiple studio instances

run bridges on different ports:

lainbridge start 9091
lainbridge start 9092

use the switch_port tool in claude code to swap between them.

license

MIT