Lesson 19 of 30, Module 3: Make It Trustworthy. It refuses to leave the folder, asks before it overwrites, and remembers your answers.
What you can do after this lesson
Anything you tell a chat lives only in that chat. If a rule must survive a closed chat, a restart or a different app, it has to be stored outside the chat, in a file that your own server owns.
The problem we inherited
A server that can write can write over the wrong document, and there is no undo you can reach from a chat.
Downloads
- Module 3 checkpoint (scribe-checkpoint-m3.zip): working code as the module leaves it, so a broken session costs you nothing
- The course GitHub repo: every checkpoint, the README and the full lesson list
Prefer to read?
The written version of this part of the course is on Substack: https://genaiunplugged.substack.com/p/give-your-ai-agents-memory-mcp-shared.
Lesson transcript
Told on Monday, gone on Tuesday
I told Claude my style rules on Monday. On Tuesday it had never heard of them.
Hello, and welcome to lesson 19 of the MCP Masterclass. Last lesson your guard held under 3 attacks. Today we meet the 1 habit of that guard which is going to wear you down, and we find out where it comes from. And we start with our map, as always.
12 lit boxes. The guard is on. And the box right next to it, called the memory, is still dark.
The same question in every chat
Well, here is the habit.
Open a chat and ask Scribe to fix a typo in draft.md. It asks. You say yes.
Open a new chat tomorrow and ask for another fix in the same draft. It asks again. Same draft, same question, same yes.
And it is not only the guard. In lesson 14 you saved a job called tidy_draft. Say you tell Claude, in one chat, to keep your openings under 12 words. It does. Open a new chat, and that rule is gone. It was never anywhere except the chat.
What context really is
But you must be thinking, Dheeraj, Claude remembers things. It remembered my draft, and it remembered the folder.
It did, inside 1 chat. That is called context, and context is nothing but the conversation you are in right now. Every message, every tool call, every answer, all of it sits in front of the model while that chat is open.
Close the chat, and the context is gone. The next chat starts at zero. Not because Claude is forgetful. Because a chat is where the words live, and the words do not leave the chat.
Where your rules should live
So the question is, where should the rules live?
They could live in Claude Desktop. Some apps have a memory of their own now, and it is useful. But it is the same story as the asking in lesson 16. It belongs to that 1 app. Claude Code does not have it, and the next app will not either.
Or they could live in your server.
Scribe is a program. Programs can write a file. A file survives a closed chat, a restart, and a switch to a different app.
So if Scribe writes down what you tell it, and reads it back when asked, then your rules live in the 1 place that travels. Same answer as the guard.
The memory box
That is the memory box on the map. It is nothing but a small file next to your server, and 2 tools. One writes a note into it. The other reads the notes back.
And once it exists, the guard can use it too. Tell Scribe once to trust a draft, and the question stops for that draft, in every app, in every chat.
The map, and what is next
So where does our map stand at the end of this lesson?
Still 12 boxes lit. But you know exactly why the memory has to be a file, and why it has to be your server that holds it.
Next lesson you give Scribe a memory, and it is the fourth time you run the 5 steps.
Bye now, and I will see you in the next lesson.
