Skip to main content
Glama
deenesjakoruzh
scarletkc

Perenna

by scarletkc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Perenna

Python PyPI CI Codecov CodeRabbit Pull Request Reviews License Ask DeepWiki

perenna MCP server

AI 에이전트를 위한 가볍고 Git 기반의 영구 메모리입니다. Claude Code, Codex, ChatGPT, Cursor 및 기타 MCP 클라이언트는 공급업체 계정이나 대화 기록을 공유하지 않고도 지속적인 메모리를 공유할 수 있습니다.

  • 메모리 읽기, 쓰기, 삭제를 위한 별도의 MCP 도구

  • 로컬 stdio 및 단일 사용자 OAuth 보호 Streamable HTTP 전송

  • 독립적인 Git 저장소에 저장된 사람이 읽을 수 있는 Markdown

  • Git에서 항상 재구축할 수 있는 로컬 Vexor 검색 인덱스

  • 여러 로컬 에이전트 프로세스를 위한 프로세스 간 잠금

Perenna가 필요한 이유는?

메모리는 여러분을 따라야 하지, 우연히 사용 중인 에이전트를 따라가면 안 됩니다.

Claude Code, Codex, Cursor, ChatGPT는 메모리를 각각 분리된 사일로에 보관합니다. 에이전트를 전환하면 메모리가 사라집니다. 기기를 변경해도 로컬 메모리는 그대로 남아 있습니다.

Perenna는 이들에게 하나의 공유된 Git 기반 메모리를 제공합니다. 로컬 에이전트와 ChatGPT는 동일한 자체 호스팅 Perenna 서비스에 연결할 수 있으며, 모든 지속 메모리는 직접 검사, 편집, 버전 관리 및 백업할 수 있는 일반 Markdown으로 유지됩니다.

Mem0의 자체 호스팅 스택은 훨씬 더 무거운 반면, 호스팅형 Free Plan은 현재 고객 콘텐츠가 모델 학습 및 제품 개선에 사용될 수 있도록 허용합니다.

Perenna는 설계부터 다릅니다: 계정 없음, 독점 메모리 클라우드 없음, 락인 없음. 여러분이 제어하는 인프라의 Git 저장소에 있는 여러분의 메모리만 있을 뿐입니다.

Related MCP server: Hypermnesic

빠른 시작

AI 에이전트와 함께 설치

Claude Code, Codex, ChatGPT Desktop, Cursor 또는 터미널과 로컬 MCP 구성 액세스 권한이 있는 다른 코딩 에이전트에 다음을 붙여넣으세요:

Install Perenna and connect it to this AI agent as a local stdio MCP server.
Work through the complete setup autonomously.

Use these as the source of truth:
- https://github.com/scarletkc/Perenna/blob/main/docs/getting-started.md
- https://github.com/scarletkc/Perenna/blob/main/docs/guides/client-setup.md

1. Detect the operating system, shell, and current MCP client.
2. Check for Python 3.12 or newer, Git, and uv. Install uv in user scope if it
   is missing. If Python or Git needs administrator approval, give me the exact
   command and stop there.
3. Install Perenna with `uv tool install perenna`. If Perenna is already
   installed, upgrade it with `uv tool upgrade perenna`.
   For Codex, also run `perenna skill install --agent codex`. For Claude Code,
   run `perenna skill install --agent claude-code`. Do not replace an existing
   modified copy or remove unrelated installed skills.
4. Check the effective Vexor embedding provider configuration. Reuse a working
   `~/.vexor/config.json` or inherited environment configuration. If none is
   available, ask me to choose between a remote provider and local embeddings.
   Explain that a remote provider receives memory text and search queries. For
   a remote provider, keep the provider and model in Vexor configuration and
   supply its secret through `VEXOR_API_KEY` or the provider-specific environment
   variable. For local embeddings, install `perenna[local]` and configure the
   local model according to the Perenna configuration reference. Verify the
   selected provider with `uvx vexor doctor` using the same environment that
   the Perenna process will inherit.
5. Ask whether I want to synchronize Perenna with a private Git repository. If
   I do, ask me to provide or approve its URL, run
   `perenna sync setup <repository-url>`, and verify it with
   `perenna sync status`. Treat repository creation, remote replacement, and
   reconciling diverged history as separate choices that require my explicit
   approval.
