Skip to content
MCP server

Memory Pulse

Corrections-first agent memory with a guard that blocks edits reintroducing retired values

Runs locallyStatus and history
Install
Pricing
Freemium
Platforms
CLI, self-hosted
Runs
Locally
Version
0.17.2
Listing updated
today

Similar MCP servers

About Memory Pulse

Memory Pulse is a freemium MCP server for knowledge and memory. It runs locally on your machine and is started by your AI client.

Memory Pulse keeps a ledger of cause-and-effect events in a file inside your own repository. A finding marked as a correction outranks everything at every brief size and never decays, and a guard blocks any edit that writes a retired value back, quoting the line that retired it. When recall cannot clear its confidence floor it returns nothing rather than a weak guess.

The README describes built-in memory security: a stored note that reads like an instruction never reaches the agent, and each row is hash-chained so any edit to the record shows. Four tools make up the surface, about 900 tokens of definitions by the README's measurement. remember runs locally and offline, while pulse, recall and execute use a hosted engine.

It works with Claude Code, Codex, Cursor, any stdio MCP client and GitHub Actions through hooks and plugins. A licence key is optional, and the README says there is a free tier without one. Setting a board file path adds board_post and board_read for messages between agents.

Install

Run in a terminal

claude mcp add memory-pulse --env MEMORY_PULSE_KEY='<MEMORY_PULSE_KEY>' -- npx -y memory-pulse

Add to claude_desktop_config.json

{
  "mcpServers": {
    "memory-pulse": {
      "command": "npx",
      "args": [
        "-y",
        "memory-pulse"
      ],
      "env": {
        "MEMORY_PULSE_KEY": "<MEMORY_PULSE_KEY>"
      }
    }
  }
}

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "memory-pulse": {
      "command": "npx",
      "args": [
        "-y",
        "memory-pulse"
      ],
      "env": {
        "MEMORY_PULSE_KEY": "<MEMORY_PULSE_KEY>"
      }
    }
  }
}

Add to .vscode/mcp.json

{
  "servers": {
    "memory-pulse": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "memory-pulse"
      ],
      "env": {
        "MEMORY_PULSE_KEY": "<MEMORY_PULSE_KEY>"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "memory-pulse": {
      "command": "npx",
      "args": [
        "-y",
        "memory-pulse"
      ],
      "env": {
        "MEMORY_PULSE_KEY": "<MEMORY_PULSE_KEY>"
      }
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "memory-pulse": {
      "command": "npx",
      "args": [
        "-y",
        "memory-pulse"
      ],
      "env": {
        "MEMORY_PULSE_KEY": "<MEMORY_PULSE_KEY>"
      }
    }
  }
}

Using several servers? Build one config file with the MCP config generator.

Configuration

  • MEMORY_PULSE_KEYLicense key (optional; free tier without one)
  • MEMORY_PULSE_LEDGERLedger file path (default ./.memory-pulse/events.jsonl)
  • MEMORY_PULSE_BOARDShared agent message board file; set it to add board_post and board_read

Tools this server provides (6)

Taken from the project documentation; the running server may differ.

remember
Record a finding or a correction locally and offline.
pulse
Re-enter the project on a ranked brief sized to a budget.
recall
Ask what caused X, what X caused, or when the link was strongest.
execute
Run JavaScript against memory in a sandbox so only the return value enters context.
board_post
Post to a shared agent message board when a board file is set.
board_read
Read the shared agent message board when a board file is set.

What it does

Corrections first
Corrections outrank other memories and never decay.
Edit guard
Blocks an edit that writes a retired value back.
Hash-chained ledger
Any edit to the stored record shows.
Injection filter
Stored notes that read like instructions never reach the agent.
Small tool footprint
Four tools totalling about 900 tokens of definitions.
Multi-host hooks
Installs hooks for Claude Code, Codex and Cursor.

Good for

  • Stop an agent re-adding a value you withdrew
  • Open each session on a ranked brief of prior findings
  • Trace what caused a past regression
  • Let several agents share a message board

Pricing

Freemium

Free tier without a licence key; paid key details not listed

Memory Pulse FAQ

Where is the memory stored?

In a local ledger file, by default ./.memory-pulse/events.jsonl, inside your repository.

Is there a free tier?

The registry entry says a licence key is optional and there is a free tier without one.

Which tools run offline?

remember runs locally and offline; pulse, recall and execute use a hosted engine.

How do I install it?

Register the stdio server with npx -y memory-pulse, or use the install script or a plugin.

Is Memory Pulse free?

Memory Pulse has a free plan, with paid plans for more usage or features.

How do I add Memory Pulse to Claude Code?

Run this command in your terminal: claude mcp add memory-pulse --env MEMORY_PULSE_KEY='<MEMORY_PULSE_KEY>' -- npx -y memory-pulse

What are the best alternatives to Memory Pulse?

The closest alternatives to Memory Pulse are REA, Context7, Chrome DevTools MCP, Codebase Memory and GitHub.

Where this comes from

  • Description: written from the project's README.
  • Install steps: from the official MCP Registry entry.

How AIPoweredBot checks servers