EchoMemoryDocs
Why EchoOpen Timeline
Get API Key

Create the EchoMemory API key required by MCP Server and OpenClaw Plugin

API keys are managed from the signed-in website surface. If you plan to use MCP Server or OpenClaw cloud features, do this before touching their config files.

MCP guideOpenClaw guide

When you need it

  • MCP Server needs an Echo API token before Cursor, Windsurf, or Claude can talk to EchoMemory.
  • OpenClaw Plugin needs an API key for cloud sync and cloud retrieval.
  • The website and EchoChat iOS app use your normal account session instead of asking for a raw API key during normal end-user use.

Create a key

  1. Sign in on the website first at https://yeahecho.com/login?next=/api.
  2. Open Developer API Keys at https://yeahecho.com/api.
  3. Create a descriptive name such as Cursor workspace or OpenClaw gateway.
  4. Copy the generated ec_... token immediately. The full value is shown only once.
The API key page itself is protected by the web login session. If you are not authenticated, sign in on the website first and then reopen the API key manager.

Manage keys

Name every key by destination

The website stores the key name, created date, and last-used date. Use that metadata to tell one integration from another.

Revoke unused keys

The API manager supports revocation directly. Once revoked, the corresponding integration stops working immediately.

Use the key correctly

  • Pass the raw ec_... value exactly as copied.
  • MCP docs refer to it as ECHO_API_TOKEN.
  • OpenClaw plugin docs place it in the plugin config as apiKey.
  • If a setup fails, first verify that you copied the entire token and did not revoke it.
Continue to MCP ServerContinue to OpenClaw Plugin