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

@gitloomhq/mcp

v0.1.0

Published

MCP server for GitLoom Cloud — memory for any MCP-speaking agent

Readme

@gitloomhq/mcp

MCP server for GitLoom Cloud — long-term memory for any agent that speaks the Model Context Protocol.

GITLOOM_API_KEY=gl_live_... npx -y @gitloomhq/mcp

Two tools: recall_memory and save_memory. Their descriptions and schemas come from @gitloomhq/sdk, so a tool behaves identically here, through the SDK, and in the OpenAI or Anthropic tool formats.

Configuring a host

The GitLoom CLI writes the config for you, in each host's own shape:

gitloom install claude-code --cloud
gitloom install codex --cloud --write
gitloom install opencode --cloud --namespace support
gitloom install openclaw --cloud
gitloom install hermes --cloud

Or by hand:

{
  "mcpServers": {
    "gitloom": {
      "command": "npx",
      "args": ["-y", "@gitloomhq/mcp"],
      "env": { "GITLOOM_API_KEY": "gl_live_..." }
    }
  }
}

Local memory instead

This server talks to a hosted namespace. To keep the memory on your own machine as a git repository, use the CLI's own server — same protocol, no account:

gitloom init ~/memory
gitloom install claude-code --write

Environment

| Variable | Purpose | |---|---| | GITLOOM_API_KEY | required — create one at app.gitloom.cloud | | GITLOOM_NAMESPACE | which namespace to use (default: the account's default) | | GITLOOM_BASE_URL | override the API host |