Memphora
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEMPHORA_API_KEY | Yes | Your Memphora API key | |
| MEMPHORA_USER_ID | No | Unique identifier for your memories | mcp_default_user |
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 |
|---|---|
| memphora_searchA | Search your personal memories for relevant information. Use this when the user asks about something they may have mentioned before, their preferences, past experiences, or any personal information. Examples: 'What's my favorite food?', 'Where do I work?', 'What projects am I working on?' |
| memphora_storeA | Store important information about the user for future recall. Use this when the user shares personal details, preferences, facts about themselves, or explicitly asks you to remember something. Examples: 'I work at Google', 'My favorite color is blue', 'Remember that I'm allergic to peanuts' |
| memphora_extract_conversationB | Extract and store memories from a conversation. Use this to save important information from a longer discussion. The system will automatically identify and store relevant facts. |
| memphora_list_memoriesB | List all stored memories for the user. Use this to see what information has been remembered. |
| memphora_deleteA | Delete a specific memory by its ID. Use this when the user wants to forget something or correct incorrect information. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| recall_context | Search memories to get context about the user before responding |
| save_session | Save important information from the current conversation |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| My Memories | All stored memories for the current user |
| Memory Summary | Summary of stored memories and statistics |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap: delete removes memories, extract processes conversations, list shows all memories, search finds specific memories, and store adds new memories. The descriptions reinforce these distinct roles, making misselection unlikely.
All tools follow a consistent 'memphora_verb_noun' pattern (e.g., memphora_delete, memphora_extract_conversation). This uniform naming convention makes the tool set predictable and easy to understand at a glance.
With 5 tools, this server is well-scoped for a memory management system. Each tool earns its place by covering core operations (store, search, list, delete, and conversation extraction), avoiding bloat while providing complete functionality.
The tool set offers complete CRUD/lifecycle coverage for the memory domain: store (create), search and list (read), delete (delete), and extract_conversation (a specialized create/update). There are no obvious gaps, enabling agents to handle all expected workflows without dead ends.