What you get
- Search existing memories from your IDE or AI agent.
- Save important coding conversations back into EchoMemory.
- Use stdio-based MCP in IDEs like Cursor and Windsurf, or a remote connector flow in Claude.
Before you begin
- Generate an Echo API key.
- Make sure the key has the scopes your deployment expects for MCP tools.
- Decide whether your client is an IDE using stdio or a Claude client using a remote MCP connector URL.
Use stdio for Cursor and Windsurf. Use the remote connector flow for Claude web and Claude Desktop.
Connect clients
Cursor
Configure an MCP server that runs through npx or a local built server path.
Command: npx
Args: -y @echomem/mcp@latest
Env:
ECHO_API_TOKEN=ec_your_key_here
ECHO_API_BASE_URL=https://echo-mem-chrome.vercel.app
Windsurf
Add the MCP server entry to your Windsurf MCP config JSON.
{
"mcpServers": {
"echomem": {
"command": "npx",
"args": ["-y", "@echomem/mcp@latest"],
"env": {
"ECHO_API_TOKEN": "ec_your_key_here",
"ECHO_API_BASE_URL": "https://echo-mem-chrome.vercel.app"
}
}
}
}
Claude web custom connector
Use the remote MCP connector URL instead of a local command process.
Name: EchoMemory
Remote MCP server URL:
https://echo-mem-chrome.vercel.app/api/extension/mcp
Claude Desktop
Use the same remote custom connector flow as Claude web instead of a local daemon or file path.
Open Claude Desktop
Go to Settings > Connectors
Click Add custom connector
Name: EchoMemory
Remote MCP server URL:
https://echo-mem-chrome.vercel.app/api/extension/mcp
Compatibility notes
The current public surface keeps canonical tool names and supports a compatibility window for older aliases. Treat the canonical operations as the stable docs-facing contract.
search_memoriessave_conversationget_memories_by_time_rangesearch_memories_by_keywordssearch_others_memories
Common mistakes
- Using the Claude connector instructions for Cursor or Windsurf.
- Forgetting to pass the Echo API token as an environment variable.
- Assuming remote connector support exists in every IDE.
- Using old alias names in new setup docs instead of canonical tool names.
- Missing the scope required for MCP routes.