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

memorysync-mcp-install

v1.0.2

Published

One command to add the MemorySync MCP servers to Claude Desktop, Claude Code, Cursor, Devin Desktop, VS Code, Codex and OpenCode.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

mohammedrafayshafiuddinmohammedrafayshafiuddin

Keywords

memorysyncmcpmodel-context-protocolmemoryagent-memoryclaudecursordevinwindsurfcodexopencode

Readme

memorysync-mcp-install

One command to connect the MemorySync MCP servers to your AI clients.

npx memorysync-mcp-install

That writes configuration for every MCP client it finds on the machine, then you restart the client. The first memory tool call opens a browser to sign in; there is no API key to copy.

What it configures

| Server | URL | Auth | |---|---|---| | memorysync | https://mcp.memorysync.io/mcp | OAuth 2.1 with PKCE, or a MemorySync API key | | memorysync-docs | https://docs.memorysync.io/mcp | none |

Supported clients

| Client id | Config file | |---|---| | claude-code | ~/.claude.json | | claude-desktop | OS application-support directory | | cursor | ~/.cursor/mcp.json | | devin-desktop | ~/.config/devin/mcp_config.json | | windsurf | ~/.codeium/windsurf/mcp_config.json (legacy Cascade) | | vscode | .vscode/mcp.json in the current workspace | | opencode | ~/.config/opencode/opencode.json | | codex | ~/.codex/config.toml |

Claude Desktop launches MCP servers as local processes, so it is configured through the mcp-remote bridge. Every other client connects to the remote Streamable HTTP endpoint directly.

Windsurf was renamed Devin Desktop, and the rename moved the config file. Both paths are supported: devin-desktop is written on every machine, while the legacy Cascade file is only updated if it already exists, so an install that has not migrated still works and a current one gets no stray file.

Why there is no pip version

This package writes config files; it is not a library you import, so the language it happens to be written in never reaches the user. Node is also already needed for Claude Desktop, which launches MCP servers as local processes and therefore goes through mcp-remote — npm-only. A pip build would not remove that, only defer the surprise.

If you have no Node at all, you do not need this package. Both MemorySync MCP servers are hosted, so adding the URL by hand is the same outcome:

| Server | URL | |---|---| | memorysync | https://mcp.memorysync.io/mcp | | memorysync-docs | https://docs.memorysync.io/mcp |

PyPI memorysync is the Python SDK for the REST API. It is unrelated to MCP and does not install these servers.

Options

--list             Show which clients were detected, change nothing
--client <ids>     Comma-separated client ids (default: every detected client)
--server <names>   memory, docs or both (default: both)
--all              Write config even for clients that were not detected
--dry-run          Print what would change, write nothing
--remove           Remove the MemorySync entries again
--api-key <key>    Configure headless auth via the MEMORYSYNC_API_KEY env var

How it treats your config files

  • Only the MemorySync keys are added or removed. Everything else in the file is preserved, including comments in Codex's TOML.
  • Any existing file is copied to <file>.memorysync-backup-<timestamp> before a change is written.
  • A file that does not parse is reported and left untouched.
  • Re-running is safe: an already-correct config reports "already up to date".
  • --api-key never writes the key to disk. It configures the client to read MEMORYSYNC_API_KEY from the environment.

Manual setup

If you would rather edit the file yourself, --dry-run prints the exact result, and https://memorysync.io/mcp-install.json carries the same details in machine-readable form.