Graph Memory RAG MCP Server
@lecharles
A Model Context Protocol (MCP) server implementation for graph-based memory storage with RAG capabilities
概要
What is Graph Memory RCP MCP Server?
Graph Memory RCP MCP Server is a Model Context Protocol (MCP) server that provides graph-based memory storage. It allows AI agents to store and retrieve information in a graph structure, maintaining context and relationships between pieces of information. It is intended for developers integrating graph memory into AI agent workflows.
How to use Graph Memory RCP MCP Server?
Install dependencies with npm install and start the server with node app.js. The server exposes tools for creating entities and relationships, querying entities and relationships by type, and deleting entities with cascading relationship cleanup.
Key features of Graph Memory RCP MCP Server
- In-memory graph database storage
- Entity creation and management
- Relationship creation between entities
- Query capabilities for entities and relationships
- Delete operations with cascading relationship cleanup
- MCP-compliant interface
Use cases of Graph Memory RCP MCP Server
- AI agents maintaining persistent context across conversations
- Storing and retrieving structured knowledge with entity-relationship links
- Managing dynamic memory graphs where nodes and edges can be added or removed
- Experimenting with graph-based memory in MCP‑enabled applications
FAQ from Graph Memory RCP MCP Server
What dependencies does Graph Memory RCP MCP Server require?
It requires @modelcontextprotocol/sdk: ^1.0.3 and zod: ^3.22.4.
How is data stored in Graph Memory RCP MCP Server?
Data is stored entirely in‑memory using two maps: one for entities and one for relationships. There is no persistent storage.
What operations can I perform with the server’s tools?
You can create entities (with name, type, and observations), create relationships between entities, query entities and relationships by type, and delete entities (which also removes their associated relationships).
Does Graph Memory RCP MCP Server use authentication or transport layers?
The README does not describe any authentication or transport configuration; it uses the standard MCP interface.
What are the limits of the in‑memory storage?
The README does not specify explicit limits. Since storage is in‑memory, capacity is bounded by available system memory and data is lost when the server stops.