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.
What existing users should know
memclaw_* tool callsExisting calls remain accepted; use caura_* in new prompts and configs
mc_ API keysEvery existing key keeps working
MEMCLAW_* env varsSupported aliases remain; prefer CAURA_* for new configuration
MCP & API endpointsUse the current caura.ai URLs shown in the dashboard
Packages & pluginsUpgrade with the current install docs; steps vary by channel
Your dataTenants, memories, fleets — nothing moves, nothing resets
Your data and account stay in place; use current Caura names for new configuration.
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?
Existing MCP tool calls, API keys, and supported environment-variable aliases continue to work. Use caura_* tool names and current Caura URLs for new configuration, and follow the current install docs when upgrading packages or plugins because migration behavior varies by channel.
Do I need to update my agent's MCP config?
Existing supported configs continue to work, but new setups should use the caura.ai URLs shown in the dashboard. When you next edit an older config, migrate it to the current URL and caura_* tool names.
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.