What can you do with this server?

The Knowledge Graph Memory Server is a persistent memory system using a local knowledge graph for storing information and learning from errors. Core Capabilities: * Entity Management: Create, delete, and manage entities (nodes) with unique names, types, and observations * Relation Management: Establish and remove directed relationships between entities in active voice * Observation Handling: Add or remove atomic facts attached to specific entities * Graph Exploration: Read the entire graph, search by query across names/types/observations, or retrieve specific nodes by name * Lesson System: Create and manage structured lessons for error patterns and solutions, including success rate tracking and metadata * Error Recommendations: Find similar errors and recommend relevant lessons based on context * File Management: Automatically split files (memory.json and lesson.json) to maintain performance * Integration: Seamlessly integrate with Cursor MCP client and Claude Desktop for persistent memory across interactions

How do I use Knowledge Graph Memory Server?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Knowledge Graph Memory Server remember that I prefer morning meetings and speak Spanish" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

en es ja ko zh

Knowledge Graph Memory Server

by T1nker-1220

Overview Schema Source Related Servers Discussions Admin

JavaScript

Hybrid

Knowledge Graph Memory Server

A basic implementation of persistent memory using a local knowledge graph. This lets Claude remember information about the user across chats and learn from past errors through a lesson system.

Core Concepts

Entities

Entities are the primary nodes in the knowledge graph. Each entity has:

A unique name (identifier)
An entity type (e.g., "person", "organization", "event")
A list of observations

Example:

{
  "name": "John_Smith",
  "entityType": "person",
  "observations": ["Speaks fluent Spanish"]
}

Relations

Relations define directed connections between entities. They are always stored in active voice and describe how entities interact or relate to each other.

Example:

{
  "from": "John_Smith",
  "to": "Anthropic",
  "relationType": "works_at"
}

Observations

Observations are discrete pieces of information about an entity. They are:

Stored as strings
Attached to specific entities
Can be added or removed independently
Should be atomic (one fact per observation)

Example:

{
  "entityName": "John_Smith",
  "observations": [
    "Speaks fluent Spanish",
    "Graduated in 2019",
    "Prefers morning meetings"
  ]
}

Lessons

Lessons are special entities that capture knowledge about errors and their solutions. Each lesson has:

A unique name (identifier)
Error pattern information (type, message, context)
Solution steps and verification
Success rate tracking
Environmental context
Metadata (severity, timestamps, frequency)

Example:

{
  "name": "NPM_VERSION_MISMATCH_01",
  "entityType": "lesson",
  "observations": [
    "Error occurs when using incompatible package versions",
    "Affects Windows environments specifically",
    "Resolution requires version pinning"
  ],
  "errorPattern": {
    "type": "dependency",
    "message": "Cannot find package @shadcn/ui",
    "context": "package installation"
  },
  "metadata": {
    "severity": "high",
    "environment": {
      "os": "windows",
      "nodeVersion": "18.x"
    },
    "createdAt": "2025-02-13T13:21:58.523Z",
    "updatedAt": "2025-02-13T13:22:21.336Z",
    "frequency": 1,
    "successRate": 1.0
  },
  "verificationSteps": [
    {
      "command": "pnpm add shadcn@latest",
      "expectedOutput": "Successfully installed shadcn",
      "successIndicators": ["added shadcn"]
    }
  ]
}

Related MCP server: Knowledge Graph Memory Server

API

Tools

create_entities
- Create multiple new entities in the knowledge graph
- Input: entities (array of objects)
  - Each object contains:
    - name (string): Entity identifier
    - entityType (string): Type classification
    - observations (string[]): Associated observations
- Ignores entities with existing names
create_relations
- Create multiple new relations between entities
- Input: relations (array of objects)
  - Each object contains:
    - from (string): Source entity name
    - to (string): Target entity name
    - relationType (string): Relationship type in active voice
- Skips duplicate relations
add_observations
- Add new observations to existing entities
- Input: observations (array of objects)
  - Each object contains:
    - entityName (string): Target entity
    - contents (string[]): New observations to add
- Returns added observations per entity
- Fails if entity doesn't exist
delete_entities
- Remove entities and their relations
- Input: entityNames (string[])
- Cascading deletion of associated relations
- Silent operation if entity doesn't exist
delete_observations
- Remove specific observations from entities
- Input: deletions (array of objects)
  - Each object contains:
    - entityName (string): Target entity
    - observations (string[]): Observations to remove
