---
mw_bundle: 1
id: MDNKPYPH
title: "Bundle Test 001"
url: https://memory.wiki/b/MDNKPYPH
document_count: 6
updated: 2026-05-04T02:56:28.388Z
analysis_generated_at: 2026-05-02T19:45:38.731Z
analysis_stale: true
source: "Memory.Wiki"
---
# Bundle Test 001

> ⚠ _Analysis may be stale — one or more member docs were edited after the last analysis run. Re-run the canvas to refresh._

## Summary

The documents outline mdfy.cc, a platform designed for intentional AI memory ownership and portability. It shifts AI interaction from passive extraction to user-curated knowledge that is shared across different LLMs using Markdown and the Model Context Protocol. While the vision is high-level, technical documents reveal critical challenges in ensuring LLMs can successfully fetch and parse these shared memories.

## Themes

- AI Memory Ownership
- Cross-Platform Interoperability
- Markdown Infrastructure
- Server-Side Rendering Challenges

## Cross-document insights

- The 'Closed Loop' Paradox: mdfy's core value proposition of 'portability' is currently broken by a technical 500 error/SPA issue that prevents LLMs from reading the very links they are supposed to consume.
- Intentionality vs. Automation: Unlike competitors Mem0 or Letta which use automated extraction, mdfy bets on 'Human-in-the-Loop' curation, suggesting that quality memory requires intentional authorship.
- Protocol as Product: The integration of MCP (Model Context Protocol) transforms mdfy from a simple Markdown host into a functional bridge between siloed AI ecosystems like ChatGPT and Claude.
- The 'Lawly' and 'PastLife' documents serve as dogfooding evidence, showing that mdfy is used as a project-planning 'anchor' for complex AI-generated business ideas.

## Key takeaways

- mdfy.cc aims to be the open standard for AI memory, prioritizing user curation over automated extraction.
- Cross-AI portability relies heavily on Markdown and robust URL-fetching capabilities that LLMs can access.
- The platform is building a multi-layered ecosystem including Chrome extensions, desktop apps, and API protocols.

## Open questions / gaps

- Security and permission model details for 'Private' vs 'Public' documents are mentioned but not technically specified.
- User growth metrics or validation of the 'User Author' vs 'AI Extract' market hypothesis are missing.
- Pricing or sustainability model for the hosted MCP service is not addressed.

## Notable connections

- **doc:mcRfLTP7** ↔ **doc:r-um_oJp** — The extension captures the data that the MCP tools later manipulate and share across AI sessions.

## Concepts (this bundle)

- **AI Memory Ownership**
- **Markdown as Lingua Franca**
- **SSR & LLM Fetching**
- **Cross-AI Workflow**
- **Model Context Protocol (MCP)**
- **Intentional Capture**

## Concept relations

- **AI Memory Ownership** ↔ **Intentional Capture** — requires
- **Cross-AI Workflow** ↔ **Markdown as Lingua Franca** — facilitated by

1. [Publish my meeting notes to mdfy](https://memory.wiki/r-um_oJp)

2. [QuickLook — Quick Start](https://memory.wiki/womPEbUm)

3. [Chrome Extension — Quick Start](https://memory.wiki/mcRfLTP7)

4. [SNS Launch Execution Plan](https://memory.wiki/jryfJV4D)

5. [mdfy for Mac — Quick Start](https://memory.wiki/CaQ31sfk)

6. [Frequently Asked Questions](https://memory.wiki/SfYEsN5E)


_Digest view — follow any link above to fetch that doc's full markdown. Add `?full=1` to this URL for the concatenated payload._