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

fluct-local

v0.1.4

Published

Local stdio MCP edition of Fluct — single-user, SQLite-backed, runs entirely on your machine.

Downloads

47

Readme

fluct-local

Local, single-user, no-cloud edition of Fluct. Everything runs on your machine: SQLite at ~/.fluct/db.sqlite, the web UI on localhost:3737, and an MCP server that Claude Code spawns as a stdio subprocess. No accounts, no Supabase, no Vercel.

Built for environments where Claude Enterprise blocks custom remote connectors but local stdio MCP servers are still allowed.

Install + run (3 lines)

npm install -g fluct-local
fluct-local start
claude mcp add --transport stdio fluct-local -- fluct-local mcp

That's it. The first start automatically creates ~/.fluct/db.sqlite and applies the schema — no separate init step needed. Open http://localhost:3737, create a map in the UI, and Claude Code will see it through 56 MCP tools (get_service_map, create_product, create_memory, snapshot tools, scenario tools, and more).

What's in the DB

~/.fluct/db.sqlite holds everything: maps, nodes, edges, scenarios, permissions, memories, snapshots, comments, audit history. The file never leaves your machine.

To inspect manually:

sqlite3 ~/.fluct/db.sqlite '.tables'

To start fresh, delete the file and re-run fluct-local init.

What's stripped vs the cloud edition

This package is a fork of the cloud Fluct, with everything that has no meaning in a single-user local context removed:

  • Supabase auth, login/signup/share routes, OAuth flow
  • Organizations, members, invites, profiles
  • API keys, OAuth tokens
  • Watcher / notification system
  • Vercel deploy configuration

The map editor, memory map, scenarios, permission labels, snapshots, and the full MCP tool set are preserved.

Environment variables

| Variable | Purpose | | --------------- | ------------------------------------------------------------------------- | | FLUCT_DB_PATH | Override the SQLite location (default ~/.fluct/db.sqlite) | | FLUCT_MAP_ID | Pin the active map for fluct-local mcp (default: most recently updated) | | PORT | Override the web UI port (default 3737) |

CLI reference

fluct-local start          Boot the web UI on http://localhost:3737
fluct-local mcp            Run the stdio MCP server (target of `claude mcp add`)
fluct-local init           Create ~/.fluct/db.sqlite and apply the schema
fluct-local --help         Print this list

Develop from source

git clone <this repo>
cd fluct-local
npm install
npm run init               # apply schema to ~/.fluct/db.sqlite
npm run dev                # next dev on :3737, hot reload
npm run mcp                # run stdio MCP from source via tsx
npm run build              # produce dist/bin + .next/standalone for publish

License

MIT