- Silent operation if observation doesn't exist
delete_relations
- Remove specific relations from the graph
- Input: relations (array of objects)
  - Each object contains:
    - from (string): Source entity name
    - to (string): Target entity name
    - relationType (string): Relationship type
- Silent operation if relation doesn't exist
read_graph
- Read the entire knowledge graph
- No input required
- Returns complete graph structure with all entities and relations
search_nodes
- Search for nodes based on query
- Input: query (string)
- Searches across:
  - Entity names
  - Entity types
  - Observation content
- Returns matching entities and their relations
open_nodes
- Retrieve specific nodes by name
- Input: names (string[])
- Returns:
  - Requested entities
  - Relations between requested entities
- Silently skips non-existent nodes

Lesson Management Tools

create_lesson
- Create a new lesson from an error and its solution
- Input: lesson (object)
  - Contains:
    - name (string): Unique identifier
    - entityType (string): Must be "lesson"
    - observations (string[]): Notes about the error and solution
    - errorPattern (object): Error details
      - type (string): Category of error
      - message (string): Error message
      - context (string): Where error occurred
      - stackTrace (string, optional): Stack trace
    - metadata (object): Additional information
      - severity ("low" | "medium" | "high" | "critical")
      - environment (object): System details
      - frequency (number): Times encountered
      - successRate (number): Solution success rate
    - verificationSteps (array): Solution verification
      - Each step contains:
        command (string): Action to take
        expectedOutput (string): Expected result
        successIndicators (string[]): Success markers
- Automatically initializes metadata timestamps
- Validates all required fields
find_similar_errors
- Find similar errors and their solutions
- Input: errorPattern (object)
  - Contains:
    - type (string): Error category
    - message (string): Error message
    - context (string): Error context
- Returns matching lessons sorted by success rate
- Uses fuzzy matching for error messages
update_lesson_success
- Update success tracking for a lesson
- Input:
  - lessonName (string): Lesson to update
  - success (boolean): Whether solution worked
- Updates:
  - Success rate (weighted average)
  - Frequency counter
  - Last update timestamp
get_lesson_recommendations
- Get relevant lessons for current context
- Input: context (string)
- Searches across:
  - Error type
  - Error message
  - Error context
  - Lesson observations
- Returns lessons sorted by:
  - Context relevance
  - Success rate
- Includes full solution details

File Management

The server now handles two types of files:

memory.json: Stores basic entities and relations
lesson.json: Stores lesson entities with error patterns

Files are automatically split if they exceed 1000 lines to maintain performance.

Cursor MCP Client Setup

To integrate this memory server with Cursor MCP client, follow these steps:

Clone the Repository:

git clone [repository-url]
cd [repository-name]

Install Dependencies:

pnpm install

Build the Project:

pnpm build

Configure the Server:

Locate the full path to the built server file: /path/to/the/dist/index.js
Start the server using Node.js: node /path/to/the/dist/index.js

Activate in Cursor:

Use the keyboard shortcut Ctrl+Shift+P
Type "reload window" and select it
Wait a few seconds for the MCP server to activate
Select the stdio type when prompted

The memory server should now be integrated with your Cursor MCP client and ready to use.

Usage with Claude Desktop

Setup

Add this to your claude_desktop_config.json:

Docker

{
  "mcpServers": {
    "memory": {
      "command": "docker",
      "args": ["run", "-i", "-v", "claude-memory:/app/dist", "--rm", "mcp/memory"]
    }
  }
}

NPX

{
  "mcpServers": {
    "memory": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-memory"
      ]
    }
  }
}

NPX with custom setting

The server can be configured using the following environment variables:

{
  "mcpServers": {
    "memory": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-memory"
      ],
      "env": {
        "MEMORY_FILE_PATH": "/path/to/custom/memory.json"
      }
    }
  }
}

MEMORY_FILE_PATH: Path to the memory storage JSON file (default: memory.json in the server directory)

System Prompt

The prompt for utilizing memory depends on the use case. Changing the prompt will help the model determine the frequency and types of memories created.

Here is an example prompt for chat personalization. You could use this prompt in the "Custom Instructions" field of a Claude.ai Project.

Follow these steps for each interaction:

1. User Identification:
   - You should assume that you are interacting with default_user
   - If you have not identified default_user, proactively try to do so.

