Content Import brings existing work into 📝Import & Export — an Obsidian vault via a self-serve CLI command, or a Substack blog via a white-glove migration. It exists so switching to MythOS doesn't mean starting your library from zero. It's for anyone moving from another tool who wants their existing writing to arrive with them, not get left behind.
Key Capabilities
- Obsidian import (self-serve) —
npx mythos-mcp import --obsidian ~/vaultconverts[[wikilinks]]to @mentions, uploads embedded images, preserves frontmatter tags and dates, and rebuilds your knowledge graph - Dry-run first — preview what an Obsidian import will do before committing, with
--visibilityand--skip-existingcontrols - Substack migration (concierge) — a white-glove migration MythOS runs on your behalf, not a self-serve button; content and audience carry over, with traffic redirects possible for custom-domain writers
- Idempotent re-imports — imported content is tagged with its source, so re-running an import skips what's already there
Getting Started
- Obsidian: generate an API key at Settings → API, then run
npx mythos-mcp import --obsidian ~/path/to/vault --dry-runto preview - Substack: reach out via Settings → Import/Export to request a migration — this is arranged with MythOS directly, not self-service
FAQ
- Can I import my Substack myself right now? Not as a self-serve button — it's currently a concierge migration MythOS performs for you, with a dry-run review step before anything is written.
- Does Obsidian import use fuzzy title matching for wikilinks? No — it matches on exact title, then case-insensitive exact title; it does not do fuzzy matching.
- What happens to my images? Embedded images from an Obsidian vault upload to Cloudflare R2 automatically as part of the import.
- What visibility do imported memos get? Private by default for Obsidian imports, controllable with the
--visibilityflag.
Related
- 📝Library Export — taking your content back out