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

@danzimon/next-best-prompt-mcp

v0.2.1

Published

MCP server for the next_best_prompt 'next-best-prompts' end-of-turn rule — end a substantive turn with 2-4 ranked, copy-paste-ready next moves, and skip when there's none. Pure guidance: no secrets, no network, no side-effecting tools. Install locally (st

Vulnerabilities

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

Links

Maintainers

danzimondanzimon

Keywords

mcpmodel-context-protocolclaudeclaude-codeclaude-desktopnext-best-promptsnext_best_promptaiprompt

Readme

next_best_prompt — next-best-prompts

A pointer to your best next moves. next_best_prompt is a tiny MCP server that carries one rule: after a substantive turn, end your reply with a short, ranked menu of next-best-prompts — the 2–4 highest-leverage things to do next, each a copy-paste-ready prompt you can trigger by replying with a single digit — and skip entirely when there's no high-value next move.

Pure guidance: no secrets, no network calls, no side-effecting tools. Safe to install anywhere, against any project or chat.

One rule, two transports

The rule lives in rule/next-best-prompt.md (single source of truth) and is code-generated into a shared module that both transports import:

  • stdio (src/) — published to npm as @danzimon/next-best-prompt-mcp. For local clients: Claude Code and Claude Desktop (local install).
  • HTTP (remote/, Next.js + mcp-handler) — deployed to Vercel as a remote connector. For Claude.ai web + mobile and any client that takes a hosted MCP URL.

Both expose identical surfaces: the instructions field, a next_best_prompt prompt, and a get_next_best_prompts_rule tool.

Install

Claude Code

claude mcp add next_best_prompt -- npx -y @danzimon/next-best-prompt-mcp

Claude Code auto-injects the server instructions, so the rule applies every turn automatically. (Optional belt-and-suspenders: also wire the SessionStart hook in hook/sessionstart-next-best-prompt.sh.)

Claude Desktop

Either point it at the local stdio server…

// claude_desktop_config.json
{ "mcpServers": { "next_best_prompt": { "command": "npx", "args": ["-y", "@danzimon/next-best-prompt-mcp"] } } }

…or use the hosted endpoint as a remote connector (see below). Fully quit and relaunch Desktop after editing the config.

Claude.ai web + mobile (hosted connector)

Mobile can't run a local server — use the hosted endpoint. On claude.ai (web): Settings → Connectors → Add custom connector, URL:

https://next-best-prompt-mcp-remote.vercel.app/api/mcp

It's account-scoped, so it appears in the mobile app automatically. Requires a plan that supports custom connectors (Pro / Max / Team / Enterprise).

Self-host the hosted endpoint

cd remote
npm install
npm run dev        # local
# or deploy remote/ to Vercel; the MCP endpoint is /api/mcp

Always-on everywhere

Only Claude Code auto-fires the rule every turn. On Desktop, web, and mobile, next_best_prompt is available as an on-demand prompt/tool — for automatic every-turn behavior, paste the condensed rule into your account preferences or a project's custom instructions. See ALWAYS-ON.md.

Development

npm install
npm run embed        # rule/next-best-prompt.md + shared/next-best-prompt.template.ts -> generated modules
npm run check-sync   # fail if the generated copies drifted from source
npm run build        # tsc -> dist/ (prebuild runs embed)

Edit the rule in rule/next-best-prompt.md or the prompt/tool wiring in shared/next-best-prompt.template.ts, then npm run embed. check-sync (run on prepublishOnly) guarantees the stdio and HTTP builds never drift.

License

MIT © 2026 Dan Zimon