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

engram-mcp

v1.0.0

Published

MCP server for Engram: persistent memory for AI

Readme

engram-mcp

MCP server for Engram — persistent memory for AI.

Give Claude memory that persists across conversations.

Install

npm install -g engram-mcp

Setup

1. Get your API key

Sign up at ngrm.ai and copy your API key.

2. Configure MCP

Cursor — Edit ~/.cursor/mcp.json:

{
  "mcpServers": {
    "engram": {
      "command": "engram-mcp",
      "env": {
        "ENGRAM_API_KEY": "eng_your_key_here"
      }
    }
  }
}

Claude Code — Edit ~/.claude/mcp.json:

{
  "mcpServers": {
    "engram": {
      "command": "engram-mcp",
      "env": {
        "ENGRAM_API_KEY": "eng_your_key_here"
      }
    }
  }
}

3. Restart your IDE

Restart Cursor or Claude Code. You'll now have memory tools available.

Tools

| Tool | Description | |------|-------------| | memory_observe | Call after every user message. Learns automatically. | | memory_recall | Search memories by query. | | memory_learn | Store something explicitly. | | memory_bg | Working memory (short-term, decays). | | memory_stats | Get memory counts. | | memory_session | Start session — gets context in one call. | | memory_end_session | End session, save state. | | memory_deep | Deep exploration of a topic. |

Usage

Add rules to make Claude use memory automatically. Example:

On every message:
1. Call memory_observe with the user's message
2. Call memory_recall for relevant context
3. Respond
4. Call memory_learn for important new information

Or just ask Claude to remember things — it'll figure it out.

Frames

Memories are organized into frames:

  • SELF — Identity, who the AI is
  • USER — Facts about the user
  • EVENTS — What happened
  • KNOWLEDGE — Facts, information
  • PREFERENCES — Likes, values
  • GOALS — Objectives
  • QUESTIONS — Open unknowns
  • SKILLS — How to do things
  • CONCEPTS — Patterns, theories
  • RELATIONS — Connections between things

Use frames to filter recall: memory_recall("preferences", frames: ["PREFERENCES"])

Links