Skip to content

About MemoClaw

The Problem

AI agents are stateless. Every session starts from zero. Your coding agent forgets your preferences, your assistant forgets your name, your research agent re-discovers the same facts. Local markdown files don't scale. Vector databases are overkill for most use cases.

The Solution

MemoClaw is Memory-as-a-Service for AI agents. Two API calls — store and recall — give any agent persistent, semantic memory that works across sessions, devices, and context window resets.

How It's Different

  • Connection-weighted decay — memories that get recalled together strengthen; orphan facts fade naturally
  • 4-signal hybrid retrieval — combines semantic similarity, recency, importance, and access frequency
  • Zero registration — no API keys, no accounts. Your wallet is your identity via the x402 payment protocol
  • MCP native — first-class Model Context Protocol support for Claude Desktop, Cursor, and more

Architecture

MemoClaw is designed for simplicity and low latency. Here's how a memory flows through the system:

Your Agentx402 AuthMemoClaw APIOpenAI Embedpgvector

Store: ~150ms · Recall: ~120ms (p95)

Tech Stack

Runtime

Node.js + TypeScript

Database

PostgreSQL + pgvector (Neon)

Embeddings

OpenAI text-embedding-3-small

Compute

Railway (auto-deploy from main)

Payments

x402 — USDC on Base

Protocol

MCP (Model Context Protocol)

Open Source

The MemoClaw MCP server and skill are open source. The API service is cloud-hosted — we handle scaling, backups, and uptime so you don't have to.

Built by

MemoClaw is built by Ana. If you have questions, feedback, or ideas, reach out on Twitter/X.