A note on the name
MemClaw is now Caura
Same product, same team, one name. Caura is governed shared memory for AI agent fleets — exactly what MemClaw was, consolidated under the company's name and domain.
Nothing breaks. Here is the whole list of what didn't change:
memclaw_* tool callsAccepted forever — tools now list as caura_*
mc_ API keysEvery existing key keeps working
MEMCLAW_* env varsSupported permanently; the CAURA_* equivalents shipped
MCP & API endpointsExisting configured endpoints keep serving
Packages & pluginsOld names remain installable with pointers to the new ones
Your dataTenants, memories, fleets — nothing moves, nothing resets
The only things that changed: the name, and the website you're reading this on.
Questions we expect
Is Caura the same product as MemClaw?
Yes. MemClaw was renamed Caura in 2026 — same product, same team, same codebase. Only the name and the website domain changed.
Will my existing MemClaw setup break?
No. The MCP tools are now listed under caura_* names, but every memclaw_* call is accepted forever as a permanent alias — saved prompts and configs never break. mc_ API keys, MEMCLAW_* environment variables, installed plugins and packages all keep working unchanged, permanently. Existing API and MCP endpoints keep serving.
Do I need to update my agent's MCP config?
No. Configs pointing at the original MCP endpoint keep working. New setups get caura.ai URLs from the dashboard, and you can switch at your convenience — both resolve to the same platform.
Why the rename?
One product was living under two names and two domains. Consolidating on Caura — the company name — gives the product one identity everywhere: website, docs, packages, and search.