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

@jcyamacho/agent-memory

v0.3.0

Published

Persistent memory for MCP-powered coding agents.

Readme

agent-memory

Persistent memory for MCP-powered coding agents.

agent-memory is a stdio MCP server that gives your LLM durable memory backed by Markdown files on disk. It helps your agent remember preferences, project context, and prior decisions across sessions.

It exposes four tools:

  • remember -> save facts, decisions, preferences, and project context
  • review -> load workspace and global memories sorted by most recently updated
  • revise -> update an existing memory when its content changes or when it should become global
  • forget -> delete a memory that is no longer relevant

Quick Start

Claude CLI:

claude mcp add --scope user memory -- npx -y @jcyamacho/agent-memory

Codex CLI:

codex mcp add memory -- npx -y @jcyamacho/agent-memory

OpenCode:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "memory": {
      "type": "local",
      "command": ["npx", "-y", "@jcyamacho/agent-memory"]
    }
  }
}

Optional LLM Instructions

Optional LLM instructions to reinforce the MCP's built-in guidance. The server instructions and tool descriptions already cover most behavior -- this prompt targets the habits models most commonly miss:

## Agent Memory

- Use `memory_review` at conversation start to load workspace memories into
  context. During the session, use `memory_remember`, `memory_revise`, and
  `memory_forget` to keep memories accurate.
- Pass `workspace` on `memory_remember` for project-scoped memory. Omit it
  only for facts that apply across projects.
- Remember preferences, confirmed approaches, and decisions with reasoning
  that would be lost after the session.
- Revise content when a fact changes, promote a project-scoped memory to
  global only when it truly applies across projects, and forget it when it is
  no longer relevant.
- Do not store secrets, temporary task state, or facts obvious from current
  code or git history.

Mutating Tool Output

remember, revise, and forget return the full affected memory as XML with updated_at and scope information so clients that hide tool-call arguments can still see what changed. forget includes deleted="true" on the returned <memory> element.

How Review Works

review requires a workspace and returns memories saved in that workspace plus global memories (saved without a workspace), sorted by most recently updated. Results are paginated -- pass page to load older memories.

When you save a memory from a git worktree, agent-memory stores the main repo root as the workspace. review applies the same normalization to incoming workspace queries so linked worktrees still match repo-scoped memories exactly.

Configuration

Store Location

By default, memories are stored under:

~/.config/agent-memory/

Override it with:

AGENT_MEMORY_STORE_PATH=/absolute/path/to/agent-memory

The store layout is:

<store>/
  globals/<memory-id>.md
  workspaces/<encoded-workspace>/<memory-id>.md

Set AGENT_MEMORY_STORE_PATH when you want to:

  • keep memory in a project-specific location
  • share a memory store across multiple clients
  • keep the Markdown files somewhere easier to back up or inspect

License

MIT