Memoria — Deterministic AI Memory & Code Intelligence MCP

● Active

io.github.kolivritech/memoria-mcp

Official Node.js MCP connector for Memoria Cloud (https://memoria.kolivri.com).

Connect this server

One click to install, or copy the config below. Suits: Claude Desktop · Cursor.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "memoria-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@kolivri/memoria-mcp@1.0.2"
      ],
      "env": {
        "MEMORIA_API_KEY": "<your MEMORIA_API_KEY>"
      }
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add --env MEMORIA_API_KEY='<your MEMORIA_API_KEY>' --transport stdio memoria-mcp -- npx -y @kolivri/memoria-mcp@1.0.2
OpenAI Codex CLI
codex mcp add memoria-mcp --env MEMORIA_API_KEY='<your MEMORIA_API_KEY>' -- npx -y @kolivri/memoria-mcp@1.0.2
VS Code
code --add-mcp '{"name":"memoria-mcp","type":"stdio","command":"npx","args":["-y","@kolivri/memoria-mcp@1.0.2"],"env":{"MEMORIA_API_KEY":"<your MEMORIA_API_KEY>"}}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in.

Environment variables
  • MEMORIA_API_KEYrequiredsecretMemoria Cloud API key from https://memoria.kolivri.com/register

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Developer Tools
Version
1.0.2
Registry
active
Published
11/19/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 22, 2026

Looks healthy: Memoria — Deterministic AI Memory & Code Intelligence MCP is maintained, open source, hosted endpoint answering without a key.

Maintained
Active
Last commit today (Nov 21, 2026), 0 open issues.
Official registry
Active
Published as io.github.kolivritech/memoria-mcp in the official MCP registry, version 1.0.2.
Source
Open source, MIT
Public repository under the MIT licence, 0 stars, 0 forks.
Runs
Local package or hosted
Ships as a local package (npm) that runs on your machine, and as a hosted endpoint at memoria.kolivri.com that receives what your client sends it.
Credentials
None needed to connect
The hosted endpoint completed the Serverdex initialize + tools/list handshake with no key (checked Nov 22, 2026); individual tools may still ask for one.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself and see the status history.

Live check

checked Nov 22, 2026, 08:08 UTCStatus history & uptime →
● Working519 msprotocol 2025-06-18v1.0.0toolspromptsresources

The endpoint answered the MCP handshake as "memoreal" and listed 14 tools. Answering since Nov 18, 2026.

Context cost ≈ 5k tokens of tool definitions a client loads per conversation (estimate: characters ÷ 4) across 14 tools.

