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

project-shared-memory-mcp

v1.0.33

Published

MCP server for project-scoped memory stored in .github/memories

Downloads

855

Readme

Project Memory MCP

An MCP (Model Context Protocol) server that gives AI assistants persistent, project-scoped memory. Memories are stored as files inside your repository under .github/memories/, so they travel with the project and can be shared via version control.

Based on the official VS Code memory tool, but redesigned to store memories per-project instead of globally — making them portable, version-controlled, and team-shareable.

Features

  • Project-scoped — memories live in .github/memories/ inside your repo
  • Version-controlled — commit and share context with your team
  • Full CRUD — view, create, edit (string replace / insert), rename, and delete memory files
  • Path-safe — validates all paths and blocks traversal attacks
  • Docker-ready — run as a container with a single mount

Setup

✨ One-Click Install

Install the MCP server directly into VS Code or VS Code Insiders:

⚠️ Select 'Install in Workspace'

Install in VS Code Install in VS Code Insiders

Option A — Run with NPX

No need to clone — just add this to .vscode/mcp.json in your project:

{
  "servers": {
    "project-memory": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "project-shared-memory-mcp"],
      "env": {
        "PROJECT_ROOT": "${workspaceFolder}"
      }
    }
  }
}

Option B — Run from source

git clone [email protected]:doctorspider42/Project-Shared-Memory-MCP.git
cd Project-Shared-Memory-MCP
npm install
npm run build

Add to your VS Code settings (.vscode/settings.json):

{
  "mcp": {
    "servers": {
      "project-memory": {
        "command": "node",
        "args": ["<path-to>/Project-Shared-Memory-MCP/dist/index.js"],
        "env": {
          "PROJECT_ROOT": "${workspaceFolder}"
        }
      }
    }
  }
}

Option C — Run with Docker

# Build the image
docker build -t project-shared-memory-mcp .

Register in VS Code MCP settings:

{
  "mcp": {
    "servers": {
      "project-memory": {
        "command": "docker",
        "args": [
          "run", "-i", "--rm",
          "-v", "${workspaceFolder}:/project",
          "project-shared-memory-mcp"
        ]
      }
    }
  }
}

The container expects the project to be mounted at /project (the default PROJECT_ROOT).

How It Works

All memory paths are virtual and start with /memories/. The server maps them to .github/memories/ inside the project root. For example:

/memories/notes.md  →  <project>/.github/memories/notes.md
/memories/session/  →  <project>/.github/memories/session/

You can instruct the AI to store notes, decisions, conventions, or any other context — and it will persist across sessions.

Available Tools

| Tool | Description | |---|---| | memory_view | View a file's contents or list a directory | | memory_create | Create a new memory file | | memory_str_replace | Replace an exact string in a memory file | | memory_insert | Insert text at a specific line | | memory_delete | Delete a file or directory | | memory_rename | Rename / move a file or directory |

Configuration

| Environment Variable | Default | Description | |---|---|---| | PROJECT_ROOT | /project | Absolute path to the project root. In VS Code's stdio mode, set this to ${workspaceFolder}. |

License

MIT