ClawKit Logo
ClawKitReliability Toolkit
Back to Registry
Official Verified

Qoris Memory — Persistent Agent Memory

Persistent memory for OpenClaw agents via the Qoris MCP server. Explicit save/recall tools for cross-session context. User-owned API key, no automatic data capture.

skill-install — Terminal

Install via CLI (Recommended)

clawhub install openclaw/skills/skills/apps-debug/qoris-memory-mcp
Or

Qoris Memory — Persistent Agent Memory

Purpose

This skill connects your OpenClaw agent to the Qoris MCP server so it can persist memories you explicitly save — across sessions, with version history and semantic search.

Important: memories are saved only when your agent calls save_memory (or you run a memory command). The skill does not monitor, capture, or silently persist conversation content. Nothing is transmitted until you make an explicit tool call.

Data Handling & Privacy

This skill sends data to an external service. Understand what before installing:

  • What gets sent: only the exact content you pass to save_memory / search_knowledge / update_memory tool calls. Nothing else.
  • Where it's stored: https://mcp.qoris.ai/mcp (TLS), scoped to your QORIS_WORKSPACE_ID. Your workspace is isolated from other users.
  • Who can read it: only holders of your QORIS_API_KEY. The key is yours, generated by you at qoris.ai/dashboard.
  • Retention: per the retention policy at https://qoris.ai/privacy. You can delete individual memories with delete_memory or rotate the API key in your dashboard to invalidate all access.
  • No auto-capture: there is no automatic memory mode. Every persisted memory corresponds to an explicit tool call your agent made.
  • Credential ownership: QORIS_API_KEY is your own per-user secret. No credentials are bundled with this skill. Treat the key as sensitive — create a restricted workspace for shared or enterprise use.

What Qoris Memory Does

Explicit cross-session save/recall

Your agent can persist information it decides is worth remembering via the save_memory tool, and recall it later via search_knowledge or get_memories. Memories survive across sessions and remain available until you delete them.

Versioned records

Every memory update is a versioned record with a timestamp. You can see the history of what was stored and when via get_document_full_content.

Memory branches

Create separate memory contexts (branches) for different projects, clients, or workspaces. Your agent operates in the right context for the right task.

Conflict surfacing

When multiple agents update the same memory, the MCP server surfaces contradictions for human resolution rather than silently overwriting.

Shared workspace memory

Memory is workspace-scoped. Agents sharing the same QORIS_WORKSPACE_ID share the same memory pool. Your team can coordinate through a shared knowledge base.

Semantic search

search_knowledge runs a semantic search across stored memories and returns cited answers grounded in what was actually stored — no hallucination.

Available Memory Tools

These are the only tools this skill exposes. Each is an explicit, user-triggered action — nothing runs automatically.

save_memory

Store a new memory with optional tags and metadata. Content is the exact string you pass.

Metadata

Stars4473
Views0
Updated2026-05-01
View Author Profile
AI Skill Finder

Not sure this is the right skill?

Describe what you want to build — we'll match you to the best skill from 16,000+ options.

Find the right skill
Add to Configuration

Paste this into your clawhub.json to enable this plugin.

{
  "plugins": {
    "official-apps-debug-qoris-memory-mcp": {
      "enabled": true,
      "auto_update": true
    }
  }
}

Tags

#memory#persistent-memory#agent-memory#context#versioning#knowledge-base#cross-session#enterprise#rag#mcp#latest
Safety NoteClawKit audits metadata but not runtime behavior. Use with caution.