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

@robinsingh/lore-mcp

v0.2.0

Published

Read and write .lore/ notes from any MCP-speaking AI coding agent.

Downloads

644

Readme

@robinsingh/lore-mcp

Read and write Lore notes from any AI coding agent that speaks MCP.

Lore notes are Markdown files in a repository's .lore/ directory that record what source comments cannot: why code is the way it is, constraints that are not visible in the file, and instructions about how it may be changed. This server puts them in front of the agent before it edits.

You do not need the VS Code extension. The notes are plain files and the format is documented — this server is one way to read them, not the only one.

Tools

| Tool | What it does | |---|---| | lore_read(path) | Notes for a file, plus its parent folders' notes and repository-wide notes, broadest first | | lore_search(query) | Keyword search across note titles, bodies, paths and symbols | | lore_write(path, title, body, …) | Records a new note |

lore_write defaults to scope: "personal", which lands in the gitignored .lore/local/. Passing scope: "team" writes to .lore/notes/, which is committed — so an agent should only do that when the user asks for a note the whole team will see.

Install

The server reads the repository given as its first argument, falling back to LORE_ROOT and then to the working directory it was launched in.

Claude Code

claude mcp add lore -- npx -y @robinsingh/lore-mcp

Codex~/.codex/config.toml

[mcp_servers.lore]
command = "npx"
args = ["-y", "@robinsingh/lore-mcp"]

Cursor, Cline, Windsurf, Zedmcp.json

{
  "mcpServers": {
    "lore": { "command": "npx", "args": ["-y", "@robinsingh/lore-mcp"] }
  }
}

Getting the agent to use it

Reading notes before editing is a habit worth stating explicitly. Add this to CLAUDE.md or AGENTS.md:

Before editing a file, call lore_read on it. The notes there record constraints
that are not visible in the source.

For Claude Code there is a plugin that does this with hooks instead of relying on the model to remember.

Note format

One Markdown file per note, with YAML frontmatter:

---
path: src/payment/service.py
symbol: PaymentService.charge_customer
line: 128
snippet: "async def charge_customer(amount: int, retries: int = 3):"
type: ai-instruction
status: open
created: 2026-07-28
---

# Payment retry loop

Never remove the retry loop — it works around a Stripe timeout bug.
Remove only after ticket #841.

path may be a file, a folder (src/api/), or . for the whole repository. A note's scope is the directory it lives in: .lore/local/ is personal and gitignored, .lore/notes/ is shared and committed.

Full specification: spec/lore-format.md.

Development

npm install
npm run check    # typecheck
npm run build    # bundle to dist/server.js

The note store is imported from the VS Code extension's ../src/noteStore.ts and bundled in, so there is one implementation of the format rather than two that drift.

Licence

MIT