Skip to main content
Memory connectors attach OpenLIT to external agent memory providers. Use them to browse stored facts, search semantically, add or edit memories, copy between backends, and ask Otter questions grounded in connector data. Add memory connectors from Configuration → Connectors (/connectors) under the Memory category, or directly from the Memory page (/memory) when no connector exists yet. Connectors are scoped to the current project and environment.
Memory connectors use the same atomic registry as data-source connectors, but they do not participate in telemetry signal routing. Credentials are encrypted on the connector instance rather than the ClickHouse vault.

​
Mental model

  • Atomic connectors — one Mem0 project endpoint, one Zep tenant, one Claude memory store configuration per connector instance.
  • Capability-driven UI — each vendor advertises supported operations (list, search, add, update, delete, feedback). OpenLIT hides actions the vendor does not support.
  • Filters — user, session/run, and agent filters are declared per vendor. Some connectors require a session or user before listing memories.
  • Port links — copying a memory to another connector stores provenance metadata so you can trace copies back to the source.

​
Supported memory connectors

Self-hosted Mem0 or Zep deployments work when you point the connector at a compatible API URL and supply the same authentication style as the hosted service.

​
Capability matrix

* Claude has no dedicated search API — OpenLIT filters listed memories locally for search queries. † Zep delete targets graph edges/nodes, not an entire session.

​
Add a memory connector

1

Select project and environment

Use the header selectors for the target project and environment.
2

Open Connectors

Go to Configuration → Connectors, open the Memory section in the catalog, and choose Add connector.
3

Pick a vendor

Select Claude, Mem0, or Zep.
4

Configure endpoint and credentials

Set the API URL (defaults work for hosted services), optional SSRF toggles for private networks, and the API key. Mem0 also accepts optional organization and project IDs.
5

Test and save

Run a health check, then save. Open Memory (/memory) and select the connector from the dropdown.
You can also add a connector from the Memory page empty state — Add memory connector opens the same add dialog.

​
Memory page features

Once a connector is configured, the Memory page provides:

​
Otter memory tools

When Otter runs on the Memory page or in chat with memory context, it can call connector-backed tools: Otter passes required filter arguments (user, session, agent) when the vendor mandates them. Enterprise builds apply the same RBAC and audit hooks as the /api/memory routes.

​
Authentication

API keys are stored encrypted on the connector (enc:v1:…) and decrypted only server-side for outbound requests.

​
Copy between connectors

Use Copy on the Memory page to duplicate memories into another write-capable connector in the same project and environment. OpenLIT:
  1. Reads the source memory from the origin connector
  2. Writes to the destination connector when add is supported
  3. Stores metadata.openlit.port on the destination memory and links the destination connector back to the source for traceability
Copy requires connectors:update (or equivalent memory mutation permission in enterprise).

​
Security and reliability

  • Endpoints validated (http/https only); credentials in URLs rejected; private/metadata SSRF targets blocked where applicable.
  • Secrets encrypted on the connector instance, redacted from errors, never logged.
  • Outbound calls use the shared safe-fetch layer with the same SSRF controls as data-source connectors.
  • Content limits: memory body up to 20,000 characters; metadata JSON up to 4,000 characters.

​
Vendor documentation

Claude memory

Anthropic Managed Agents memory stores.

Mem0 API

Mem0 Platform REST API reference.

Zep SDK

Zep Cloud API and graph memory.

Connectors overview

Shared connector registry and project scope.

Data-source connectors

Tempo, Loki, Prometheus, Jaeger, and ClickHouse.

Otter (AI Copilot)

Chat with Otter across OpenLIT surfaces.

Environments

Partition memory connectors by environment.