smg-claude-memory-mcp
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| memory_versionA | Get the current version of the Memory MCP server and configuration. |
| memory_useC | Set the active project. Subsequent tools use it by default. |
| memory_init_projectC | Initialize a new project namespace (creates DuckDB + registers it). |
| memory_list_projectsA | List all registered projects. |
| memory_project_infoC | Get detailed info for a project. |
| memory_storeB | Store a new memory with auto-embedding, summary, entity extraction, and TTL. |
| memory_searchC | Semantic search with composite relevance scoring. |
| memory_recallC | Recall a specific memory by ID or exact title. |
| memory_updateC | Update an existing memory. Re-embeds if title/content changed. |
| memory_deleteB | Soft-delete (archive) or hard-delete a memory. |
| memory_listC | List memories with filtering, sorting, and pagination. |
| memory_provenanceC | Get the full audit trail for a memory. |
| memory_get_rulesB | Get all mandatory and forbidden rules (direct SQL, cached). |
| memory_session_startB | Start a session. Loads rules, last summary, sprint goals, recent decisions. |
| memory_session_endC | End a session and store its summary. |
| memory_attach_projectC | Attach an existing project directory. Auto-activates on success. |
| memory_make_portableC | Move the project's DB into the project directory for git sharing. |
| memory_syncC | Sync a portable DB after git pull. Auto-activates on success. |
| memory_exportC | Export all active memories to human-readable .md files. |
| memory_importC | Import memories from exported .md files. |
| memory_model_infoC | Current embedding model + available presets. |
| memory_set_modelC | Switch embedding model between 'english' and 'multilingual' presets. |
| memory_reembedC | Re-embed all active memories with the current model. |
| memory_check_updateA | Check if a newer version of the Memory MCP server is available. Queries GitHub Releases first, falls back to git commit comparison. Does NOT modify anything - it only reports. Returns step-by-step update instructions when a new version is available. |
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 24 tools
Each tool has a clearly distinct purpose with descriptions that resolve potential overlap. Tools for storing, searching, recalling, updating, and deleting memories are well-differentiated. Retrieval tools (search, recall, list) each target different access patterns.
All tools start with 'memory_' forming a consistent prefix. However, the second component mixes verb_noun (memory_store, memory_search), noun phrases (memory_project_info), and bare verbs (memory_use), which is somewhat inconsistent. The pattern is more noun-heavy than typical verb_noun conventions.
With 24 tools, the server offers extensive functionality, but this exceeds the typical well-scoped range of 3-15. While the domain (memory management with projects, sessions, models, git sync) justifies many tools, the count feels heavy. A reduction or grouping could improve coherence.
The tool set covers most expected operations for a memory server: CRUD for memories, project management, session handling, model configuration, export/import, and audit trails. Missing features include project deletion and rule editing, which are minor gaps. The surface is largely complete for the stated purpose.