Getting Started

Choose the right EchoMemory setup before you install anything

The fastest way to reduce confusion is to choose the product surface first, then follow the guide for that surface only. This page aligns the shared prerequisites and language across the website, Chrome extension, EchoChat iOS app, MCP server, and OpenClaw plugin.

What you need first

  1. Create or access your EchoMemory account.
  2. Decide which surface you need first: website, browser extension, iOS app, MCP client, or OpenClaw.
  3. Generate an Echo API key if you plan to use MCP or OpenClaw cloud features.
  4. Choose the guide that matches where you want EchoMemory to show up.
Do not start from repo-level setup unless you are actively developing. Most end users should begin from the product surface they actually care about, not from the implementation repo.

Choose the right surface

If you want to...Read this guideWhy
Sign in, open the memory graph, or join a gathering inviteWebsiteThe website owns the normal account flow, graph entry, API key manager, and invite-link event entry.
Use the native Echo product on iPhoneEchoChat iOS AppThe iOS app covers talking with Echo, memory creation, profile reading, and the product walkthrough.
Save and reuse context in browser AI chatsChrome ExtensionThe extension owns extraction, query optimization, and supported chat-site integrations in the account-backed cloud flow.
Give Cursor, Windsurf, or Claude access to memoriesMCP ServerMCP is the contract for IDE and agent integrations. It covers local stdio and remote connector flows.
Sync markdown memory files from OpenClaw into Echo cloudOpenClaw PluginThe plugin handles memory directory scans, localhost UI, sync status, Slack commands, and retrieval behavior.
If you need MCP or OpenClaw, stop after choosing the surface and read Get API Key before editing config.

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.