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

@neurealistic/backlog-mcp

v0.3.0

Published

MCP server for a markdown task backlog (Backlog.md-compatible) with atomic, collision-safe id assignment.

Readme

@neurealistic/backlog-mcp

An MCP server for a markdown task backlog — CRUD over backlog/tasks/*.md with atomic, collision-safe id assignment.

It writes the exact file shape that the Backlog.md CLI and board read (frontmatter + ## Acceptance Criteria / ## Implementation Plan / ## Implementation Notes), so it is a drop-in, safer alternative to backlog task create for programmatic callers: id allocation happens under a lockfile and a wx write, so a concurrent create can never overwrite an existing task. Structured JSON params also remove the CLI's shell-escaping footguns (backticks / angle brackets / pipes).

Install

npm install -g @neurealistic/backlog-mcp

Run

stdio (the default — an MCP client such as Claude Code spawns it):

BACKLOG_DIR=/path/to/backlog backlog-mcp

HTTP (Streamable HTTP transport):

MCP_PORT=3457 BACKLOG_DIR=/path/to/backlog backlog-mcp
# → http://localhost:3457/mcp

Register it in an MCP client (.mcp.json):

{
  "mcpServers": {
    "backlog": {
      "command": "backlog-mcp",
      "env": { "BACKLOG_DIR": "/path/to/backlog" }
    }
  }
}

Backlog directory

Resolved per call as: the tool's dir param → persisted home (set_home) → $BACKLOG_DIR → <cwd>/backlog. Call set_home once and later calls need no dir; an explicit dir still overrides per call, so one server can serve several backlogs (e.g. a workspace TASK-* and a project CEN-*) — the id prefix comes from each dir's config.yml (task_prefix). The home is stored per-user at $BACKLOG_MCP_CONFIG (default ~/.config/backlog-mcp/config.json).

Tools

| Tool | Description | |------|-------------| | set_home | Set the default backlog dir (persisted); optionally init an empty dir (creates tasks/ + config.yml). | | get_home | Show the current default backlog dir + how it was resolved. | | task_list | List tasks (id, title, status, labels, AC progress); optional status filter. | | task_get | Read one task in full (frontmatter + AC + plan + notes). | | task_create | Create a task with an atomic collision-safe id (never overwrites). | | task_update | Update status / plan / notes (replace), append a comment, or check/uncheck an AC by number. | | task_delete | Delete a task file (destructive). |

Every write takes a per-dir lock (.mcp-lock, 10s TTL); a create allocates its id inside the lock and writes with wx, so ids are race-free and never clobbered.

License

MIT