Library Export takes your content back out of 📝Import & Export — a one-click markdown or JSON download from the web, or incremental syncs from the command line. It exists so your library is never a one-way door; what you wrote is yours to keep in a format you can actually use elsewhere. It's for backups, migrations, or anyone who wants a local copy alongside their MythOS library.

Key Capabilities

• Markdown export — every memo as a .md file with YAML frontmatter (title, ID, tags, visibility, dates), compatible with Obsidian, Hugo, and other markdown tools
• JSON export — full data export including memos, daily entries, contacts, templates, habits, community activity, and settings
• Web download — one-click from Settings, gated behind re-authenticating your account, delivered as a gzipped file
• CLI incremental sync — npx mythos-mcp pull with --since, --tags, and --full flags for scripted, repeatable backups

Getting Started

1. Go to Settings → Import/Export
1. Choose Markdown or JSON and download, re-authenticating when prompted
1. For scripted backups, run npx mythos-mcp pull --output ~/mythos-backup with an API key set

FAQ

• Is my export encrypted? The web download is gated behind re-authentication, not file-level encryption — treat the downloaded file itself as sensitive.
• Can I export just what's changed since my last backup? Yes — the CLI's pull command supports --since for incremental exports, tracked via its own manifest.
• What's included in the JSON export that isn't in the markdown export? The JSON export is the fuller one — daily entries, contacts, templates, habits, community activity, and settings, not just memo content.
• Can I filter what gets exported? Yes, the CLI supports --tags to scope a pull to specific tags.

Related

• 📝Content Import — bringing content the other direction

Contexts

• 🏷️#mythos
• 🏷️#mythos-feature
• 🏷️#mythos-integrations