Neo4j Agent Memory MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NEO4J_URI | Yes | Neo4j database URI (e.g., bolt://localhost:7687) | |
| NEO4J_DATABASE | No | Neo4j database name (optional) - For Neo4j Enterprise with multiple databases | neo4j |
| NEO4J_PASSWORD | Yes | Neo4j password | |
| NEO4J_USERNAME | Yes | Neo4j username |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_memoriesC | Search and retrieve memories from the knowledge graph |
| create_memoryA | Create a new memory in the knowledge graph. Consider that the memory might already exist, so Search → Create → Connect (its important to try and connect memories) |
| create_connectionC | Create a connection between two memories (its good to have connected memories) |
| update_memoryC | Update properties of an existing memory such as adding more detail or make a change when you find out something new |
| update_connectionC | Update properties of an existing connection between memories |
| delete_memoryA | Delete a memory and all its connections (use with caution - this permanently removes the memory and all its connections) |
| delete_connectionA | Delete a specific connection between two memories (use with caution - this permanently removes the relationship) |
| list_memory_labelsA | List all unique memory labels currently in use with their counts (useful for getting an overview of the knowledge graph) |
| get_guidanceB | Get help on using the memory tools effectively |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose: create/delete/update operations for memories and connections, plus search, list, and guidance tools. There is no overlap in functionality, making it easy for an agent to select the correct tool.
All tool names follow a consistent verb_noun pattern (e.g., create_memory, delete_connection, update_memory). The naming is uniform and predictable, with no deviations in style or convention.
With 9 tools, the server is well-scoped for managing a knowledge graph, covering essential CRUD operations for memories and connections, plus auxiliary functions like search and guidance. Each tool earns its place without bloat.
The toolset provides complete lifecycle coverage for memories and connections (create, read via search, update, delete), along with utilities for listing labels and getting guidance. There are no obvious gaps for the domain of memory management in a knowledge graph.