2. Memory Retrieval:
   - Always begin your chat by saying only "Remembering..." and retrieve all relevant information from your knowledge graph
   - Always refer to your knowledge graph as your "memory"

3. Memory
   - While conversing with the user, be attentive to any new information that falls into these categories:
     a) Basic Identity (age, gender, location, job title, education level, etc.)
     b) Behaviors (interests, habits, etc.)
     c) Preferences (communication style, preferred language, etc.)
     d) Goals (goals, targets, aspirations, etc.)
     e) Relationships (personal and professional relationships up to 3 degrees of separation)

4. Memory Update:
   - If any new information was gathered during the interaction, update your memory as follows:
     a) Create entities for recurring organizations, people, and significant events
     b) Connect them to the current entities using relations
     b) Store facts about them as observations

Building

Docker:

docker build -t mcp/memory -f src/memory/Dockerfile .

License

This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.

New Tools

create_lesson
- Create a new lesson from an error and its solution
- Input: lesson (object)
  - Contains error pattern, solution steps, and metadata
  - Automatically tracks creation time and updates
  - Verifies solution steps are complete
find_similar_errors
- Find similar errors and their solutions
- Input: errorPattern (object)
  - Contains error type, message, and context
  - Returns matching lessons sorted by success rate
  - Includes related solutions and verification steps
update_lesson_success
- Update success tracking for a lesson
- Input:
  - lessonName (string): Lesson to update
  - success (boolean): Whether solution worked
- Updates success rate and frequency metrics
get_lesson_recommendations
- Get relevant lessons for current context
- Input: context (string)
- Returns lessons sorted by relevance and success rate
- Includes full solution details and verification steps

BIG CREDITS TO THE OWNER OF THIS REPO FOR THE BASE CODE I ENHANCED IT WITH LESSONS AND FILE MANAGEMENT

Big thanks! https://github.com/modelcontextprotocol/servers jerome3o-anthropic https://github.com/modelcontextprotocol/servers/tree/main/src/memory

Available Tools

13 tools

add_observationsB

Add new observations to existing entities in the knowledge graph

ParametersJSON Schema

Name	Required	Description	Default
`observations`	Yes

TDQS

B3.3/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description must disclose behavioral traits on its own. It only states that it adds observations, without detailing whether observations are appended or replaced, what happens if the entity does not exist (e.g., error or auto-creation), or any other side effects. The tool is clearly a write operation, but critical safety and behavior information is missing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence that immediately conveys the tool's core function. There is no fluff or redundant phrasing, and the primary verb and object are front-loaded. It earns a high score for efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that there are no annotations and no output schema, the description must provide comprehensive context on its own. However, it only gives a high-level statement and lacks necessary details about input requirements, validation, error handling, or effect on existing data. This leaves significant gaps in the agent's understanding of the tool's full behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has zero coverage for the top-level parameter, and the description does not compensate by explaining the parameter structure. Although the nested schema properties describe entityName and contents, the description adds no semantic value beyond the schema, and the agent must rely solely on the schema to understand that observations is an array of objects with those fields. This is insufficient given the low schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb 'Add' and identifies the resource 'observations' and the target 'existing entities' within the knowledge graph. This clearly distinguishes it from sibling tools like create_entities (which creates entities) and delete_observations (which removes observations), making the tool's purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies that this tool is used when adding observations to existing entities, but it does not explicitly state when to use it over alternatives or provide any comparison with sibling tools. There is no mention of constraints such as 'only for existing entities' or guidance about creating entities first. Thus, the usage context is implied rather than explicitly outlined.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

create_entitiesB

Create multiple new entities in the knowledge graph

ParametersJSON Schema

Name	Required	Description	Default
`entities`	Yes

TDQS

B3.1/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that it creates entities, but does not mention potential duplicate handling, overwrite behavior, validation rules, or whether the operation is atomic—information an agent would need for a mutating tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence that communicates the core purpose with no filler. It is appropriately concise for a simple tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of annotations, an output schema, and limited schema coverage, the description should offer more context about usage, side effects, or return behavior. It does not, leaving significant gaps for an agent to make assumptions about how the tool behaves.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema's top-level 'entities' parameter has no description (coverage 0%), and the tool description does not explain what constitutes an entity (name, type, observations). The description adds no value beyond the bare phrase 'multiple new entities,' failing to compensate for the schema gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Create') and a specific resource ('multiple new entities in the knowledge graph'), clearly distinguishing this from sibling tools like create_relations and add_observations. It is explicit and unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It does not mention create_relations, add_observations, or any exclusions, leaving the agent to infer selection based solely on the name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

