<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Memory on Vibe Coding</title><link>https://vibecoding.rest/tags/memory/</link><description>Recent content in Memory on Vibe Coding</description><generator>Hugo</generator><language>en</language><atom:link href="https://vibecoding.rest/tags/memory/index.xml" rel="self" type="application/rss+xml"/><item><title>Memory</title><link>https://vibecoding.rest/mcp-servers/memory/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/mcp-servers/memory/</guid><description>&lt;p&gt;The Memory server stores facts as a local knowledge graph — entities, relationships, observations — that persists between sessions, giving an agent a lightweight, inspectable form of long-term memory.&lt;/p&gt;&#10;&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;&#10;&lt;p&gt;Without persistence, every new conversation starts with zero context about you, your preferences, or past decisions. A local, file-backed memory store closes that gap without relying on a specific vendor&amp;rsquo;s built-in memory feature.&lt;/p&gt;</description></item></channel></rss>