Knowledge Graph Memory Server

Created By
s2005a year ago
Standalone MCP server for enabling memory for Claude through a knowledge graph
Overview

What is Knowledge Graph Memory Server?

The Knowledge Graph Memory Server is a standalone implementation that enables persistent memory for the AI model Claude through a local knowledge graph, allowing it to remember user-specific information across chats.

How to use Knowledge Graph Memory Server?

To use the server, you can set it up with Docker or NPX, and configure it in your Claude Desktop settings. You can also use it as a standalone package by installing it via npm or npx.

Key features of Knowledge Graph Memory Server?

  • Persistent memory storage using a local knowledge graph.
  • Ability to create, read, update, and delete entities and relations.
  • Supports adding and removing observations for entities.
  • Search functionality for nodes based on queries.

Use cases of Knowledge Graph Memory Server?

  1. Personalizing user interactions by remembering preferences and past conversations.
  2. Managing relationships and interactions between different entities.
  3. Enhancing AI responses by providing context from previous chats.

FAQ from Knowledge Graph Memory Server?

  • Can the server handle multiple users?

Yes, it can manage memory for different users by creating unique entities for each user.

  • Is it easy to set up?

Yes, the setup process is straightforward with detailed instructions provided in the documentation.

  • What programming language is it built with?

The server is built using JavaScript and can be run in a Node.js environment.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
s2005
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago