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

@momo-memory/growth-pm

v0.1.4

Published

Give your coding agent access to user signals, churn data, and growth intelligence from Momo

Readme

@momo-memory/growth-pm

Give your coding agent access to user signals, churn data, and growth intelligence from Momo.

Quick Start

1. Get your API key

Go to Momo Integrations → Momo MCP → Generate API Key.

2. Add to your coding agent

Add to Claude Code settings (~/.claude/settings.json) or project .mcp.json:

{
  "mcpServers": {
    "momo": {
      "command": "npx",
      "args": ["-y", "@momo-memory/growth-pm"],
      "env": {
        "MOMO_API_KEY": "your-api-key",
        "MOMO_API_URL": "https://app.usemomo.com"
      }
    }
  }
}

That's it. Two env vars — no Supabase credentials, no Anthropic key.

3. Try it

Ask your coding agent:

  • "What should I build next?"
  • "Which users are churning and why?"
  • "What are my power users doing differently?"
  • "Analyze why [email protected] dropped off"
  • "What features do ICP users care about most?"

Available Tools (11)

| Tool | Description | |------|-------------| | growth_get_overview | Dashboard summary: users, ICP breakdown, segments, features | | growth_get_power_users | Top users ranked by engagement score | | growth_get_dropped_icps | ICP users who are churning | | growth_get_icp | Derived Ideal Customer Profile traits | | growth_get_churn_funnel | Which features have highest churn | | growth_get_feature_adoption | Feature usage broken down by ICP fit | | growth_get_user_journey | A user's full timeline (meetings, decisions, signals) | | growth_get_signals | Conversation signals from emails and meetings | | growth_search | Search contacts and companies | | growth_analyze_user | AI-powered churn analysis for one user | | growth_analyze_cohort | AI cohort analysis across churning users |

How it works

The MCP server calls your Momo API with your API key. All data processing (scoring, ICP derivation, AI analysis) happens on Momo's server. Your coding agent just gets the results.

Your Agent → @momo-memory/growth-pm → Momo API → PostHog + Gmail + CRM data

Environment Variables

| Variable | Required | Description | |----------|----------|-------------| | MOMO_API_KEY | Yes | Your API key from Momo Integrations → MCP | | MOMO_API_URL | No | API URL (defaults to https://app.usemomo.com) |