hippocampus
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 |
|---|---|
| personal_initA | Arranque en frío (D18): crea/abre la BD en Delega la orquestación (init + persistir |
| personal_create_typeA | Añade un tipo de nodo/arista al catálogo en runtime (D16). |
| personal_find_entityA | Busca una entidad ANTES de crearla (buscar-y-enlazar, R3). Devuelve candidatos. |
| personal_upsert_entityC | Crea/actualiza una entidad; reusa el id si ya existe (R3). |
| personal_linkC | Crea una arista dirigida y tipada entre dos entidades (R4). |
| personal_add_reflectionA | Guarda el texto crudo como documento y lo enlaza a las entidades (provenance, R5). |
| personal_attachB | Guarda un adjunto (imagen). Pasá |
| personal_mergeA | Fusiona el nodo duplicado Reapunta aristas, provenance y adjuntos al superviviente y funde los aliases, respetando los UNIQUE del esquema (atómico). No permite fusionar el 'Self' como origen. |
| personal_neighborsA | Mapa barato del vecindario: nodos + aristas + summary recortado + presupuesto (R6, DL1). Fase A de la lectura en dos fases. Por default NO trae el texto crudo de los
documentos (
|
| personal_get_nodeA | Contenido completo de un nodo (fase B, DL2): summary completo + docs crudos sin truncar. Atajo dirigido para leer todo lo que cuelga de un nodo tras verlo en el mapa
( |
| personal_provenanceC | Documentos de los que salió un nodo (F1): el texto crudo asociado, no el nodo pelado. |
| personal_searchA | Búsqueda keyword (FTS5) por nombre/alias/summary y texto de documentos (R7, DL4). Primer paso del flujo: barato. Recorta en el borde el |
| personal_graphC | Subgrafo |
| tech_saveC | Guarda una observación/mensaje (como |
| tech_searchB | Recupera observaciones por FTS (como |
| tech_getB | Contenido completo de una observación, sin truncar (como |
| tech_updateB | Actualiza una observación, p. ej. cerrar una tarea con |
| tech_list_openA | Lista las tareas abiertas ( |
| conversation_importB | Importa un transcript crudo de una consola de IA (§3.15, D25). Idempotente por (source, external_id). |
| conversation_searchC | Recupera conversaciones de auditoría por FTS (título + contenido) (§3.15). |
| conversation_getC | Transcript completo de una conversación, sin truncar (§3.15). |
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
The three prefixed domains (personal/tech/conversation) are clearly separated, and most tools target a distinct resource or action. Within personal, however, personal_provenance and personal_get_node both expose raw document text, and personal_neighbors/personal_graph both return graph-like views, requiring careful reading of descriptions.
The personal_/tech_/conversation_ prefixes create clear namespaces, and most tools follow a verb_noun pattern. A few personal_ names are bare nouns (provenance, neighbors, graph) rather than action verbs, which is a minor but noticeable inconsistency.
21 tools is on the heavy side for a single MCP server, even though the load is distributed across three distinct modules. The count feels manageable but exceeds the typical well-scoped range.
Core workflows are well covered: creating and linking entities, adding documents/attachments, searching and retrieving content, updating tech observations, and importing/auditing conversations. The main gaps are the lack of a general delete/detach operation and limited batch listing, but these can usually be worked around.