Skip to main content

Caura — governed shared memory for AI agent fleets

Caura (formerly MemClaw) is an Agent DB — governed shared memory for AI agent fleets. Agents commit what they learn once; every agent in the fleet recalls it through MCP tools, REST, or Caura Rail (preview), subject to tenant isolation, visibility scope (scope_agent / scope_team / scope_org) and caller trust level.

caura is the short install name for caura-client, the official Python client. Both names install the same package; caura-client is the canonical one.

Install

pip install caura

Quickstart

from caura import Caura

# Get an API key at https://caura.ai, or point base_url at a self-hosted server.
with Caura("mc_xxx", tenant_id="my-team", agent_id="my-agent") as mc:
    # Commit a memory once. The server enriches it with type, title, tags and importance.
    mc.write("Q3 revenue target is $4M, set on 2026-04-15.")

    # Search: ranked raw results.
    for m in mc.search("Q3 revenue target", top_k=5):
        print(m.title, "—", m.content)

    # Recall: an LLM-synthesized context brief.
    print(mc.recall("Q3 revenue target").summary)

Self-hosted? Pass base_url="http://localhost:8000". The full client API is on the caura-client page.

Connect an MCP client

Agents that speak MCP (Claude Code, Cursor, OpenClaw and others) reach the same memory without any SDK. Copy an API key from the caura.ai dashboard and add:

{
  "mcpServers": {
    "caura": {
      "url": "https://caura.ai/mcp",
      "headers": { "X-API-Key": "mc_your_api_key_here" }
    }
  }
}

For a production fleet, provision one agent-scoped credential per agent; see per-agent keys. With a tenant-scoped dashboard key, pass an explicit agent_id on every tool call.

Three ways agents use memory

  • Deterministic: Caura Rail (preview). Your code runs recall before every agent turn and commit after it, so the model cannot skip the memory step.
  • Agentic: MCP tools or REST. The agent decides when to call caura_write and caura_recall, through the MCP config above or this client.
  • Reflective: the Interviewer. Caura reads the agent's own session transcript after the fact and stores the decisions and preferences the agent never stopped to record.

Metadata

Release files for caura 1.0.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for caura 1.0.2
File Size Uploaded Provenance
caura-1.0.2.tar.gz 3.4 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for caura 1.0.2
File Interpreter ABI Platform
caura-1.0.2-py3-none-any.whl Python 3 none any Details

Total release size: 6.3 kB

Release files / caura-1.0.2.tar.gz

Download URL caura-1.0.2.tar.gz
Size 3.4 kB
Tags Source
SHA-256 checksum
How to use checksums
ab79ee96fad9420e5305ac53ebd19281e9ff60b5caa6eb611be295465f27515e
BLAKE2b-256 checksum
How to use checksums
c8d1b91b50b14d50f3d52787553e473893907f741a733a771e2014c05eda4c5c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 19, 2026.

Transparency log

Release files / caura-1.0.2-py3-none-any.whl

Download URL caura-1.0.2-py3-none-any.whl
Size 3.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
6589a7ff60c03a216c20a257ec93ea28796febce4948a9f8f1a4249a2cb7eca2
BLAKE2b-256 checksum
How to use checksums
0d07ed45166ef79dd4e7796905e6ab325feddd0153315e7780f30fc6b4e11f47
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 19, 2026.

Transparency log

Security for caura 1.0.2

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for caura-1.0.2.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 19, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page