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

agy-frontend-mcp

v0.1.0

Published

MCP server that delegates frontend coding to agy (Antigravity/Gemini) inside an isolated git worktree

Readme

agy-frontend-mcp (TypeScript / Node)

A TypeScript/Node port of agy-frontend-mcp — an MCP server that delegates frontend coding to agy (the Antigravity / Gemini CLI) inside an isolated git worktree, so an MCP client (e.g. Claude Code) can hand a whole frontend task to Gemini, review the diff, and decide whether to merge.

Same behavior and design as the Python version (the design docs in ../docs/superpowers/specs/ apply); this is the "more universal language" build with npx distribution.

Requirements

  • agy on PATH and logged in
  • Node ≥ 18, git

Tools

  • frontend_delegate(task, model?, base_repo?, session_id?, add_dirs?, timeout_seconds?, sandbox?) — run one agy agentic loop in a fresh worktree (or continue via session_id). Returns {session_id, branch, worktree_path, status, summary, changed_files, diffstat, stderr_tail, elapsed_s}. Success is judged by the git diff, not agy's exit code (statussuccess / needs_attention / timeout).
  • frontend_diff(session_id) — the worktree's git diff (truncated past MAX_DIFF_BYTES).
  • frontend_finish(session_id, action)merge into base, or discard; the per-task agy state dir is reclaimed either way.

Build & run

npm install
npm run build          # → dist/
npm test               # vitest (fakes agy)
AGY_SMOKE=1 npm test -- tests/smoke.test.ts   # real agy, end-to-end

Register in Claude Code (.mcp.json)

{
  "mcpServers": {
    "agy-frontend": {
      "command": "node",
      "args": ["/abs/path/to/agy-frontend-mcp/ts/dist/server.js"],
      "timeout": 1800000
    }
  }
}

Once published to npm, npx agy-frontend-mcp works as the command/args.

How it works (the agy quirks this encapsulates)

  • Isolationagy --gemini_dir=<empty per-task dir> relocates all agy state so it can't read other projects' transcripts; OAuth is unaffected (system keyring).
  • Writes into the worktree — the prompt is scoped to the absolute worktree path, because agy writes loose filenames into its own scratch sandbox.
  • No hangs — every agy subprocess gets stdin = ignore (agy blocks on inherited stdin) and is killed by process group on timeout.
  • Permissions--dangerously-skip-permissions (no TTY); safety is the worktree boundary. sandbox=false by default (frontend tasks often need the network).

Notes

  • Dev-only npm audit findings come from the vitest/vite/esbuild toolchain and are not shipped (the published package contains only dist/ + @modelcontextprotocol/sdk + zod).

License

MIT — see ../LICENSE.