engram-global
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rememberA | Save a new memory. Call this whenever you discover something important during a task (a fact,
a preference, project status, an event). Self-score |
| recallA | Search for and return memories. Always call this at the start of a task. It surfaces relevant past
knowledge, preferences, and project context.
mode="fast" searches only tier=hot, quickly. If the score is low it
automatically falls back to deep.
mode="deep" searches more broadly, including cold/superseded/episode
memories, and follows associative links.
mode="exhaustive" ignores activation and ranks purely by relevance across
every memory. Use this as a last resort to dig up a "sunk" memory you're
sure you recorded but that isn't surfacing under fast/deep.
You normally don't need to pass |
| reinforceA | Report which memories actually turned out to be useful. When a task finishes, report the ids of memories that actually helped. Reinforced memories are more likely to surface near the top on the next recall. Passing multiple ids at once links those memories together via a co-occurrence link (Hebbian learning). strength ranges 0.1-3.0 and controls how strong the reinforcement is. |
| correctA | Use this instead of forget when a memory turns out to be wrong. Demotes the old memory to superseded (corrected) and creates a new memory that records the reason for the correction. Explicitly recording the mistake prevents the same error from being repeated (a hypercorrection effect). |
| linkA | Create an explicit link between two memories. Call this when you want to manually connect related memories. Deep recall can then follow this link to surface memories associatively. |
| forgetA | Soft-delete a memory (move it to trash). Call this when a memory is no longer needed and you want it excluded from search. This moves the memory to trash rather than physically deleting it, so it can be restored if deleted by mistake. If you want to correct an error rather than remove a memory, use correct instead of forget. |
| consolidation_candidatesA | Return clusters of episode memories that are candidates for consolidation. Call this before ending a session (at session end), to surface clusters of similar older episodes that are candidates for compressing into knowledge or project memories. The LLM generates the summary, then calls mark_consolidated to complete the consolidation. |
| mark_consolidatedA | Record that a consolidation has been completed. Call this after the LLM has summarized a cluster surfaced by consolidation_candidates and created the new memory via remember. The original episodes are demoted to cold (long-term storage) and linked to the new memory via a derived_from link. Also use this tool to demote the target episodes to cold after acting on a skill_candidates cluster. |
| skill_candidatesA | Return clusters of episode memories that are candidates for extraction into a reusable skill. When 3 or more (default; the "three-times rule") episodes recording the same shape of work (procedure) form a similar cluster, use this as input for judging whether that procedure is worth extracting into a reusable skill (a how-to document — a SKILL.md for Claude Code, etc.). Unlike consolidation_candidates, there is no age filter here (recently repeated work is exactly the target). Even when a cluster is found, always propose turning it into a skill to the user and get their approval first. Never create or deploy a skill on your own. Once the decision (adopt or pass) is made, record the reasoning via remember(type=knowledge), then clean up the original episodes with mark_consolidated(episode_ids, new_memory_id). |
| reindexA | Rebuild the DB index from the Markdown files. Call this after manually editing files, or when you suspect the DB is corrupted. Only memories that differ are re-embedded, so this is faster than a full rebuild. |
| statsA | Return memory statistics. Shows memory counts (by type and tier), the number of access events, the number of links, and so on. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ricoaiproject-cmd/engram-global'
If you have feedback or need assistance with the MCP directory API, please join our Discord server