Memory MCP Server AI Integration

Retrieve a comprehensive list of all MemBridge Memory Records stored for the authenticated user. MemBridge Memory Records contain information that users have explicitly saved for future reference, such as personal preferences, project details, important facts, decisions, ongoing work, and cross-session context. Returns each memory record's ID, title, content preview, creation timestamp, and size. Memory records are sorted by creation date (newest first). This is the primary tool for discovering what memory records exist and obtaining their IDs for further operations like retrieve_record or delete_record. Context optimization: Set titleOnly to true to retrieve only titles and metadata without content, reducing context usage while searching for relevant records.

Create and save a new MemBridge Memory Record when the user explicitly requests to save information for future reference. Records persist across chat sessions and AI tools. Types of information users may want to save: • User preferences and personal details (favorite languages, frameworks, coding style, work hours, timezone) • Project-specific information (architecture decisions, naming conventions, tech stack, API endpoints, database schemas) • Important facts and context (business rules, domain knowledge, recurring tasks, team structure) • Decisions and rationale (why certain approaches were chosen, what alternatives were considered) • Ongoing work and progress (current tasks, blockers, next steps, incomplete features) • User instructions and guidelines (how they prefer code to be written, what to avoid, communication preferences) • Repeated information (if a user mentions something important multiple times) • Cross-session context (information that should be remembered for future conversations) Best practices for record organization: • Keep each record focused on a single topic or category (e.g., separate records for 'Work schedule' and 'Coffee preferences' rather than one 'Personal info' record) • You can call this tool multiple times to create separate records for different topics - this is encouraged for better organization • Splitting information into multiple records makes it easier to find, update, and delete specific information later • Well-organized records improve searchability and reduce the need to read through irrelevant information • Aim for records that are detailed enough to be useful but focused enough to have a clear purpose Each record is assigned a unique UUID and can be updated, retrieved, or deleted later. Subject to storage limits based on the user's plan. Use this tool only when the user asks to save, remember, or store information.

Update an existing MemBridge Memory Record's content and title while preserving the original creation timestamp. The updated timestamp will be refreshed. Useful for consolidating related information, refining outdated details, or correcting inaccurate memory records. Use this when you need to modify existing information rather than creating a duplicate entry. Best practices for updating records: • Keep each record focused on a single topic or category for easier management • If the update introduces significantly different information, consider creating a separate record instead • Well-organized, topic-focused records are easier to find, update, and delete later

Retrieve the full content and metadata of a specific MemBridge Memory Record by its ID. MemBridge Memory Records contain information that users have explicitly saved for future reference, such as personal preferences, project details, important facts, decisions, ongoing work, and cross-session context. Returns the complete memory record including title, content, creation timestamp, and last update timestamp. Use this when you need to access the detailed information of a particular MemBridge Memory Record that you've identified through list_record or that the user has referenced.

Permanently delete a specific MemBridge Memory Record by its ID. This action is irreversible and will completely remove the memory record from storage. Use this when information becomes outdated, incorrect, or is no longer needed. Always confirm with the user before deleting important memory records.