Tools (14)

  • encode_memory5 params

    Store a single memory record in Memoreal Cloud (consumes 1 Write API call; non-idempotent: encoding identical text twice creates separate IDs until consolidate is run) and return { id, namespace, salience }. Defaults type to "episodic", salience to 0.5 (items >=0.7 or semantic/core surface in memory://rules), and namespace to "default" while rejecting reserved "org:" prefixes. Use when persisting one architectural decision, bug root cause, or user rule; use batch_encode instead for 2+ memories at once, or handoff_to_agent for cross-wing task handoffs.

    Show parameters
    • namespacestringrequiredLogical project or workspace namespace (defaults to "default"; never prefix with "org:").
    • contentstringrequiredNon-empty memory text to persist.
    • typestringMemory tier classification (core and semantic receive 1.5x/1.25x recall boosts).
    • saliencenumberImportance weight from 0.0 to 1.0 (use >=0.7 for durable team rules).
    • contextarrayOptional [key, value] string pairs (for example [["file", "src/auth.js"]]) targetable by delete_by_context.
  • batch_encode2 params

    Store multiple memories atomically in one request (consumes max(1, memories.length) Write API calls; non-idempotent) and return { ids, encoded }. Validates every item namespace before writing so any reserved "org:" prefix aborts the entire batch cleanly; items inherit top-level namespace and default to type="episodic" and salience=0.5. Use when checkpointing or importing 2+ memories together; use encode_memory instead for a single memory write.

    Show parameters
    • namespacestringFallback logical workspace namespace applied to batch items that omit namespace.
    • memoriesarrayrequiredNon-empty array of memory objects ({ content, type?, salience?, namespace?, context? }).
  • recall_memories4 params

    Retrieve up to 20 deterministically ranked memory records for a query (read-only, idempotent; consumes 1 Read API call) and return { results, total_candidates } with per-item { memory, score }. Scores up to 500 candidates in namespace by lexical match (0.55), salience (0.30), and 30-day freshness (0.15) multiplied by tier boost (core=1.5x, semantic=1.25x), excluding items below min_salience. Use when you need individual memory IDs, metadata, or scores (for inspection, feedback, or forget_memory); use build_context instead for a ready-to-inject <memory_context> block, or search_code for code symbols.

    Show parameters
    • namespacestringrequiredLogical workspace namespace to search (defaults to "default"; never prefix with "org:").
    • querystringrequiredKeywords or natural-language topic to match against stored memory content.
    • token_budgetnumberAdvisory token budget hint for downstream context sizing (default 4096).
    • min_saliencenumberMinimum salience filter (0.0-1.0); memories strictly below this value are excluded.
  • build_context3 params

    Assemble a token-budgeted <memory_context> XML/Markdown block from a namespace (read-only, idempotent; consumes 1 Read API call) and return { context, memories_used }. Ranks up to 500 namespace memories deterministically and packs lines greedily up to max(256, token_budget * 4) characters under "## Established Facts" (core/semantic) and "## Recent Context" (episodic/buffer). Use at session start or before planning a task to ground the model in one call; use recall_memories instead when you need raw memory objects and IDs.

    Show parameters
    • namespacestringrequiredLogical workspace namespace to ground context around (never prefix with "org:").
    • querystringrequiredActive task, feature, or session topic used to rank relevant facts and history.
    • token_budgetnumberMaximum token budget (~4 characters per token, default 4096) before truncating lower-ranked items.
  • forget_memory1 param

    Permanently delete one memory and its incident graph edges by ID (destructive, idempotent; consumes 1 Write API call) and return { deleted }. Enforces organization ownership (returns JSON-RPC error -32003 on foreign IDs) and returns { deleted: false } when the ID is already absent. Use when removing a single known memory ID; use delete_by_context instead to bulk-delete memories by [key, value] metadata tag, or feedback (useful=false) to lower salience without deleting.

    Show parameters
    • idstringrequiredExact memory UUID returned by encode_memory or recall_memories.
  • delete_by_context3 params

    Permanently bulk-delete all memories whose context array contains an exact [key, value] pair (destructive, idempotent; consumes 1 Write API call) and return { deleted_count }. Scopes deletion to namespace when provided, or across all namespaces in your organization when namespace is omitted (rejecting reserved "org:" prefixes). Use to purge memories tied to a deleted file, PR, or feature tag; use forget_memory instead when deleting a single memory by UUID.

    Show parameters
    • namespacestringOptional logical namespace filter; omit to match across the entire organization.
    • keystringrequiredExact context tuple key to match (for example "file" or "pr").
    • valuestringrequiredExact context tuple value to match (for example "src/legacy.js").
  • feedback2 params

    Adjust a memory salience weight based on recall utility (consumes 1 Write API call; non-idempotent because repeated calls compound the salience delta) and return { updated }. Enforces organization ownership on id; useful=true boosts salience toward 1.0 while useful=false dampens noisy or outdated entries without deleting them. Use after recall_memories to tune future ranking quality; use forget_memory instead for permanent removal, or consolidate to merge duplicate records.

    Show parameters
    • idstringrequiredTarget memory UUID from recall_memories.
    • usefulbooleanrequiredTrue to boost salience when helpful; false to dampen salience when stale or noisy.
  • consolidate1 param

    Run an idempotent maintenance pass on a workspace namespace to deduplicate redundant records, link superseded state, and promote recurring high-salience episodic memories to Semantic tier (consumes 1 Write API call; non-destructive to unique facts) and return { namespace, consolidated }. Requires Write permission and a valid logical namespace (never prefixed with "org:"). Use at session wrap-up after multiple encode_memory calls; use feedback instead to rate one memory, or delete_by_context to purge obsolete tags.

    Show parameters
    • namespacestringrequiredLogical workspace namespace to consolidate (for example "my-project").
  • health

    Check Memoreal Cloud service status, total organization memory count across all namespaces, and rolling 30-day API quota usage (read-only, idempotent; consumes 1 Read API call on tools/call) and return { status, memory_count, used_calls_30d, api_call_limit }. Takes no parameters; api_call_limit is null on Unlimited plans. Use to verify connectivity and overall organization quota headroom; use stats instead when you need memory counts scoped to one specific project namespace.

  • stats1 param

    Retrieve the stored memory count for a single logical namespace alongside rolling 30-day organization quota metrics (read-only, idempotent; consumes 1 Read API call) and return { namespace, memory_count, used_calls_30d, api_call_limit }. Rejects reserved "org:" prefixes on namespace. Use when inspecting how many memories exist inside one specific project or wing namespace; use health instead for an organization-wide connectivity and total-memory check, or list_agent_wings for per-wing counts.

    Show parameters
    • namespacestringrequiredLogical workspace namespace to inspect (for example "my-project" or "wing:qa").
  • search_code2 params

    Search indexed code symbol definitions, file paths, and reference memories within a namespace (read-only, idempotent; consumes 1 Read API call) and return { results, total_candidates } capped at 20 ranked { memory, score } hits. Requires code memories in namespace (populated via /memoreal-sync-code or encode_memory) and rejects reserved "org:" prefixes. Use to discover where functions, classes, or routes live by keyword; use explain_code instead to inspect callers and invariants of a known symbol, or recall_memories for general prose rules.

    Show parameters
    • namespacestringrequiredLogical repository or workspace namespace to search (never prefix with "org:").
    • querystringrequiredFunction, class, route, or file keyword to locate.
  • explain_code3 params

    Synthesize definitions, caller/callee references, related tests, and architectural notes for a specific code symbol in a namespace (read-only, idempotent; consumes 1 Read API call) and return { results, total_candidates } (up to 20 ranked matches). Pass the identifier via symbol or its equivalent alias target (if both are supplied, symbol takes precedence). Use before editing a known function, class, or module to check its blast radius and invariants; use search_code instead when you only have keywords and need to find symbol names first.

    Show parameters
    • namespacestringrequiredLogical repository or workspace namespace containing indexed code memories.
    • symbolstringExact function, class, or module name to explain (preferred; equivalent to target).
    • targetstringAlias for symbol accepted for client compatibility when symbol is omitted.
  • list_agent_wings1 param

    List all five built-in specialist multi-agent wings (architect, reviewer, qa, security, ops), their isolated wing:<id> namespaces, and active memory counts (read-only, idempotent; consumes 1 Read API call) and return { wings }. Always returns all five wings even when memory_count is 0. Use to inspect wing responsibilities and queued handoff volume before delegating work; use handoff_to_agent to record a new cross-wing handoff, or stats to inspect a custom project namespace.

    Show parameters
    • namespacestringOptional logical workspace namespace context (never prefix with "org:").
  • handoff_to_agent8 params

    Persist a high-salience (0.9) Semantic handoff memory into a target specialist wing namespace (wing:<target>) (consumes 1 Write API call; non-idempotent: repeated calls create distinct handoff records) and return { id, wing, namespace }. Accepts target wing via wing or alias to_wing (defaults to "architect") and sender via from_agent or alias from_wing (defaults to "agent"), attaching files and memory_ids as searchable context tuples. Use when delegating findings and next steps between architect, reviewer, qa, security, or ops agents; use encode_memory instead for general project memories.

    Show parameters
    • wingstringDestination specialist wing (preferred; defaults to "architect" if both wing and to_wing are omitted).
    • to_wingstringAlias for destination wing used when wing is omitted.
    • from_agentstringIdentifier of the sending agent or role (preferred; defaults to "agent").
    • from_wingstringAlias for sending specialist wing used when from_agent is omitted.
    • summarystringrequiredRequired concise summary of architectural findings, constraints, and state.
    • taskstringOptional concrete follow-up action appended for the receiving wing.
    • filesarrayOptional file paths attached as ["file", path] context tags.
    • memory_idsarrayOptional related memory UUIDs attached as ["memory_id", id] context tags.

Checked by Serverdex with a plain initialize + tools/list call to memoria.kolivri.com/v1/mcp, no credentials, about once a day. A failed check is never a removal.

On GitHub

read Nov 22, 2026
Stars
0
Forks
0
Last push
Nov 21, 2026
License
MIT

JavaScript

From the README

@kolivri/memoreal-mcp — Deterministic AI Memory & Code Intelligence MCP for Claude Code, OpenCode, Cursor & Claude Desktop @kolivri/memoreal-mcp is the official zero-dependency Node.js ESM Model Context Protocol (MCP) connector (stdio & HTTP) for Memoreal Cloud — giving AI coding and operator agents (Claude Code, OpenCode, Cursor, Windsurf, VS Code, Cline, Roo Code, Zed, Goose, and Claude Desktop) deterministic long-term memory, cross-session recall, and code intelligence powered by memoreal.kolivri.com. • Memoreal Cloud Portal & API Keys: https://memoreal.kolivri.com (Get API Key — includes 1,000 free API calls/memories; paid tiers: Developer $19/mo, Startup $79/mo, Business $299/mo) • Documentation & Benchmarks: https://memoreal.kolivri.com/docs (500/500 = 100.0% LongMemEval at 12.9 ms p50, 102/102 = 100.0% Hebrew LongMemEval across 15 languages) • Support: stas@kolivri.com · WhatsApp 054-787-5670 Environment Variables Backward Compatibility: Legacy MEMORIAAPIKEY, MEMORIAAPIURL, and MEMORIA_NAMESPACE environment variables remain 100% supported as automatic fallbacks across all transports. Installation 1. One-Line Auto-Installer (15 AI Clients + Claude Code Lifecycle Hooks) Automatically configures Claude Code, Cursor, Windsurf, VS Code, Claude Desktop, OpenCode, Cline, Roo Code, Continue, Zed, Goose, PearAI, Trae, Void, and Melty: 2. Claude Code (claude mcp add) 3. Cursor (~/.cursor/mcp.json) & Claude Desktop (claudedesktopconfig.json) 4.…

Read the full README on GitHub →

Remotes

  • streamable-httphttps://memoria.kolivri.com/v1/mcp

Alternatives to Memoria — Deterministic AI Memory & Code Intelligence MCP

All Memoria — Deterministic AI Memory & Code Intelligence MCP alternatives →Best Developer Tools servers →

The most-starred Developer Tools servers in the index, with their live-check result.

ServerStarsLast pushLive check
REA466,935Nov 2026Local / not checked
GitHub34,658Nov 2026Needs sign-in
Repomix29,280Nov 2026Local / not checked
Compiler Explorer19,201Nov 2026Working
XERJ19,135Nov 2026Local / not checked

Memoria — Deterministic AI Memory & Code Intelligence MCP: questions people ask

Is Memoria — Deterministic AI Memory & Code Intelligence MCP a remote or a local MCP server?
According to its entry in the official MCP registry, Memoria — Deterministic AI Memory & Code Intelligence MCP ships as a hosted endpoint (streamable-http) that your client connects to by URL and as a local package (npm) that your client starts on your machine. Use the hosted endpoint when your client supports Streamable HTTP; use the package when you want it to run locally.
Does Memoria — Deterministic AI Memory & Code Intelligence MCP need an API key?
Its hosted endpoint completed the Serverdex live check — an MCP initialize + tools/list call — with no credentials on Nov 22, 2026. Individual tools may still ask for a key when called.
Is Memoria — Deterministic AI Memory & Code Intelligence MCP safe to use?
Looks healthy: Memoria — Deterministic AI Memory & Code Intelligence MCP is maintained, open source, hosted endpoint answering without a key. In detail — maintained: Active; official registry: Active; source: Open source, MIT; runs: Local package or hosted; credentials: None needed to connect. Serverdex check of Nov 22, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is Memoria — Deterministic AI Memory & Code Intelligence MCP still maintained?
Active: the repository's last commit today. Last push Nov 21, 2026, 0 GitHub stars, MIT licence. Read from GitHub on Nov 22, 2026.
What tools does Memoria — Deterministic AI Memory & Code Intelligence MCP expose?
14 tools as listed by the server itself during the live check, including encode_memory, batch_encode, recall_memories, build_context, forget_memory. The full list with parameters is in the Live check section above.
How do I add Memoria — Deterministic AI Memory & Code Intelligence MCP to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
Browse all Developer Tools →

Add the badge to your site

Show visitors that Memoria — Deterministic AI Memory & Code Intelligence MCP is listed here — it’s also the link we check for a free listing.

Memoria — Deterministic AI Memory & Code Intelligence MCP — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-kolivritech-memoria-mcp?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="Memoria — Deterministic AI Memory & Code Intelligence MCP — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![Memoria — Deterministic AI Memory & Code Intelligence MCP — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-kolivritech-memoria-mcp?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Add to CursorAdd to VS CodeOpen in Claude Code

Install buttons — for your README

[![Add to Cursor](https://serverdex.io/brand/install-cursor.svg)](https://serverdex.io/install/cursor/io-github-kolivritech-memoria-mcp) [![Add to VS Code](https://serverdex.io/brand/install-vscode.svg)](https://serverdex.io/install/vscode/io-github-kolivritech-memoria-mcp) [![Open in Claude Code](https://serverdex.io/brand/install-claude-code.svg)](https://serverdex.io/install/claude-code/io-github-kolivritech-memoria-mcp)

One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.

Install buttons — HTML for your docs

<a href="https://serverdex.io/install/cursor/io-github-kolivritech-memoria-mcp"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/io-github-kolivritech-memoria-mcp"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/io-github-kolivritech-memoria-mcp"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>

Same buttons as plain links for a docs page or website.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).