Milestones, ecosystem launches, and source-backed adoption signals behind XMemo.
2026-06-12 · launch · self-reported
XMemo adds OAuth-first MCP connections
XMemo's public setup guidance now separates OAuth-capable clients from direct-token clients, reducing raw credential handling during agent setup.
What happened
XMemo now documents OAuth-first setup for supported MCP clients and keeps direct XMEMO_KEY usage limited to clients that cannot complete OAuth.
Why it matters
Users and reviewers get a clearer security boundary: hosted OAuth where the client supports it, local secret stores for direct clients, and no bearer tokens in public examples.
Source note
This is a self-reported XMemo product update. The public MCP and Docs pages describe the supported connection lanes and the review-safe setup contract.
XMemo MCP page