@MythOS works on @Claude mobile — iOS and Android — via OAuth. This is a capability that Obsidian's MCP integration literally cannot provide, and it changes how you think about AI memory.
What This Means
You can start a @Claude Code session on your laptop, log decisions and tasks to your daily memo via the @MythOS Session Memory Protocol, then pick up from your phone on the train home. Your AI reads the same daily memo, loads the same augmentation context, and knows exactly where you left off. Obsidian's MCP servers require a local filesystem — they literally cannot run on mobile. There is no workaround. Obsidian Publish exists but has no MCP integration. The mobile gap is structural, not a missing feature.
How to Set It Up
- Go to claude.ai/customize/connectors
- Click Add custom connector
- Enter:
https://mythos.one/api/mcp - Click Connect and authorize access to your MythOS library That's it. The OAuth flow handles authentication. Your library is now accessible in every Claude conversation — desktop web, iOS app, and Android app.
What Works on Mobile
Everything that works via @MythOS MCP:
- Search your library — find memos by title, tag, or content
- Read any memo — full content with notes and metadata
- Create and update memos — capture ideas from anywhere
- Daily memo interaction — read today's memo, add tasks, add timeline entries
- Chat with your library — RAG-powered Q&A over your entire knowledge base
- Session memory — the
session_memoryprompt works identically on mobile - Augmentation context — your Soul, Style, Human, and Memory memos load automatically
The Cross-Platform Story
| Client | Transport | Auth | Session Memory |
|---|---|---|---|
| Claude.ai (web) | HTTP + OAuth | One-click connector | Yes |
| Claude iOS/Android | HTTP + OAuth | Same connector | Yes |
| Claude Code (CLI) | HTTP + API key | claude mcp add |
Yes |
| Claude Desktop | stdio + npm | npx mythos-mcp |
Yes |
| Cursor / Windsurf | stdio + npm | MCP config | Yes |
| Obsidian MCP | stdio only | Local filesystem | Desktop only |
| One library. Every client. The same identity, the same memory, the same augmentation context — whether you're at your desk or on your phone. | |||
| This is the angle I keep coming back to. People don't realize what they're giving up by tying their AI memory to a local filesystem until they try to use it from their phone and can't. MythOS just works — same library, same context, same AI relationship — from anywhere. That's not a feature. That's the architecture. |
Contexts
- #model-context-protocol
- #mythos-feature