MCP Neo4j Knowledge Graph Memory Server

Created By
JovanHsua year ago
MCP Memory Server with Neo4j backend for AI knowledge graph storage
Overview

What is MCP Neo4j Knowledge Graph Memory Server?

MCP Neo4j Knowledge Graph Memory Server is a memory server based on the Neo4j graph database, designed for storing and retrieving information during interactions between AI assistants and users. It enhances the official Knowledge Graph Memory Server by using Neo4j as the backend storage engine.

How to use MCP Neo4j Knowledge Graph Memory Server?

To use the server, you can install it via npm or Docker. For npm, run npm install -g @jovanhsu/mcp-neo4j-memory-server. For Docker, clone the repository and use docker-compose to start the server.

Key features of MCP Neo4j Knowledge Graph Memory Server?

  • High-performance storage based on Neo4j graph database
  • Powerful fuzzy search and exact match capabilities
  • Complete CRUD operations for entities, relationships, and observations
  • Full compatibility with the MCP protocol
  • Support for complex graph queries and traversals
  • Docker support for easy deployment

Use cases of MCP Neo4j Knowledge Graph Memory Server?

  1. Storing user interactions for personalized AI responses
  2. Building complex knowledge graph applications
  3. Enhancing AI assistant capabilities with memory retrieval

FAQ from MCP Neo4j Knowledge Graph Memory Server?

  • Can I use this server with any AI assistant?

Yes! It is designed to integrate with various AI assistants that support the MCP protocol.

  • Is there a cost to use the MCP Neo4j Knowledge Graph Memory Server?

No, it is open-source and free to use under the MIT license.

  • What are the system requirements?

You need Node.js >= 22.0.0 and a Neo4j database (local or remote) to run the server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
JovanHsu
Star
0
Language
TypeScript
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