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

mempalace-mcp-proxy

v1.0.3

Published

Cursor stdio MCP proxy to memory API (Streamable HTTP) with MEM_X-User-Id; legacy debug server via MEM_LEGACY_DEBUG_SERVER=1.

Readme

mempalace-mcp-proxy

Local stdio MCP proxy that forwards Cursor-style clients to an upstream Streamable HTTP MCP service while injecting workspace and VCS context.

Metadata injection is tool-scoped, not global. The current whitelist is:

  • add_memory
  • search_memory

Other tools are forwarded without injected project metadata.

Structure

  • src/bin/
    • executable entrypoints
  • src/core/
    • shared runtime helpers
  • src/context/
    • request/header construction and client-context collection
  • src/proxy/
    • upstream MCP proxy implementation
  • src/vcs/
    • git/svn/workspace inspection
  • src/legacy/
    • old debug-server helpers kept behind MEM_LEGACY_DEBUG_SERVER

src/ root stays directory-only. Import modules through the structured subpaths instead of root-level compatibility wrappers.

The package now exposes stable subpaths through package.json.exports, for example:

const { getUpstreamMcpUrl } = require("mempalace-mcp-proxy/context/proxy-env");
const { inspectVcsAtWorkspace } = require("mempalace-mcp-proxy/vcs/workspace-vcs");

Run

Local dev (same entry as the published CLI):

npm start

Published package / one-shot (bin name matches package.json name):

npx -y mempalace-mcp-proxy

npx -y mempalace-mcp-proxy installs the package and runs the mempalace-mcp-proxy bin. A second bin name mcp-npx-server points to the same file for older configs.

Publish

This package is plain CommonJS JavaScript. There is no TypeScript build step or separate compile artifact.

npm install
npm run check
npm run pack:dry-run
npm run publish:npm