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

@amugona/slog-mcp

v0.1.0

Published

slog MCP server — search, read and capture your private slog notes from Claude and other MCP clients

Readme

@amugona/slog-mcp

Search, read, and capture your slog notes — right from Claude.

한국어 문서는 패키지에 동봉된 README.ko.md 를 참고하세요.

slog is a private-first journal: every note you write is private by default, and you choose what (if anything) becomes public. This MCP server connects MCP clients like Claude Code and Claude Desktop to your slog notes, so you can:

  • Ask about your own life. "When did I start running this year?" — Claude searches your notes and answers from what you wrote.
  • Capture without switching apps. Mid-conversation, say "save this as a note" and it lands in slog — always as a private note.
  • Edit and organize. Update a note's title, body, or series without leaving the chat.

It talks to the slog REST API over HTTPS with your personal API key. It never opens your database directly, and it cannot publish, unpublish, or delete anything — those actions are blocked server-side for API keys, not just omitted from the tool list.

Quick start

1. Get an API key

In slog Studio, go to Settings → API keys and create a key.

The full key (slog_...) is shown only once — copy it right away. If you lose it, use Regenerate on the key row to get a new secret (the old one stops working immediately).

2. Connect your client

Claude Code

claude mcp add slog -e SLOG_API_KEY=slog_your_key_here -- npx -y @amugona/slog-mcp

Claude Desktop — add to claude_desktop_config.json (Settings → Developer → Edit Config):

{
  "mcpServers": {
    "slog": {
      "command": "npx",
      "args": ["-y", "@amugona/slog-mcp"],
      "env": { "SLOG_API_KEY": "slog_your_key_here" }
    }
  }
}

Any other MCP client that supports stdio servers works the same way: run npx -y @amugona/slog-mcp with the SLOG_API_KEY environment variable set.

3. Try it

Start a new conversation and ask something like:

What did I write about coffee last month?

Tools

| Tool | What it does | |---|---| | search_notes | Search notes (space-separated terms, AND match) with date range, series filter, and pagination | | capture_note | Create a new note — always private | | get_note | Read one note in full | | update_note | Edit a note's title, body, series, or draft state | | list_series | List your series |

What it deliberately can't do

Publishing, unpublishing, and deleting are not available through API keys — the slog API rejects those requests no matter what client sends them. The worst an AI mishap could do here is add or edit a private note; it can never expose or destroy one. Use slog Studio for publishing and deleting.

Configuration

| Environment variable | Required | Default | Notes | |---|---|---|---| | SLOG_API_KEY | ✅ | — | Your personal key from Studio → Settings → API keys | | SLOG_API_URL | | https://slog.amgn.app | Point elsewhere for self-hosted or local development (use http://127.0.0.1:3000, not localhost) |

Troubleshooting

  • "SLOG_API_KEY 가 필요합니다" on startup — the key environment variable is missing. Check the env block in your client config.
  • Authentication errors on every call — the key may have been revoked or regenerated. Issue a new one in Studio and update your config.
  • The server prints diagnostics to stderr only; a healthy start logs [slog-mcp] ready — <api url>.

License

MIT