MCP MITM Mem0
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enable debug logging | false |
| MCP_NAME | No | MCP server name | memory-service |
| MITM_HOST | No | MITM proxy host | localhost |
| MITM_PORT | No | MITM proxy port | 8080 |
| MEM0_API_KEY | Yes | Your Mem0 SaaS API key (required) | |
| DEFAULT_USER_ID | No | Default user ID for memories | 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_memoriesB | Search conversation history using natural language - USE AUTONOMOUSLY based on conversation triggers |
| list_memoriesB | List all stored conversation memories |
| add_memoryC | Store important information to memory - AUTO-STORE user preferences and decisions |
| delete_memoryB | Delete a specific memory by ID |
| analyze_conversationsC | Analyze conversation patterns and generate insights - AUTO-RUN at session start |
| suggest_next_actionsB | Get personalized recommendations - AUTO-SUGGEST when user seems stuck or asks 'what now?' |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_recent_memories | Get recent memories for the default user. Quick access to the 10 most recent memories. Useful for: - Getting up to speed at the start of a session - Checking what was just discussed - Understanding current context without searching |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose with no overlap: add, delete, list, and search memories are distinct CRUD operations, while analyze_conversations and suggest_next_actions provide separate analytical functions. The descriptions reinforce this separation with specific use cases like 'AUTO-STORE' or 'AUTO-SUGGEST'.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., add_memory, analyze_conversations). The verbs are clear and descriptive (add, analyze, delete, list, search, suggest), and the nouns align well with the memory/conversation domain, making the set predictable and readable.
With 6 tools, this server is well-scoped for managing conversation memories and providing insights. Each tool earns its place by covering essential operations (CRUD for memories, analysis, and suggestions) without being overly sparse or bloated, fitting a typical utility server range.
The tool set provides strong coverage for memory management (add, delete, list, search) and analytical functions (analyze, suggest), with no dead ends. A minor gap exists in update functionality for memories (e.g., edit_memory), but agents can work around this by deleting and re-adding, and the core workflows are well-supported.