claude-dev-memory
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LETTA_API_KEY | Yes | Your Letta Cloud API Key | |
| LETTA_AGENT_ID | No | The Agent ID to use (optional) | |
| LETTA_BASE_URL | No | Letta API URL | https://api.letta.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| memory_recallA | 讀取專案的 Core Memory，取得專案上下文、學習紀錄、決策。 用於：session 開始時恢復上下文，或隨時查看記憶內容。 |
| memory_updateA | 更新 Core Memory，記錄專案進度和決策。 注意：Core Memory 有 ~2000 token 限制，超過時建議使用 memory_archive。 |
| memory_archiveA | 存入 Archival Memory，保存完整 spec、commit、學習紀錄。 特性：無大小限制、可語意搜尋。 |
| memory_searchB | 搜尋 Archival Memory，找出相關的過去記錄。 用於：遇到類似問題時參考過去的解法。 |
| memory_statusA | 查看記憶系統狀態，首次使用時自動初始化 Agent。 顯示：連線狀態、Core Memory 使用量、Archival 記錄數。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Core Memory | 專案的核心記憶，包含 project、learnings、decisions 三個區塊 |
TDQS
Scored across 5 tools
Each tool targets a distinct memory operation: recall reads core memory, update writes core memory, archive moves to archival, search queries archival, and status inspects the system. The distinction between recall and search is clear from their descriptions, avoiding ambiguity.
All tools follow the consistent pattern of 'memory_' prefix followed by a lowercase verb (recall, update, archive, search, status). This predictable naming makes it easy to infer the function of each tool.
With 5 tools, the set is well-scoped for a memory management system, covering read, write, archival, search, and status without unnecessary redundancy.
The tool surface covers the full lifecycle of a memory system: accessing core memory, updating it, archiving to long-term storage, searching that storage, and monitoring system state. This is a complete set for the stated purpose, with no obvious gaps.