Observed since 20 Oct, 22:12 UTC
No superseded metadata states collected. Unchanged observations do not create new revisions.
MCP server for 0Latency — persistent memory layer for AI agents. Give Claude, Cursor, or any MCP client long-term memory.
Persistent memory for AI agents. Give Claude, Cursor, Windsurf, or any MCP-compatible tool long-term memory in one config change.
0Latency automatically extracts, stores, and recalls memories across conversations — so your AI assistant actually remembers you.
Sign up at 0latency.ai and grab your API key from the dashboard.
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"0latency": {
"command": "npx",
"args": ["-y", "@0latency/mcp-server"],
"env": {
"ZERO_LATENCY_API_KEY": "your-api-key-here"
}
}
}
}
Add to your project .mcp.json:
{
"mcpServers": {
"0latency": {
"command": "npx",
"args": ["-y", "@0latency/mcp-server"],
"env": {
"ZERO_LATENCY_API_KEY": "your-api-key-here"
}
}
}
}
Add to .cursor/mcp.json in your project root:
{
"mcpServers": {
"0latency": {
"command": "npx",
"args": ["-y", "@0latency/mcp-server"],
"env": {
"ZERO_LATENCY_API_KEY": "your-api-key-here"
}
}
}
}
Same pattern — just point your client's MCP config at:
command: npx -y @0latency/mcp-server
env: ZERO_LATENCY_API_KEY=your-api-key-here
npm install -g @0latency/mcp-server
Then use 0latency-mcp as the command instead of npx:
{
"command": "0latency-mcp",
"env": {
"ZERO_LATENCY_API_KEY": "your-api-key-here"
}
}
| Tool | Description |
|---|---|
memory_add | Extract and store memories from a conversation turn |
remember | Simple interface — "remember this" for quick facts |
seed_memories | Bulk-load known facts directly (bypass extraction) |
memory_recall | Recall relevant memories for current conversation context |
memory_search | Full-text search across stored memories |
memory_list | List memories with type/pagination filters |
memory_delete | Delete a specific memory by ID |
import_document | Import a document and extract memories from it |
import_conversation | Import a chat export and extract memories from each turn |
memory_graph | Query the knowledge graph (entities, relationships, paths) |
| Variable | Required | Default | Description |
|---|---|---|---|
ZERO_LATENCY_API_KEY | ✅ | — | Your 0Latency API key |
ZERO_LATENCY_API_URL | — | https://api.0latency.ai | API base URL (for self-hosted) |
memory_add or remember to store important factsmemory_recall to retrieve relevant contextNo prompt engineering required. The AI tools are designed to be self-describing — your AI assistant will naturally use them when appropriate.
Store a memory:
"Remember that I prefer TypeScript over JavaScript and use Vim keybindings."
Recall memories:
"What do you know about my coding setup?"
Import existing context:
"Import this project README as background knowledge."
Explore the knowledge graph:
"What entities are connected to the auth-service project?"
git clone https://github.com/0latency-ai/mcp-server.git
cd mcp-server
npm install
npm run build
npm start
MIT © Justin Ghiglia
Download counts and popularity will appear here as the collector receives them.
This describes our collected data; it is not a security assessment.
Observed since 20 Oct, 22:12 UTC
No superseded metadata states collected. Unchanged observations do not create new revisions.
package:5c82d32f3887f4e00285e240320331540474fed6378c7281f90a294925255530