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

@loupfeed/demo-mcp

v0.2.1

Published

loupfeed demo engine MCP server — lets an agent (Claude Code, Claude Desktop, …) discover an app's navigable surface, ground scenario files in the resulting map, and play them back humanized while recording walkthrough videos.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

giles.fokamgiles.fokam

Keywords

Readme

@loupfeed/demo-mcp

The agent surface of the loupfeed demo engine (#6): an MCP server that lets Claude Code (or any MCP client) produce recorded, human-looking product walkthroughs of your app.

The division of labour: the agent writes scenario files; the engine guarantees the playback invariant — visible cursor travel, clicks only on elements actually in the viewport, wheel-burst scrolling, human typing cadence (see @loupfeed/demo-core).

Tools

| Tool | Purpose | | --- | --- | | demo_discover | Crawl the app → app map (route templates, scenario-ready selectors, nav edges). Sign in via prologueSteps or a storage state. | | demo_get_map | Re-read the stored map — ground every scenario in it. | | demo_validate_scenario | Schema-check a draft; returns exact issues to fix. | | demo_save_scenario | Validate + persist scenarios/<name>.scenario.json. | | demo_play | Humanized playback, recorded; per-step results + video path. | | demo_list_recordings | The takes produced so far. |

Artifacts live under LOUPFEED_DEMO_DIR (default .loupfeed-demo/). ${VAR} placeholders in scenarios resolve from the server's environment at play time — credentials never enter scenario files or the conversation.

Setup (Claude Code)

claude mcp add demo \
  --env LOUPFEED_DEMO_DIR=.loupfeed-demo \
  --env [email protected] \
  --env DEMO_PASSWORD=… \
  -- npx -y @loupfeed/demo-mcp

playwright is a peer dependency — install it and its browsers where the server runs (npx playwright install chromium).

The agent loop

Give your agent instructions along these lines (this is the "demo director" skill):

When asked for a demo: 1) demo_discover the app (use prologueSteps with ${DEMO_EMAIL}/${DEMO_PASSWORD} placeholders if sign-in is needed); 2) read the map and write a scenario for the requested flow, using the map's selectors verbatim, read steps between meaningful moments, and expectVisible assertions after each transition; 3) demo_validate_scenario, fix issues, demo_save_scenario; 4) demo_play and hand the user the video path. If a step fails, read the failure screenshot next to the recording, adjust the scenario, and re-play — same seed reproduces the same take.