claude-engram
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLAUDE_ENGRAM_MODEL | No | Ollama model (optional — only for scout_search, convention checking) | gemma3:12b |
| CLAUDE_ENGRAM_ARCHIVE_DAYS | No | Days until inactive memories archive | 14 |
| CLAUDE_ENGRAM_SCORER_TIMEOUT | No | AllMiniLM server idle timeout (seconds) | 1800 |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| claude_engram_statusB | Check Claude Engram health. Returns: status, model, memory stats. |
| session_startA | Load full context: memories, checkpoints, decisions, memory health. Auto-cleans duplicates. Hook auto-starts basic session, but this gives deep context. |
| session_endA | Optional. Shows session summary. All memories auto-save without this - just a nice recap. |
| pre_edit_checkB | Run BEFORE editing important files. Checks: past mistakes, loop risk, scope violations. |
| memoryC | Memory operations. Operations:
|
| workB | Work tracking. Operations:
|
| scopeA | Scope guard for multi-file tasks. Operations:
|
| loopA | Loop detection to prevent death spirals. Operations:
|
| contextA | Context protection for long tasks. Operations:
|
| conventionB | Project conventions. Operations:
|
| outputC | Output validation. Operations:
|
| scout_searchB | Search codebase semantically. Returns findings with files, lines, connections. |
| scout_analyzeC | Analyze code with local LLM. Provide code and question. |
| file_summarizeC | Summarize file purpose. Modes: quick (pattern-based) or detailed (LLM). |
| deps_mapC | Map file dependencies. Shows imports and optionally reverse deps. |
| impact_analyzeC | Analyze change impact. Shows dependents, exports, risk level. |
| code_quality_checkC | Check code for AI slop: long functions, vague names, deep nesting. |
| code_pattern_checkC | Check code against stored conventions using LLM. |
| audit_batchC | Audit multiple files for issues. Supports glob patterns. |
| find_similar_issuesC | Search codebase for bug pattern (e.g., 'except:\s*pass'). |
| session_mineA | Mine session history. Operations:
|
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 21 tools
Most tools have distinct purposes, but there is some overlap between code_pattern_check, code_quality_check, and convention.check, which all analyze code against rules. Additionally, scout_search and find_similar_issues both search code for patterns, though they target different use cases. Descriptions help differentiate, but an agent might occasionally misselect.
Tool names consistently use underscore_case with a verb_noun or noun_verb pattern (e.g., audit_batch, session_start, code_quality_check). However, a few names like claude_engram_status and find_similar_issues break the pattern slightly, and the nested operation prefixes (e.g., 'checkpoint_save' under 'context') could be more uniform.
With 21 tools, the count is on the higher side but still reasonable for a comprehensive developer assistant server. Each tool serves a distinct purpose, and the inclusion of nested operations (e.g., under 'memory' and 'session_mine') keeps the top-level list manageable. A slight reduction could improve navigability.
The tool set covers a wide range of features: memory management, session/handoff handling, code analysis, conventions, scope, output validation, and work tracking. It lacks direct file I/O tools, but that is likely handled by other servers. Overall, the surface is comprehensive for a context and memory management server, with only minor gaps like a dedicated planning or task decomposition tool.