Graph Memory RAG MCP Server

Created By
lecharlesa year ago
A Model Context Protocol (MCP) server implementation for graph-based memory storage with RAG capabilities
Overview

what is Graph Memory RAG MCP Server?

Graph Memory RAG MCP Server is a Model Context Protocol (MCP) server implementation that provides graph-based memory storage capabilities, allowing AI agents to store and retrieve information in a graph structure, which is ideal for maintaining context and relationships between different pieces of information.

how to use Graph Memory RAG MCP Server?

To use the server, install the necessary dependencies with npm install, then start the server using node app.js. You can interact with the server through its API to create entities, manage relationships, and query data.

key features of Graph Memory RAG MCP Server?

  • In-memory graph database storage
  • Entity creation and management
  • Relationship creation between entities
  • Query capabilities for both entities and relationships
  • Delete operations with cascading relationship cleanup
  • MCP-compliant interface

use cases of Graph Memory RAG MCP Server?

  1. Storing and retrieving contextual information for AI applications.
  2. Managing complex relationships between data entities in research projects.
  3. Facilitating knowledge representation in intelligent systems.

FAQ from Graph Memory RAG MCP Server?

  • What is the purpose of the Graph Memory RAG MCP Server?

It is designed to provide a structured way for AI agents to manage and retrieve contextual information using graph-based storage.

  • How do I install the server?

You can install it by running npm install in your terminal.

  • Can I contribute to the project?

Yes! Contributions are welcome, and you can open issues or submit pull requests for improvements.

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