6. Register `perenna mcp --source <stable-client-name>` using the client-specific
   method in the setup guide. Preserve unrelated MCP servers and settings. Use
   a stable source such as `claude-code`, `codex`, or `cursor` for this client.
   For another client, use its official instructions for adding a local stdio
   MCP server. Make sure the Perenna process inherits `VEXOR_CONFIG_JSON`,
   `VEXOR_API_KEY`, or any provider-specific key used in step 4. Report only
   whether a secret is present.
7. Verify `perenna --help` and the saved MCP configuration. Reload MCP servers
   and call `memory_read` with `action: "list"` when the client supports it. If
   a restart is required, tell me the single restart step.
8. Report the commands run, files changed, and verification results. Keep API
   keys out of tracked configuration files.

공식 출시 버전 설치

Perenna는 Python 3.12+, Git 및 uv가 필요합니다.

uv tool install perenna

로컬 클라이언트용 옵션 메모리 동작 스킬을 설치합니다:

perenna skill install --agent codex
# or
perenna skill install --agent claude-code

두 클라이언트 모두 스킬을 받아야 하는 경우 하나의 명령에서 --agent를 반복하세요. 구성 참조는 사용자 및 프로젝트 범위, 대상 위치 및 대체 보호 조치를 문서화합니다.

Codex 및 Claude Code는 대신 Perenna 저장소 마켓플레이스에서 결합된 스킬 및 MCP 연결을 설치할 수 있습니다. Plugin 설정 가이드를 따르고 클라이언트별로 하나의 설정 경로를 선택하세요.

Perenna는 작동하는 Vexor 임베딩 공급자가 필요합니다. 대화식 공급자 선택 및 구성을 위해 다음을 실행하세요:

uvx vexor init

Perenna는 자동으로 ~/.vexor/config.json을 재사용합니다. 프로세스 수준 구성을 사용할 때 MCP 서버가 호스트 환경에서 VEXOR_CONFIG_JSON과 VEXOR_API_KEY 또는 선택한 공급자의 키를 받는지 확인하세요. 원격 공급자는 메모리 텍스트와 검색 쿼리를 받습니다.

로컬 임베딩을 선택하는 경우 Perenna의 로컬 추가 기능도 설치하세요:

uv tool install "perenna[local]"

Vexor 공급자 구성은 원격 및 로컬 설치 범위를 다룹니다. MCP 클라이언트를 시작하는 환경에서 선택한 공급자를 다음으로 확인하세요:

uvx vexor doctor

MCP 클라이언트가 시작하도록 구성하세요:

perenna mcp --source <client-name>

Perenna는 다른 홈이 구성되지 않는 한 ~/.perenna/ 아래에 로컬 데이터를 생성합니다.

개인 Git 저장소를 통해 호환 가능한 기록을 가져오거나, 게시하거나, 빠르게 전달하려면 다음을 실행하세요:

perenna sync setup <repository-url>

개발을 위해 소스에서 설치

git clone https://github.com/scarletkc/Perenna.git
cd Perenna
uv tool install .

문서

문서 색인에서 시작하여 작업에 맞는 경로를 따라가세요:

라이선스

MIT

Available Tools

3 tools
memory_deleteA
Destructive

Delete exactly one committed memory by ID, expected title, and revision. The deletion removes it from current recall but remains recoverable from Git history.

ParametersJSON Schema
NameRequiredDescriptionDefault
memory_idYes
base_revisionYes
expected_titleYes

Output Schema

