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

@vitaminm/lcm-mcp

v0.0.3

Published

MCP server exposing Local Conversational Memory tools (lcm_grep, lcm_describe, lcm_expand, lcm_insert) to any MCP-compatible host.

Readme

@vitaminm/lcm-mcp

MCP server that exposes @vitaminm/lcm-core memory tools to any MCP-compatible host: Claude Code, NanoClaw v2, custom agents, etc.

Tools exposed

| Tool | Purpose | |---|---| | lcm_grep | Full-text search of an agent's message history via SQLite FTS5 | | lcm_describe | Metadata for a message or summary by id | | lcm_expand | Recover original messages covered by a summary | | lcm_insert | Insert a new message into an agent's lcm.db |

Every tool takes an agent parameter; the server is multi-tenant and opens each agent's lcm.db on demand. DBs live at <LCM_DB_DIR>/<agent>/lcm.db.

Install

npm install -g @vitaminm/lcm-mcp
# or run via npx (preferred for MCP host configs)

Configure as MCP server

In Claude Code:

claude mcp add lcm "npx @vitaminm/lcm-mcp" --env LCM_DB_DIR=$HOME/.config/lcm

In NanoClaw v2 (per agent group):

ncl groups config add-mcp-server --group whatsapp_sage \
  --name lcm --command "npx @vitaminm/lcm-mcp" --env LCM_DB_DIR=$HOME/.config/lcm

Configuration

| Env var | Default | Meaning | |---|---|---| | LCM_DB_DIR | ~/.config/lcm | Base directory for per-agent lcm.db files |

Smoke test

LCM_DB_DIR=$HOME/.config/lcm npx @vitaminm/lcm-mcp
# (server runs on stdio; ctrl-C to exit)

To smoke-test against your existing nanoclaw v1 lcm.dbs without copying:

LCM_DB_DIR="$HOME/Library/Application Support/nanoclaw/agents" npx @vitaminm/lcm-mcp

(v1 already stores DBs at <base>/<agent>/lcm.db which matches the layout this server expects.)