create_lessonC

Create a new lesson from an error and its solution

ParametersJSON Schema

Name	Required	Description	Default
`lesson`	Yes

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Create' implies a write/mutation operation, the description doesn't address critical aspects: permission requirements, whether creation is idempotent or can overwrite existing lessons, what happens on failure, or what the response contains. For a complex creation tool with nested objects, this leaves significant behavioral uncertainty.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, focused sentence with zero wasted words. It front-loads the core action ('Create a new lesson') and immediately specifies the source material. Every word contributes essential information, making it optimally concise for its purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a creation tool with complex nested parameters (1 parameter with 6+ sub-properties), no annotations, and no output schema, the description is insufficient. It doesn't explain the creation workflow, success/failure behavior, return values, or how the input structure relates to the described 'error and its solution' concept. The agent must rely entirely on the raw schema without contextual guidance.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description mentions the parameter's purpose ('from an error and its solution'), which provides high-level context for the 'lesson' object. However, with 0% schema description coverage and 1 complex nested parameter containing multiple sub-properties, the description doesn't explain the structure, required fields beyond what the schema shows, or how 'error' and 'solution' map to specific properties like 'errorPattern' and 'verificationSteps'. It adds minimal value beyond the schema's structural definition.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Create' and the resource 'new lesson', specifying it's created 'from an error and its solution'. This distinguishes it from generic creation tools like 'create_entities' by focusing on error-based lesson creation. However, it doesn't explicitly differentiate from 'update_lesson_success' which might also involve lesson modifications.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'create_entities' (for general entity creation) or 'update_lesson_success' (for modifying existing lessons). It mentions the source material ('from an error and its solution') but doesn't specify prerequisites, constraints, or appropriate contexts for invocation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

create_relationsB

Create multiple new relations between entities in the knowledge graph. Relations should be in active voice

ParametersJSON Schema

Name	Required	Description	Default
`relations`	Yes

TDQS

B3.3/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'create' and offers an active-voice guideline, but does not mention idempotency, validation of from/to entities, behavior on duplicates, or error handling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with a brief second clause. Every word earns its place and the main purpose is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations or output schema, the description is too sparse. It omits critical details such as whether from/to entities must already exist, how duplicates are handled, and whether creation is atomic for the batch.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% at the top level, so the description needed to compensate. It adds the active-voice guideline but does not explain the structure of the relations array or the meaning of from/to/relationType, which the schema already partially covers.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (create), the object (multiple new relations), and the context (knowledge graph). It distinguishes from siblings like delete_relations and create_entities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies this tool is for creating relations, but it does not explicitly state when to use it versus alternatives or mention any prerequisites. The active-voice guideline is a style note, not usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

delete_entitiesA

Delete multiple entities and their associated relations from the knowledge graph

ParametersJSON Schema

Name	Required	Description	Default
`entityNames`	Yes	An array of entity names to delete

TDQS

A3.5/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It does disclose that associated relations are deleted as part of the operation, which is a useful behavioral detail. However, it does not mention irreversibility, permissions, or whether observations are affected, leaving gaps in transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence that front-loads the action and scope with no unnecessary words. Every word contributes to understanding the tool's purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter destructive tool with no output schema, the description conveys the core purpose but omits behavioral details such as error handling, atomicity, and return values. Given the lack of annotations, it is moderately complete but has room for improvement.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% coverage of the parameter 'entityNames' with a description, so the baseline is 3. The tool description does not add any additional parameter semantics beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool deletes multiple entities and their associated relations, using a specific verb ('Delete') and resource ('entities' and 'relations'). It distinguishes itself from sibling tools like delete_relations, which only handle relations, and delete_observations, which handles observations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives such as delete_relations or delete_observations. It does not state any exclusions, prerequisites, or scenarios where another tool would be more appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

delete_observationsB

Delete specific observations from entities in the knowledge graph

ParametersJSON Schema

Name	Required	Description	Default
`deletions`	Yes

TDQS