ParametersJSON Schema
NameRequiredDescription
actionYes
commitYes
memoryYes
changedYes
sync_statusYes
index_statusYes
recoverable_via_gitYes

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false. The description adds valuable non-obvious context: the deletion removes from recall but remains recoverable via Git history, and it deletes 'exactly one' memory. This goes beyond the annotations without contradicting them. It does not mention side effects like concurrency checks, but the added recoverability and scoping are meaningful.

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 one compact sentence that leads with the action and core constraints, then adds the recoverability detail. There is no fluff or repetition; every word earns its place.

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 destructive operation with three required parameters and an output schema, the description is thin. It omits behavior on mismatch (e.g., if expected_title or base_revision does not match), error semantics, or any guidance on when this tool should be chosen over siblings. The recoverability note is helpful (something the output schema won't reveal), but other important context is missing.

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 description must compensate. However, it only mentions parameters as 'ID, expected title, and revision' without explaining their purpose, format, or how they are used (e.g., what an expected title is for, what a base revision means, or how they act as safety checks). No examples or constraints are provided, leaving agents to infer semantics from names alone.

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 states a specific verb ('Delete'), resource ('one committed memory'), and identifies the parameters by role (ID, expected title, revision). It clearly distinguishes from siblings memory_read and memory_write by the action it performs.

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 does not provide explicit guidance on when to use this tool versus alternatives. It only implies deletion use case without mentioning conditions, prerequisites, or exclusions (e.g., 'use memory_read to view' or 'use memory_write to create'). No context is given for when a deletion is appropriate.

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

memory_readA
Read-onlyIdempotent

Read permanent memory. List returns stable memory IDs and titles, search returns bounded ranked candidate passages, and get returns one complete committed memory with its revision.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

Output Schema

ParametersJSON Schema
NameRequiredDescription

No output parameters

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, non-destructive, idempotent, and open-world behavior. The description adds useful context beyond annotations: search results are 'bounded ranked candidate passages,' list returns only IDs/titles, and get returns a 'complete committed memory with its revision.' No contradiction with annotations.

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 front-loads the core purpose and uses parallel clauses to describe each action without redundancy or filler. It is compact yet informative.

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

Completeness5/5

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

Given the tool's three modes and the existence of an output schema, the description is complete: it explains the behavior of each action and what kind of result to expect. Annotations cover safety and side-effect concerns, and sibling names make the read/write/delete division clear.

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 documents the action variants, required fields, and limit bounds through its oneOf structure and const values. The description does not add parameter-level detail such as query format or memory_id semantics, but with schema coverage effectively complete, the baseline 3 is appropriate.

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 states a specific verb and resource ('Read permanent memory') and enumerates three distinct modes—list, search, get—with their concrete outcomes. This distinguishes the tool from memory_write and memory_delete without relying on the name alone.

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

Usage Guidelines4/5

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

The description tells an agent what each mode returns, which is clear guidance for choosing list vs search vs get. It does not explicitly say 'use this instead of memory_write or memory_delete,' but 'Read' and the sibling names make the intended usage obvious.

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

memory_writeA
Destructive

Create or modify permanent memory. Summary is a stable one-line description of what a memory covers. Patch applies exact all-or-nothing edits; replace overwrites the complete summary and body. Existing memories require a current base revision.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

Output Schema

ParametersJSON Schema
NameRequiredDescription
actionYes
commitYes
memoryYes
changedYes
sync_statusYes
index_statusYes

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations (destructiveHint=true, readOnlyHint=false), the description discloses valuable behavioral details: patch is all-or-nothing, replace overwrites the complete summary/body, and existing memories require a current base revision, implying optimistic concurrency. This does not contradict any annotation.

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 three dense sentences with no filler. The purpose is front-loaded, and each sentence addresses a distinct aspect: overall behavior, summary semantics, and modifications semantics.

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

Completeness4/5

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

The description covers the key operational facts an agent needs: the three modes, the summary convention, patch atomicity, and the base-revision requirement. Since an output schema exists, return-value details are not needed here. A minor gap is not pointing agents to memory_read to retrieve the current base revision.

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 description adds meaning beyond the schema by defining summary as a 'stable one-line description', explaining the exact semantics of patch and replace, and mentioning the base revision requirement. This is useful context that the bare schema types do not convey, though title and project are left to the schema.

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 states a specific action ('Create or modify') on a clear resource ('permanent memory') and further differentiates the three operational modes: create, patch, and replace. This makes the tool unmistakably the write counterpart to memory_read and memory_delete.

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 provides internal guidance on when to use patch vs replace and notes the base-revision prerequisite for modifying existing memories. However, it does not explicitly mention memory_read or memory_delete or state when to prefer this tool over those siblings.

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.

  1. 2 tool updatesv0.1.1
    • Changedmemory_read5 fields changed
      • removedInput schema / additionalProperties
        Removed value: -false
      • addedInput schema / oneOf
        Added value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "action": {
+        "const": "list"
+      },
+      "project": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "action"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "action": {
+        "const": "search"
+      },
+      "limit": {
+        "maximum": 5,
+        "minimum": 1,
+        "type": "integer"
+      },
+      "project": {
+        "type": "string"
+      },
+      "query": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "action",
+      "query"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "action": {
+        "const": "get"
+      },
+      "memory_id": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "action",
+      "memory_id"
+    ],
+    "type": "object"
+  }
+]
      • removedInput schema / properties
        Removed value: -{
-  "action": {
-    "enum": [
-      "list",
-      "search",
-      "get"
-    ],
-    "type": "string"
-  },
-  "limit": {
-    "maximum": 5,
-    "minimum": 1,
-    "type": "integer"
-  },
-  "memory_id": {
-    "type": "string"
-  },
-  "project": {
-    "type": "string"
-  },
-  "query": {
-    "type": "string"
-  }
-}
      • removedInput schema / required
        Removed value: -[
-  "action"
-]
      • changedOutput schema / oneOf
        Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "action": {
-        "const": "list"
-      },
-      "memories": {
-        "items": {
-          "additionalProperties": false,
-          "properties": {
-            "memory_id": {
-              "type": "string"
-            },
-            "scope": {
-              "type": "string"
-            },
-            "summary": {
-              "type": "string"
-            },
-            "title": {
-              "type": "string"
-            }
-          },
-          "required": [
-            "memory_id",
-            "title",
-            "scope",
-            "summary"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "project": {
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "projects": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      }
-    },
-    "required": [
-      "action",
-      "project",
-      "memories",
-      "projects"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "action": {
-        "const": "search"
-      },
-      "limit": {
-        "maximum": 5,
-        "minimum": 1,
-        "type": "integer"
-      },
-      "matches": {
-        "items": {
-          "additionalProperties": false,
-          "properties": {
-            "memory_id": {
-              "type": "string"
-            },
-            "passages": {
-              "items": {
-                "additionalProperties": false,
-                "properties": {
-                  "end_char": {
-                    "minimum": 1,
-                    "type": "integer"
-                  },
-                  "start_char": {
-                    "minimum": 0,
-                    "type": "integer"
-                  },
-                  "text": {
-                    "type": "string"
-                  }
-                },
-                "required": [
-                  "text",
-                  "start_char",
-                  "end_char"
-                ],
-                "type": "object"
-              },
-              "minItems": 1,
-              "type": "array"
-            },
-            "rank": {
-              "minimum": 1,
-              "type": "integer"
-            },
-            "revision": {
-              "type": "string"
-            },
-            "scope": {
-              "type": "string"
-            },
-            "summary": {
-              "type": "string"
-            },
-            "title": {
-              "type": "string"
-            }
-          },
-          "required": [
-            "memory_id",
-            "title",
-            "scope",
-            "summary",
-            "revision",
-            "rank",
-            "passages"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "project": {
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "truncated": {
-        "type": "boolean"
-      }
-    },
-    "required": [
-      "action",
-      "project",
-      "limit",
-      "matches",
-      "truncated"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "action": {
-        "const": "get"
-      },
-      "memory": {
-        "additionalProperties": false,
-        "properties": {
-          "body": {
-            "type": "string"
-          },
-          "created_at": {
-            "type": "string"
-          },
-          "memory_id": {
-            "type": "string"
-          },
-          "revision": {
-            "type": "string"
-          },
-          "scope": {
-            "type": "string"
-          },
-          "source": {
-            "type": "string"
-          },
-          "summary": {
-            "type": "string"
-          },
-          "title": {
-            "type": "string"
-          },
-          "updated_at": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "memory_id",
-          "title",
-          "scope",
-          "summary",
-          "source",
-          "created_at",
-          "updated_at",
-          "revision",
-          "body"
-        ],
-        "type": "object"
-      }
-    },
-    "required": [
-      "action",
-      "memory"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "action": {
+        "const": "list"
+      },
+      "memories": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "memory_id": {
+              "type": "string"
+            },
+            "scope": {
+              "type": "string"
+            },
+            "summary": {
+              "type": "string"
+            },
+            "title": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "memory_id",
+            "title",
+            "scope",
+            "summary"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "project": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "projects": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "action",
+      "project",
+      "memories",
+      "projects"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "action": {
+        "const": "search"
+      },
+      "limit": {
+        "maximum": 5,
+        "minimum": 1,
+        "type": "integer"
+      },
+      "matches": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "memory_id": {
+              "type": "string"
+            },
+            "passages": {
+              "items": {
+                "additionalProperties": false,
+                "properties": {
+                  "end_char": {
+                    "minimum": 1,
+                    "type": "integer"
+                  },
+                  "start_char": {
+                    "minimum": 0,
+                    "type": "integer"
+                  },
+                  "text": {
+                    "type": "string"
+                  }
+                },
+                "required": [
+                  "text",
+                  "start_char",
+                  "end_char"
+                ],
+                "type": "object"
+              },
+              "minItems": 1,
+              "type": "array"
+            },
+            "rank": {
+              "minimum": 1,
+              "type": "integer"
+            },
+            "revision": {
+              "type": "string"
+            },
+            "scope": {
+              "type": "string"
+            },
+            "summary": {
+              "type": "string"
+            },
+            "title": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "memory_id",
+            "title",
+            "scope",
+            "summary",
+            "revision",
+            "rank",
+            "passages"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "project": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "truncated": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "action",
+      "project",
+      "limit",
+      "matches",
+      "truncated"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "action": {
+        "const": "get"
+      },
+      "memory": {
+        "additionalProperties": false,
+        "properties": {
+          "body": {
+            "type": "string"
+          },
+          "created_at": {
+            "type": "string"
+          },
+          "memory_id": {
+            "type": "string"
+          },
+          "revision": {
+            "type": "string"
+          },
+          "scope": {
+            "type": "string"
+          },
+          "summary": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "updated_at": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "memory_id",
+          "title",
+          "scope",
+          "summary",
+          "created_at",
+          "updated_at",
+          "revision",
+          "body"
+        ],
+        "type": "object"
+      }
+    },
+    "required": [
+      "action",
+      "memory"
+    ],
+    "type": "object"
+  }
+]
    • Changedmemory_write4 fields changed
      • removedInput schema / additionalProperties
        Removed value: -false
      • addedInput schema / oneOf
        Added value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "action": {
+        "const": "create"
+      },
+      "body": {
+        "type": "string"
+      },
+      "project": {
+        "type": "string"
+      },
+      "summary": {
+        "type": "string"
+      },
+      "title": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "action",
+      "title",
+      "summary",
+      "body"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "action": {
+        "const": "patch"
+      },
+      "base_revision": {
+        "type": "string"
+      },
+      "edits": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "new_text": {
+              "type": "string"
+            },
+            "old_text": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "old_text",
+            "new_text"
+          ],
+          "type": "object"
+        },
+        "minItems": 1,
+        "type": "array"
+      },
+      "memory_id": {
+        "type": "string"
+      },
+      "summary": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "action",
+      "memory_id",
+      "base_revision",
+      "edits"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "action": {
+        "const": "replace"
+      },
+      "base_revision": {
+        "type": "string"
+      },
+      "body": {
+        "type": "string"
+      },
+      "memory_id": {
+        "type": "string"
+      },
+      "summary": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "action",
+      "memory_id",
+      "base_revision",
+      "summary",
+      "body"
+    ],
+    "type": "object"
+  }
+]
      • removedInput schema / properties
        Removed value: -{
-  "action": {
-    "enum": [
-      "create",
-      "patch",
-      "replace"
-    ],
-    "type": "string"
-  },
-  "base_revision": {
-    "type": "string"
-  },
-  "body": {
-    "type": "string"
-  },
-  "edits": {
-    "items": {
-      "additionalProperties": false,
-      "properties": {
-        "new_text": {
-          "type": "string"
-        },
-        "old_text": {
-          "type": "string"
-        }
-      },
-      "required": [
-        "old_text",
-        "new_text"
-      ],
-      "type": "object"
-    },
-    "minItems": 1,
-    "type": "array"
-  },
-  "memory_id": {
-    "type": "string"
-  },
-  "project": {
-    "type": "string"
-  },
-  "summary": {
-    "type": "string"
-  },
-  "title": {
-    "type": "string"
-  }
-}
      • removedInput schema / required
        Removed value: -[
-  "action"
-]
  2. 3 tool updatesv0.1.0
    • First observedmemory_delete
    • First observedmemory_read
    • First observedmemory_write
