What you need first
- Create or access your EchoMemory account.
- Decide which surface you need first: website, browser extension, iOS app, MCP client, or OpenClaw.
- Generate an Echo API key if you plan to use MCP or OpenClaw cloud features.
- Choose the guide that matches where you want EchoMemory to show up.
Choose the right surface
| If you want to... | Read this guide | Why |
|---|---|---|
| Sign in, open the memory graph, or join a gathering invite | Website | The website owns the normal account flow, graph entry, API key manager, and invite-link event entry. |
| Use the native Echo product on iPhone | EchoChat iOS App | The iOS app covers talking with Echo, memory creation, profile reading, and the product walkthrough. |
| Save and reuse context in browser AI chats | Chrome Extension | The extension owns extraction, query optimization, and supported chat-site integrations in the account-backed cloud flow. |
| Give Cursor, Windsurf, or Claude access to memories | MCP Server | MCP is the contract for IDE and agent integrations. It covers local stdio and remote connector flows. |
| Sync markdown memory files from OpenClaw into Echo cloud | OpenClaw Plugin | The plugin handles memory directory scans, localhost UI, sync status, Slack commands, and retrieval behavior. |
Terminology guide
Cloud-first vs local-only
Cloud-first means EchoMemory data is backed by your account and can be used across devices or tools. In the current docs, that applies to the Chrome extension. Local-only behavior should be read as an OpenClaw concept unless a guide explicitly says otherwise.
Memories vs sources
Memories are distilled units of knowledge. Sources are the original conversation or document material those memories came from.
Local UI vs memory graph
In OpenClaw, the localhost local UI browses local markdown files. The cloud memory graph is a separate web surface and should not be described as the same thing.