AI Engineer Neo4j Memory MCP Demo

Created By
a-s-g93a year ago
A short demo of the Neo4j Memory MCP server.
Overview

what is AI Engineer Neo4j Memory MCP Demo?

AI Engineer Neo4j Memory MCP Demo is a demonstration project showcasing the integration of the Neo4j Memory MCP server with Claude Desktop, allowing for memory retrieval and updates during conversations.

how to use AI Engineer Neo4j Memory MCP Demo?

To use the demo, set up the Neo4j database, install the required Python package manager (uv), and configure Claude Desktop to connect to the Neo4j Memory MCP server. Follow the provided instructions to set up your environment and initiate conversations.

key features of AI Engineer Neo4j Memory MCP Demo?

  • Integration with Neo4j for memory storage and retrieval
  • Automatic logging of interactions in the Neo4j database
  • Ability to access memories across different conversations and clients

use cases of AI Engineer Neo4j Memory MCP Demo?

  1. Enhancing conversational AI with memory capabilities
  2. Storing and retrieving semantic memories for improved user interactions
  3. Facilitating knowledge sharing between different AI clients using the same Neo4j instance

FAQ from AI Engineer Neo4j Memory MCP Demo?

  • What is the purpose of the Neo4j Memory MCP server?

It serves as a memory storage solution for conversational AI, allowing for context retention across interactions.

  • Is the demo free to use?

Yes! The demo is available for anyone to use and explore.

  • Can I use my own Neo4j database credentials?

Yes! You can replace the default credentials with your own when configuring the server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
a-s-g93
Star
0
Language
-
License
-

Recommend Servers

View All
Alloy

2 days ago
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)

8 hours ago
Crevio

a day ago