Deploy Server
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

TDQS

A4.2/5.0

Scored across 3 tools

Disambiguation5/5

Each tool handles a distinct lifecycle operation: reading/querying, writing/updating, and deleting memories. There is no overlap between the primary actions, and the sub-modes within memory_read are explicitly separated (list, search, get).

Naming Consistency5/5

All tool names follow the same memory_verb pattern using clear, lowercase snake_case verbs. The naming makes the operation type immediately obvious and perfectly consistent across the set.

Tool Count5/5

Three tools is a compact but complete surface for a permanent memory store. Each tool earns its place, and no redundant or extraneous operations exist.

Completeness5/5

The set covers the full lifecycle: create/modify via memory_write, read via memory_read (including list/search/get), and delete via memory_delete. Revision-handling and Git-history recovery details further round out the functionality, leaving no critical gaps.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive

Resources

Related MCP Connectors

Related MCP Servers

  • Hypermnesic

    leonardsellem
    A
    license
    A
    quality
    A
    maintenance
    Git-native long-term memory for AI agents: your markdown files are the source of truth, the search index is a disposable projection rebuilt from git, and every memory the agent writes is a reviewable git commit. Served over one OAuth-secured MCP endpoint with hybrid lexical+semantic recall and a gated, git-first commit_note write tool.
    7
    9
    AGPL 3.0