mcp-shared-memory

This MCP server provides a shared, structured memory store that can be used across multiple MCP-enabled tools and chat sessions. It is designed to help tools like Claude Desktop, Cursor, Windsurf, Cline, RooCode, Warp, Antigravity, and others maintain project-specific memories, entities, concepts, and sessions in a centralized, organized way. You can run the server directly with npx, or install and run it from a local environment after cloning the repository. Once running, configure your MCP-enabled tools to connect to the shared-memory server so they can read from and write to the memory store, enabling consistent context and memory across tools and sessions. A notable addition in v0.1.2 is version tracking and update notifications, so you can ask the assistant “What’s new in mcp-shared-memory?” to learn about latest changes.

Prerequisites:

• Node.js and npm installed on your system
• Git for cloning repositories (optional if using npx)

Installation steps:

1. Install dependencies and build (if you prefer a local install):

# Clone the repository
git clone https://github.com/Ideas-Net-Studio/mcp-shared-memory.git
cd mcp-shared-memory

# Install dependencies
npm install

# Build for production (if provided by the project)
npm run build

2. Run using npx (recommended):

npx -y mcp-shared-memory

3. If you clone and want to run locally after build, configure your MCP tool to point to the built entry:

{
  "mcpServers": {
    "shared-memory": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-memory/dist/index.js"]
    }
  }
}

4. Optional: add an npm script for convenience in your project, e.g. in package.json:

"scripts": {
  "start:mcp-shared-memory": "npx -y mcp-shared-memory"
}

Then run: npm run start:mcp-shared-memory

Tips and recommendations:

• Environment and memory storage: memoryDir, enabled, and description can typically be configured per your project needs (e.g., in a .mcp-memory.json or mcp-memory.json file as shown in the project structure).
• If you build locally, ensure the absolute path to the built entry (dist/index.js) is correct when configuring tools.
• Common issues: ensure Node and npm versions are compatible with the server, and that your MCP tools are configured to point to the correct host/port or file path as required by your setup.
• Version 0.1.2 adds version tracking and update notifications; use the assistant prompt “What’s new in mcp-shared-memory?” for recent changes.
• This server is designed for multi-tool compatibility, so you should be able to connect multiple MCP-enabled tools to the same memory store and share project memories across sessions.