light-agent-memory-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| memory_project_saveA | Save or update project context — tech stack, architecture, conventions, and notes. |
| memory_project_getA | Retrieve saved context for a specific project by name. |
| memory_project_listA | List all saved projects. |
| memory_pref_saveA | Save or update a personal coding preference — style, tools, workflow patterns. |
| memory_pref_getA | Retrieve a specific preference by key. |
| memory_pref_listA | List all saved preferences, optionally filtered by category. |
| memory_learning_saveA | Record a session learning — solutions discovered, bugs encountered, insights gained. |
| memory_learning_searchA | Search session learnings by keyword. Matches against title, content, and tags. |
| memory_saveA | Unified save — automatically routes to the correct table based on type. Use data fields matching the type: project (name, path, tech_stack, architecture, conventions, notes), preference (key, value, category), or learning (title, content, project_name, tags). |
| memory_searchA | Search across all memory types by keyword. Optionally filter by type (project, preference, learning). |
| memory_deleteA | Delete a specific memory by type and ID. |
| memory_listA | List all stored memories with optional type filter, pagination, and stats. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
The type-specific tools (project/pref/learning) are fairly distinct, but the generic memory_save, memory_search, and memory_list overlap with specialized equivalents like memory_project_save, memory_learning_search, and memory_project_list. The descriptions clarify the generic vs. specific distinction, but an agent still faces multiple paths to accomplish the same operation.
Tool names consistently use a memory_ prefix and mostly follow a memory_<type>_<action> pattern. Minor inconsistencies exist: 'search' is used for learning where 'list' or 'get' might be expected, and the top-level memory_save/memory_search/memory_delete/memory_list deviate from the type-specific naming pattern.
Twelve tools is reasonable for a memory system covering projects, preferences, and learnings. The count is slightly inflated by the generic memory_* tools that duplicate type-specific functionality, but overall the server remains well-scoped and navigable.
The server covers create, read, list, search, and delete across all memory types, either through type-specific or generic tools. Minor gaps exist—learning has no direct get-by-ID function, and deletion is only exposed through the generic memory_delete—but common workflows can be completed with existing tools.