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

sample-notes-mcp-server

v0.1.0

Published

A tiny Model Context Protocol (MCP) server for saving, listing, searching, and deleting text notes, over stdio.

Readme

sample-notes-mcp-server

A tiny Model Context Protocol (MCP) server for saving, listing, searching, and deleting text notes — over stdio.

It knows nothing about any particular client. It just speaks MCP over stdio, so any MCP client (Claude Desktop, Claude Code, or your own) can use it. Notes persist as a JSON file on disk.

Install

No install required — run it straight from npm with npx:

npx sample-notes-mcp-server

Or install it globally:

npm install -g sample-notes-mcp-server
sample-notes-mcp-server

Usage

sample-notes-mcp-server [notes-file]
  • notes-file (optional) — path to the JSON file where notes are stored. Defaults to ./notes.json in the current working directory. The file is created on first write.

The server communicates over stdio: stdout is reserved for the MCP protocol, so all human-facing logging goes to stderr. You normally don't run it by hand — an MCP client launches it for you (see below).

Tools

| Tool | Arguments | Description | | --- | --- | --- | | add_note | text: string | Save a short text note. Returns the new note's id. | | list_notes | (none) | List all saved notes. | | search_notes | query: string | Find notes containing query (case-insensitive substring match). | | delete_note | id: number | Delete a saved note by its id. |

Each note is stored as { id, text, createdAt }, where id auto-increments and createdAt is an ISO 8601 timestamp.

MCP client configuration

Add the server to your MCP client's config. Most clients use a JSON block like this:

{
  "mcpServers": {
    "notes": {
      "command": "npx",
      "args": ["-y", "sample-notes-mcp-server", "/absolute/path/to/notes.json"]
    }
  }
}

The trailing path argument is optional — omit it to use ./notes.json relative to the client's working directory. Using an absolute path is recommended so your notes land in a predictable place.

Claude Desktop

Add the block above to claude_desktop_config.json:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Then restart Claude Desktop.

Claude Code

claude mcp add notes -- npx -y sample-notes-mcp-server /absolute/path/to/notes.json

Development

npm install      # install dependencies
npm run build    # compile TypeScript to dist/
npm run start    # run the built server
npm run smoke-test  # spawn the built server via a real MCP stdio client and exercise every tool

The build uses a two-config split: tsconfig.json drives the editor and typecheck (and covers the smoke test), while tsconfig.build.json excludes the smoke test so it never ships in dist/.

License

MIT — see LICENSE.