B3.1/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must disclose behavioral traits. It only states the action without mentioning permanence, side effects, required permissions, or return format. As a mutation tool, this is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that directly conveys the core action, with no unnecessary words. It is well-structured and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has a non-trivial parameter schema and no output schema or annotations. The description is too minimal to fully inform usage, lacking details on how to specify deletions and what to expect in response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description does not explain the 'deletions' parameter structure. Schema coverage is 0% for the top-level parameter, and the description adds no semantic meaning beyond the schema's nested field descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the function: deleting specific observations from entities in a knowledge graph. It distinguishes itself from sibling tools like delete_entities and add_observations by specifying the granularity ('specific observations').

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives such as delete_entities or when not to use it. The description lacks any context or conditions for usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

delete_relationsA

Delete multiple relations from the knowledge graph

ParametersJSON Schema

Name	Required	Description	Default
`relations`	Yes	An array of relations to delete

TDQS

A3.5/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must convey behavioral traits, but it only says 'Delete' without mentioning consequences such as irreversibility, partial failure handling, or permissions. For a mutating operation, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that is direct and front-loaded. Every word earns its place, and there is no redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple with one well-specified parameter and no output schema, so the core purpose is covered. However, behavioral details like error handling, atomicity, or effects on related entities are absent, which leaves some ambiguity for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema fully describes the 'relations' parameter and its nested properties (from, to, relationType), so the description adds little beyond what is already structured. The phrase 'multiple' aligns with the array type but does not provide extra meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific action ('Delete') on a specific resource ('relations'), and the plural 'multiple relations' distinguishes this from sibling tools like delete_entities and delete_observations. It is concise and unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for deleting one or more relations, but it does not explicitly state when to prefer this over alternatives, nor does it mention any exclusions or prerequisites. It provides only minimal contextual guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

find_similar_errorsC

Find similar errors and their solutions in the knowledge graph

ParametersJSON Schema

Name	Required	Description	Default
`errorPattern`	Yes

TDQS

