learned-experience
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_API_KEY | No | Used as the default for LEARNED_EXPERIENCE_EMBED_API_KEY when remote embeddings are enabled | |
| LEARNED_EXPERIENCE_DB | No | Explicit database path | $LEARNED_EXPERIENCE_HOME/experiences.db |
| LEARNED_EXPERIENCE_HOME | No | Data directory (database and model cache) | ~/.learned-experience |
| LEARNED_EXPERIENCE_EMBEDDINGS | No | Embedding provider: local, openai, ollama, or none (lexical only) | local |
| LEARNED_EXPERIENCE_HOOK_QUIET | No | Set to 1 to make the failure hook silent when nothing matches | unset |
| LEARNED_EXPERIENCE_EMBED_MODEL | No | Embedding model: Xenova/all-MiniLM-L6-v2, text-embedding-3-small, nomic-embed-text | provider default |
| LEARNED_EXPERIENCE_TRANSFER_DIR | No | The only directory the transfer tool may read or write .jsonl files in | $LEARNED_EXPERIENCE_HOME/transfers |
| LEARNED_EXPERIENCE_EMBED_API_KEY | No | Key for remote embedding providers | $OPENAI_API_KEY |
| LEARNED_EXPERIENCE_EMBED_BASE_URL | No | Any OpenAI-compatible endpoint, or the Ollama base URL | provider default |
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| recallA | Check whether this problem (or a similar one) has been solved before. Call BEFORE investigating. Returns ranked hits with fix, avoid-list and confidence. Exact error text in |
| recordA | Store what happened after solving (or failing to solve) a non-trivial problem. Duplicates are merged automatically: the response says whether the record was created, merged into an existing one, or linked to one with a different fix. Keep it terse and never include secrets. |
| reinforceA | Feedback loop. After applying a fix from |
| amendA | Patch fields of an existing record (better fix, extra avoid items, corrected context). Only supplied fields change. |
| forgetA | Permanently remove a record that is wrong or obsolete. |
| consolidateA | Deterministic clustering of episodes that look like the same underlying lesson. For each cluster, write ONE |
| statsA | Counts, success rate, duplicates prevented, embedding status, most common context tags. |
| transferA | Portability. mode='export' writes every record as JSONL (to |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| solve | Wraps a problem in the recall -> apply -> reinforce -> record loop. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| protocol | The recall -> apply -> reinforce -> record loop |
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/fitz2882/learned-experience'
If you have feedback or need assistance with the MCP directory API, please join our Discord server