memory

This MCP server provides Memory Pulse capabilities for Claude Code, enabling structured, full-context memory storage and multi-level retrieval. The server exposes tools to store different memory types (decisions, solutions, sessions) and to retrieve memories with layered search strategies (exact, full-text, semantic) along with a built-in timeline and relationship graph. Once running, you can configure Claude Code to connect to the MCP server and issue commands like mpulse_store_decision, mpulse_store_solution, mpulse_store_session for writing memories, and mpulse_recall, mpulse_timeline, mpulse_relations for reading memories. The result is a local-first, zero-config memory system that preserves complete context without lossy compression, enabling more reliable AI reasoning and decision tracking. To use it, add an MCP configuration that points to memory-pulse-mcp-server (via npx or your preferred runtime) and then issue your memory operations through Claude Code or your MCP client of choice.

Prerequisites:

• Node.js 18+ installed on your system (for the MCP server distribution via npm/npx).
• Internet access to pull the MCP server package when using npx or npm.

Option A: Run with npx (Recommended)

1. Ensure Node.js is installed.
2. Run:

npx memory-pulse-mcp-server

Option B: Global installation

1. Ensure Node.js is installed.
2. Install globally and run the server:

npm install -g memory-pulse-mcp-server
memory-pulse-mcp

Option C: Build from source

1. Ensure Node.js and pnpm are installed.
2. Clone the repository and navigate to it:

git clone https://github.com/jiahuidegit/memory-mcp-server.git
cd memory-mcp-server

3. Install dependencies and build:

pnpm install
pnpm build

4. Run the built server (depending on the project’s build output, e.g., node dist/server.js or equivalent).

Prerequisites summary:

• Node.js 18+ (for npx/npm usage)
• pnpm (for build workflow, optional if using prebuilt packages)
• Internet access to fetch dependencies

Environment variables:

• MEMORY_STORAGE controls storage type: sqlite (default) or postgresql. If using PostgreSQL, set MEMORY_STORAGE to 'postgresql' and provide DATABASE_URL.
• MEMORY_DB_PATH specifies the SQLite database path when using sqlite.
• DATABASE_URL provides the PostgreSQL connection string when using PostgreSQL. Common issues:
• If MEMORY_STORAGE is set to postgresql but DATABASE_URL is missing or invalid, the server will fail to connect. Ensure the URL is correct and the database is reachable.
• When using npx, the latest version is retrieved automatically. If you need stability, install globally and pin the version.
• For Claude integration, ensure the MCP configuration points to the correct command and arguments (npx memory-pulse-mcp-server) as shown in the examples. Tips:
• The default SQLite storage is zero-config and stored at ~/.emp/memory.db. You can override with MEMORY_DB_PATH.
• The MCP tools cover storage (mpulse_store*, mpulse_store_decision, mpulse_store_solution, mpulse_store_session) and retrieval (mpulse_recall, mpulse_timeline, mpulse_relations).
• Always restart the MCP client after configuration changes.