Connect imem to Obsidian
3 steps · about 2 minutes
Obsidian connects through Self-hosted LiveSync credentials from the app's Sync page — not MCP. AI clients reach the same vault over MCP with OAuth in the browser and no API key; Obsidian instead syncs the markdown files directly.
https://mcp.imem.aiAuthentication uses OAuth in the browser with PKCE and dynamic client registration. No API key is needed; tokens are scoped to one vault and can be revoked from settings.
Setup steps
- 1
Sign in and open the Sync page
Sign in to imem and open the Sync page at /app/sync. It holds your LiveSync Setup URI, Pass Phrase, and manual credentials for this vault.
- 2
Install Self-hosted LiveSync
In Obsidian, install and enable the Self-hosted LiveSync community plugin.
- 3
Use the Setup URI
Copy or open the Setup URI from the Sync page, then enter the Pass Phrase when LiveSync asks. The passphrase unlocks this one setup package; it is not your vault encryption key.
Verify the connection
Once LiveSync connects, edits flow both ways between Obsidian and the web vault. To confirm the full loop, paste the test prompt into any AI client already connected over MCP and watch the note appear in Obsidian.
Run the imem setup check now. Use the "setup_imem" tool if it is available. It should save and read a harmless test memory, then tell me whether imem is ready.
Troubleshooting
- Setup URI fails — use Manual setup on the Sync page instead: server URL, database name, username, and password each go into their own LiveSync fields. Do not paste them into the Setup URI field.
- Password is hidden — the password disappears after the reveal window expires. Rotate credentials on the Sync page to get a new Setup URI, Pass Phrase, and manual password.
Ready to remember everything?
Create a free vault, connect Obsidian, and your AI keeps durable memory across every session.