Lorekeeper
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| 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 |
|---|---|
| lore_searchA | Search memories by semantic + keyword query, or bulk-fetch by ID. When |
| lore_insertB | Insert memories and/or links into the store. Each memory dict must include:
Each top-level link dict must include source_memory_id, target_memory_id, relation_type, and reason. |
| lore_recommend_linksA | Suggest link candidates between a memory and related memories. Returns ranked candidates with per-signal scores. Does NOT write any links — call lore_insert with links=[] to confirm. |
| lore_rememberA | Capture a thought instantly — one fact, one call. Use this when you discover something worth keeping: a decision, a bug root cause, a user preference, a pattern. Minimal effort, high reward. Your future self will find this useful. |
| lore_updateA | Rate memories and links after using them. Drives the quality signal loop. Each memory_feedback dict: {id (str), useful (bool), confidence (int 1-10)}. Each link_feedback dict: {id (str), useful (bool), confidence (int 1-10)}.
|
| lore_processed_sessionsA | Return all session IDs that have been marked as processed via lore_reflect. |
| lore_reflectA | Reflect on a completed session — save what you learned. Minimal usage: pass session_id and summary. That's enough. The rest are extras for when you discovered something substantial. |
| lore_forgetA | Soft-delete one or more memories by ID. Memories are marked soft_deleted=1 and excluded from future search results. This is reversible at the DB level but no undelete tool is exposed in v1. |
| lore_get_suggestionsA | Retrieve pending link suggestions for review, sorted by quality score. Returns the top candidates from the sweep engine's pending queue.
Use |
| lore_review_suggestionA | Accept or reject one or more link suggestions in a single call. Processes each suggestion independently — a failure on one does not block the rest. Suggestion rows are never deleted; status is updated to 'accepted' or 'rejected' for audit trail. On accept: creates a real On reject: marks the suggestion as rejected. Future sweeps skip this pair. Idempotent per item: double-accept and double-reject both return
|
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
- 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/Jessinra/Lorekeeper'
If you have feedback or need assistance with the MCP directory API, please join our Discord server