Now that LLMs can read and use context files before initially responding, your AI output becomes that much better.
I listened to all the experts and created .md (notes/plain text) files for myself, each role/hat, and then for each project. While the “about me” text didn’t stale, the other two files did. Maybe the role doesn’t change often, but you find yourself realizing you need to refine it as you learn how it all works together with AI. And the project files were continually changing.
It really isn’t that difficult to update a text file, but those documents are hard to read though. Not only that, I can’t keep up with the changes on the project ones.
As I went along with longer-term projects, I discovered:
- Project files became obsolete quickly, particularly when it was a new idea. You set out doing one thing and discovered a better way.
- It’s a pain to search through desktop files. And some of those text files were super long, making it hard to determine what you need to update.
- You drain your usage quicker using context files within projects.
- If you have a Project folder per role, projects within that umbrella can stack up quickly. If you have a context file for each project under a Project folder, then you’re wasting usage. But then you’re uploading and downloading files making the Project context obsolete.
All in all, managing the context files became a whole ‘nother task.
Then I got an idea.
I’m a heavy Notion.so user, so when I downloaded Claude Desktop, I made sure to connect Notion through Claude’s MCP. If I could use the Notion MCP to create databases and pages…why couldn’t I use this system for context files?
That’s just what I did—let me show you how to do the same.
Note that I use “projects” in two different ways here:
- Lowercase is the normal meaning (”I am working on a fun project…”)
- Initial caps is in reference to Claude’s Project feature
Tools I’m using for this instance
- Claude Desktop (free)
- Notion (through browser, free or paid account)
When to use MCPs for context writing
This method can get complicated and overwhelming quickly, so it might be overkill for some users.
For context files
I have a lot of things going on at any given time: personal life, business & brand, special projects (there are at least three), and work. I setup Project folders in Claude for each one of those areas, and then created for when the instructions got too granular or separate from the whole. For example: my work has two distinct components, so there’s one Project folder for each. Then I write personally for work, so there’s another folder for that. And then another one for branded communications.
You see how this gets complicated fast.
Context files on your desktop are great for information that doesn’t change, or changes very little over time. But when you’ve got multiple projects going on that need different contexts, or context that changes often, this would be a good solution for you.
For communication between chats
This is really where the method shines.
Some of my projects involve coding, which means I’m going back and forth between Claude Chat, which is better for research and design, and Claude Code, which is best for technical aspects and execution. I became frustrated having to reexplain things, upload the same documents into the various chats, and even having to explain Claude Chat’s thinking to Claude Code.
Or even worse, sometimes the chat thread would hit capacity or throw an error, which means I was forced to recreate or try to explain where we were at to a different chat.
Now I use Notion for site changelogs, procedural instructions, and even onboarding files.
Benefits of Using Notion + Claude MCP for Context Files
- Claude can write context files for you (saves time)
- Easier to manually maintain: easier to read through formatting, and Notion has great search capabilities
- Can have multiple sets of contexts without draining your usage
- More seamless transition between products and chats
- You can use your context files ON THE GO! Once you MCP is set up, you can use it outside of Claude Desktop
Now that we have the ‘why,’ the next part will tackle the initial setup of your Claude Hub in Notion.