memex
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NEO4J_URI | Yes | The URI for the Neo4j database (e.g., bolt://localhost:7687) | |
| NEO4J_USER | Yes | The username for the Neo4j database | |
| GEMINI_API_KEY | Yes | Your Google Gemini API key for synthesis and extraction | |
| NEO4J_PASSWORD | Yes | The password for the Neo4j database |
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 |
|---|---|
| get_project_contextB | Returns a compressed briefing of the project as a Markdown string: active modules, recent decisions, and open problems. |
| get_symbol_contextB | Returns detailed information about a specific function or class as a Markdown string including callers/callees. |
| get_recent_decisionsB | Returns architectural and technical decisions from the past N days as a Markdown string. |
| get_open_problemsA | Returns currently open technical problems and TODOs sorted by severity as a Markdown string. |
| search_contextA | Semantic + keyword + graph traversal search across all node types. Use for broad discovery. Returns a Markdown string. |
| get_engineering_contextC | Returns a bounded, provenance-aware engineering ContextPacket projection using the shared memex selector. |
| get_stale_contextC | Returns relationships that have decayed in confidence and may be outdated as a Markdown string. |
| record_decisionA | Creates a Decision node in the graph. Call this when making or discovering architectural choices. Returns a status string. Phase 9: pass corroborates= to reinforce, supersedes= to replace, or force=true to bypass duplicate detection. |
| record_problemA | Creates a Problem node in the graph. Call this when discovering bugs or technical debt. Returns a status string. |
| resolve_problemB | Marks a Problem as closed and records the resolution. Returns a status string. |
| invalidate_edgeA | Explicitly invalidates a graph edge when it is discovered to be stale or incorrect. Returns a status string. |
| explain_changeA | Cross-references a git commit's diff with linked Decision/Problem nodes and returns a grounded Markdown explanation synthesised by Gemini Pro. |
| predict_impactA | Returns a ranked Markdown list of modules likely affected by changes to a file, based on graph coupling (calls + imports + decision links). No LLM call. |
| get_context_briefingA | Returns a ranked, token-capped briefing of the most important context for this codebase. Use this at the START of a session to efficiently prime your understanding without overloading your context window. The briefing includes cluster summaries, recent high-confidence decisions, and active problems. |
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 14 tools
Tools are largely distinct: each getter targets a specific aspect (decisions, problems, project, symbol, stale context, engineering context), and write/action tools are clearly separate (record, resolve, invalidate, explain, predict). Minor overlap exists between get_project_context and get_context_briefing, both providing project summaries, but they differ in focus and usage timing.
All tool names follow a consistent verb_noun pattern in snake_case (get_recent_decisions, record_decision, resolve_problem, invalidate_edge, explain_change, predict_impact). The verb clearly indicates the action, and nouns describe the target resource, making the naming predictable and uniform.
14 tools is well within the expected range for a knowledge/context management server. Each tool addresses a distinct operation (retrieval, recording, mutations, analysis) without redundancy, and the count feels appropriate for the scope of the domain.
The surface covers key lifecycle operations: decision recording (with supersede/force), problem creation and resolution, edge invalidation, context retrieval via multiple projections, search, and analytical tools. Minor gaps include no explicit update tool for decisions or problems (though supersede covers decision updates), but agents can work around with existing tools.