1. Conduid
  2. Developer Tools
  3. server-memory
MCP server · Developer Tools

server-memory

This project is derived from the original @modelcontextprotocol/server-memory package, modified for my specific needs. Providing persistent memory capabilities for AI models through a knowledge graph. This allows models like Claude to retain and recall information across interactions.

Unclaimed MIT last commit a year ago devtools
49Fair

Scored 5 months ago · breakdown

About server-memory

server-memory is an MCP server published by kwanLeeFrmVi in the Developer Tools category: this project is derived from the original @modelcontextprotocol/server-memory package, modified for my specific needs. Providing persistent memory capabilities for AI models through a knowledge graph. This allows models like Claude to retain and recall information across interactions.

The repository has 2 stars and 1 forks, with the last commit a year ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

Install
npx mcp-server-memory
Claude Code
claude mcp add memory-kwanleef -- npx -y mcp-server-memory
npx
npx -y mcp-server-memory

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about server-memory

Powered by Claude · Grounded in docs

I know everything about server-memory. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

Static checks derived from the repository 3 days ago. Heuristics on the source, not an audit.

  • ✓README presentThe repository ships documentation.
  • ✓License declaredUsable under a stated license.
  • !Tests presentNo tests found. Behaviour changes may go unnoticed between versions.
  • ✓Dependencies pinnedA lockfile pins dependency versions.
  • ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

README

MCP Server: Memory

NPM Version Bun Version License

This project is derived from the original @modelcontextprotocol/server-memory package, modified for my specific needs.

An MCP (Model Context Protocol) server providing persistent memory capabilities for AI models through a knowledge graph. This allows models like Claude to retain and recall information across interactions.

Overview

This server implements the Model Context Protocol and acts as a bridge between an AI model and a persistent knowledge graph stored locally. It allows the model to:

  • Create and manage entities (people, places, concepts, etc.).
  • Define relationships between entities.
  • Store observations or facts associated with entities.
  • Search and retrieve information from the knowledge graph.

By default, the knowledge graph is stored in a knowledge_graph.json file in the current working directory where the server is run.

Usage with Claude Desktop

This server is primarily designed to be used with MCP-compatible clients like the Claude Desktop application. You configure it within the client's settings.

Example mcpServers Configuration:

{
  "mcpServers": {
    "memory": {
      "command": "npx",
      "args": ["-y", "mcp-server-memory"],
      "env": {
        "MEMORY_FILE_PATH": "/path/to/your/custom_memory.json"
      }
    }
  }
}

...[rest of existing content remains unchanged...]

README fetched from the repository 3 days ago. The original is authoritative.

Questions

About server-memory

How do I install server-memory?

Run npx mcp-server-memory, then add the server to your MCP client's configuration.

Is server-memory safe to use with an AI agent?

Its trust score is 49 out of 100 (fair). It passes 4 of the 6 static security checks run so far; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is server-memory still maintained?

The last commit was a year ago and 1 open issues. That's long enough that you should check whether the maintainer is responding to issues before depending on it.