MemoVault
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEMOVAULT_DATA_DIR | No | The directory path where memory data will be stored. | ./memovault_data |
| MEMOVAULT_LLM_BACKEND | No | The LLM backend to use, typically 'openai' or 'ollama'. | |
| MEMOVAULT_OPENAI_MODEL | No | The OpenAI model to use (e.g., gpt-4o-mini). | gpt-4o-mini |
| MEMOVAULT_MEMORY_BACKEND | No | The storage backend for memories, either 'vector' for semantic retrieval or 'simple' for JSON storage. | |
| MEMOVAULT_OPENAI_API_KEY | No | Your OpenAI API key, required if using the 'openai' backend. | |
| MEMOVAULT_EMBEDDER_BACKEND | No | The backend used for generating embeddings (e.g., 'openai', 'ollama', or 'sentence_transformer'). |
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": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_memoryA | Store new information in memory. Use this to remember facts, preferences, events, or any important information the user wants to persist across sessions. Args: content: The information to remember memory_type: Optional type (fact, preference, event, opinion, procedure, personal) Returns: Confirmation message with the memory ID |
| search_memoriesB | Search for relevant memories. Use this to find stored information related to a topic or question. Args: query: What to search for top_k: Maximum number of results (default: 5) Returns: Dictionary with matching memories |
| chat_with_memoryA | Chat with memory-enhanced responses. Use this for questions where stored memories might provide context. The response will incorporate relevant memories automatically. Args: query: User's question or message top_k: Number of memories to use as context (default: 5) Returns: AI response enhanced with relevant memories |
| get_memoryB | Retrieve a specific memory by ID. Args: memory_id: The unique identifier of the memory Returns: The memory content and metadata |
| delete_memoryC | Remove a specific memory. Args: memory_id: The unique identifier of the memory to delete Returns: Confirmation message |
| list_memoriesC | Show recent memories. Args: limit: Maximum number of memories to return (default: 10) Returns: Dictionary with list of recent memories |
| clear_memoriesA | Clear all stored memories. Warning: This permanently deletes all memories! Returns: Confirmation message |
| memory_statusB | Get the current status of the memory system. Returns: Dictionary with status information |
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/Blvckjs96/MemoVault'
If you have feedback or need assistance with the MCP directory API, please join our Discord server