C2.8/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'find similar errors and their solutions' but doesn't clarify what 'similar' means (e.g., based on pattern matching, semantic similarity), how results are returned, or any limitations like rate limits or authentication needs. This leaves significant gaps in understanding the tool's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to grasp quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (1 parameter with nested objects, no annotations, no output schema), the description is insufficient. It doesn't explain the input structure, output format, or behavioral details needed for effective use. For a tool that likely involves complex pattern matching and result retrieval, more context is required.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the schema provides no parameter descriptions. The tool description mentions 'errorPattern' implicitly but doesn't explain what it should contain or how it's used to find similar errors. It fails to compensate for the lack of schema documentation, leaving parameters largely undefined.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Find') and target ('similar errors and their solutions in the knowledge graph'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'search_nodes' or 'get_lesson_recommendations', which might also involve searching or retrieving information from the knowledge graph.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'search_nodes' and 'get_lesson_recommendations' that might overlap in functionality, there's no indication of specific use cases, prerequisites, or exclusions for this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_lesson_recommendationsC

Get relevant lessons based on the current context

ParametersJSON Schema

Name	Required	Description	Default
`context`	Yes	The current context to find relevant lessons for

TDQS

C2.6/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It states the tool 'Get[s] relevant lessons' but doesn't disclose behavioral traits like whether it's read-only, requires authentication, has rate limits, returns structured data, or handles errors. For a tool with no annotations, this leaves significant gaps in understanding its operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core purpose. It avoids unnecessary words, but could be more structured by including key details like usage context or output format. Overall, it's appropriately sized with minimal waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (inference-based recommendations), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what 'relevant' entails, how lessons are selected, the return format, or error handling. For a recommendation tool with no structured support, more detail is needed to guide the agent effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with one parameter 'context' documented as 'The current context to find relevant lessons for'. The description adds no additional meaning beyond this, as it only repeats 'based on the current context'. With high schema coverage, the baseline score of 3 is appropriate, as the schema already provides adequate parameter details.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get relevant lessons based on the current context' clearly states the verb 'Get' and resource 'lessons', but it's vague about what 'relevant' means and doesn't differentiate from sibling tools like 'search_nodes' or 'find_similar_errors'. It specifies the action but lacks precision in scope or method.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives such as 'search_nodes' or 'find_similar_errors'. The description implies usage based on 'current context' but doesn't specify scenarios, prerequisites, or exclusions, leaving the agent to guess when this is the appropriate choice.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

open_nodesC

Open specific nodes in the knowledge graph by their names

ParametersJSON Schema

Name	Required	Description	Default
`names`	Yes	An array of entity names to retrieve

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden of disclosing behavior. It only says 'open', which implies read-only retrieval, but does not explicitly state that it is non-mutating, what it returns, or how missing names are handled. This leaves significant ambiguity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficiently worded sentence that directly states the action and resource. It contains no filler or redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has no output schema and the description does not clarify what 'open' returns (e.g., node attributes, observations, relations). For an agent to invoke the tool and interpret results correctly, this missing information is a notable gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% coverage, already describing 'names' as 'An array of entity names to retrieve'. The tool description merely restates 'by their names', adding no extra semantic detail beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses the specific verb 'Open' and identifies the resource 'nodes in the knowledge graph', scoped by 'names', making it clear this is a direct retrieval by exact names. It implicitly differentiates from search_nodes (searching) and read_graph (full graph), but does not explicitly name alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given on when to use this tool versus siblings. The description does not state that it should be used when exact node names are known, nor does it exclude using search_nodes for lookup or read_graph for broader context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

read_graphB

Read the entire knowledge graph

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

B3.1/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must carry the full burden of behavioral disclosure, but it only states that the graph is read. It does not mention that the operation is read-only, whether it requires permissions, or that the response may be very large. The word 'read' implies non-destructive behavior, but no details are given.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence that directly states the tool's purpose with no redundancy. It is well-structured and every word contributes to the meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description should explain what reading the graph returns or any caveats (e.g., large payloads). It does not, and it also fails to differentiate this tool from search_nodes for partial reads. The tool is simple, but the description is still incomplete for an agent to use it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters and the schema is empty, so there is nothing to document. The baseline for zero parameters is 4, and the description correctly indicates that no inputs are needed, without adding unnecessary detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb 'read' and identifies the resource 'the entire knowledge graph,' clearly distinguishing it from sibling tools that create or delete entities. However, it is brief and doesn't elaborate on the output format or how it differs from export_to_obsidian, so it falls short of a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no explicit guidance on when to use this tool over alternatives like search_nodes or open_nodes. It is only implied that this is for reading the whole graph, with no mention of filtering or use cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search_nodesC

Search for nodes in the knowledge graph based on a query

ParametersJSON Schema

Name	Required	Description	Default
`query`	Yes	The search query to match against entity names, types, and observation content

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. It describes the action as 'search' but does not disclose key behaviors such as case sensitivity, partial matching, result limits, ordering, or whether it searches across all entity fields or just specific ones.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no wasted words, but it is vague and lacks structure. It could be improved by adding brief details or examples without increasing length significantly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter tool without an output schema, the description is minimally adequate. However, given the presence of sibling tools with overlapping functionality, more context (e.g., search scope, result format) would make it complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema covers 100% of the parameter with a description that explains what the query matches against. The tool description restates 'based on a query' but adds no additional semantics beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool searches for nodes in the knowledge graph based on a query, which is specific enough to distinguish from siblings like 'traverse_graph' or 'query_by_time'. However, it could be more precise (e.g., specifying it's a full-text search).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives (e.g., 'query_by_time', 'traverse_graph', 'read_graph'). No exclusions or context for selection are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

update_lesson_successC

Update the success rate of a lesson after applying its solution

ParametersJSON Schema

Name	Required	Description	Default
`lessonName`	Yes	Name of the lesson to update
`success`	Yes	Whether the solution was successful

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'Update' which implies a mutation, but fails to specify permissions needed, whether changes are reversible, rate limits, or response format. This leaves significant gaps for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, making it easy to understand quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's mutation nature, lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like error handling, return values, or integration with sibling tools, leaving the agent with insufficient context for safe and effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 100%, so the input schema already documents both parameters ('lessonName' and 'success') adequately. The description adds minimal value by implying the context ('after applying its solution') but doesn't provide additional syntax or format details beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Update') and resource ('success rate of a lesson') with context ('after applying its solution'), making the purpose understandable. However, it doesn't explicitly differentiate this tool from sibling tools like 'create_lesson' or 'get_lesson_recommendations' in terms of when to update versus create or retrieve.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides minimal guidance by implying usage 'after applying its solution,' but it lacks explicit when-to-use rules, alternatives (e.g., vs. 'create_lesson' for initial setup), or prerequisites. No clear boundaries or comparisons to sibling tools are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

13 tool updatesAug 18, 2025
- First observedadd_observations
- First observedcreate_entities
- First observedcreate_lesson
- First observedcreate_relations
- First observeddelete_entities
- First observeddelete_observations
- First observeddelete_relations
- First observedfind_similar_errors
- First observedget_lesson_recommendations
- First observedopen_nodes
- First observedread_graph
- First observedsearch_nodes
- First observedupdate_lesson_success

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.3/5.0

Scored 2026-04-18 11:40 across 13 tools

Disambiguation4/5

Most tools have distinct purposes, but some overlap exists: 'open_nodes' and 'search_nodes' both involve accessing nodes, which could cause confusion. However, descriptions clarify that 'open_nodes' targets specific names while 'search_nodes' uses queries, reducing ambiguity. Other tools like 'add_observations' vs. 'create_entities' are clearly differentiated.

Naming Consistency5/5

Tool names follow a consistent verb_noun pattern throughout, such as 'add_observations', 'create_entities', and 'delete_relations'. All tools use snake_case and clear verbs, making them predictable and easy to understand. There are no deviations in naming conventions.

Tool Count5/5

With 13 tools, the count is well-scoped for a knowledge graph memory server, covering operations like CRUD for entities, relations, observations, and lessons. Each tool appears to serve a specific function without redundancy, fitting the domain's complexity appropriately.

Completeness4/5

The tool set provides comprehensive coverage for knowledge graph management, including creation, reading, updating, and deletion of entities, relations, observations, and lessons. A minor gap is the lack of an 'update_entities' or 'update_relations' tool for modifying existing content, but agents can work around this by deleting and recreating. Core workflows are well-supported.

Maintenance

ActivityInactive

ResponsivenessUnresponsive

Resources

Need Help?

Reddit Discussion

Related Servers

Related MCP Connectors

ContextaOAuth
cc.contexta
Persistent memory and knowledge graph for AI assistants — keyword + vector + graph search.
Knowledge & Memory RAG Systems Vector Databases
2
Penfield Memory AOAuth
io.github.penfieldlabs
Persistent memory and knowledge graphs for AI agents. Hybrid search, context checkpoints, and more.
Knowledge & Memory RAG Systems Vector Databases
1726
meminal
ai.meminal
Memory for deep conversational context across any platform
Knowledge & Memory Autonomous Agents Communication
2
Tycana
io.github.tycana
Gives your AI assistant persistent memory and intelligence about your work patterns.
Knowledge & Memory Autonomous Agents Developer Tools
2

Related MCP Servers

Loc Knowledge Graph Memory
Knowledge & Memory Autonomous Agents
bughide010
A
license
Not graded
quality
D
maintenance
Enables Claude to remember information about users across chats using a persistent local knowledge graph that stores entities, relationships, and observations.
Updated 10 months ago (2025-12-08 15:17 UTC)
114,646 npm
-
Knowledge Graph Memory Server
Knowledge & Memory RAG Systems
guinacio
A
license
Not graded
quality
C
maintenance
A persistent memory system using a local knowledge graph that enables Claude to remember information about users across chats, with advanced search, graph traversal, and filtering capabilities for entities, relations, and observations.
Updated 7 months ago (2026-02-21 14:19 UTC)
MIT
AGI MCP Server
Knowledge & Memory Vector Databases RAG Systems
randyandrade
F
license
B
quality
D
maintenance
Enables persistent memory for AI systems by providing tools for episodic, semantic, and procedural data storage through a vector-and-graph-enhanced database. It allows models to maintain long-term continuity using similarity search, thematic clustering, and identity tracking.
Updated a year ago (2025-06-29 02:45 UTC)
24
1
-
adaptive-memory-graph
Knowledge & Memory Search
raskolnikovdd
A
license
Not graded
quality
D
maintenance
Enables persistent, intelligent memory across sessions using a weighted, interconnected graph that evolves through conversation.
Updated 6 months ago (2026-03-11 18:48 UTC)
22 PyPI
MIT

Knowledge Graph Memory Server

Core Concepts

Entities

Relations

Observations

Lessons

API

Tools

Lesson Management Tools

File Management

Cursor MCP Client Setup

Usage with Claude Desktop

Setup

Docker

NPX

NPX with custom setting

System Prompt

Building

License

New Tools

BIG CREDITS TO THE OWNER OF THIS REPO FOR THE BASE CODE I ENHANCED IT WITH LESSONS AND FILE MANAGEMENT

Available Tools

Tool Schema Changelog

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches