← Lab
💾 mem
CLIClaudeRAGKnowledge 2026

mem

Save Claude memories as team knowledge

A CLI that turns the memory notes Claude writes during your work into a searchable, deduplicated knowledge base your whole team — and Claude — can query later. Part of AI Documents, our RAG platform for developer & customer chat over your docs.

Visit live site →

mem is a command-line tool for developers who work inside Claude. As Claude writes memory notes during your sessions, mem pushes them into a shared, searchable knowledge base — so the next question, yours or Claude’s, is answered from what your team has already figured out.

What you can do

  • mem save — analyze your Claude memory files and store them as developer knowledge (auto-titled, summarized, and classified)
  • mem search "…" — semantic search across everything you’ve saved
  • No duplicates — saving the same topic updates the existing entry instead of piling up
  • mem install — wire the developer & customer chat servers into Claude Code, Cursor, or claude.ai
  • Roles — admins create users and API keys from the CLI; developers just save and search

Install

curl -fsSL https://api-docs.innyalabs.com/install.sh | bash

Works behind a VPN/proxy, so it runs even on restricted networks.

Tech

Node + TypeScript CLI over an Express API, Postgres (Neon), and a Pinecone vector store, with MCP servers so any Claude client can read the knowledge. Part of the AI Documents platform, deployed on a Hostinger VPS.

Updates

What's shipping, what's fixed, what's next.

  1. mem CLI is live

    Turn the memories Claude writes during your work into searchable team knowledge. Install with one curl command, then just `mem save` and `mem search`.

    mem is now available — a CLI that turns Claude’s working memory into a searchable knowledge base your team and Claude can query later.

    Install

    curl -fsSL https://api-docs.innyalabs.com/install.sh | bash

    What shipped

    • mem save — analyzes your Claude memory files, then summarizes, titles, and classifies each one before storing it as developer knowledge
    • mem search "…" — semantic search across everything saved
    • No duplicates — re-saving the same topic updates the existing entry instead of creating a copy
    • Roles — admins create developers and API keys straight from the CLI; developers are limited to save/search
    • mem install — adds the developer & customer chat servers to Claude Code, Cursor, or claude.ai
    • Proxy aware — works behind a VPN/proxy, so it runs on restricted networks too

    Why this matters

    Developers using Claude were losing hard-won context to chat history. mem keeps it in one searchable place, so the next question is answered from what the team already learned — and Claude can pull it back automatically through MCP.

    What’s next

    • Auto-save on a schedule
    • Semantic dedup (same topic, different wording)
    • A web view of the team knowledge base