In Memoria

me.pi22by7Published by pi22by7.mev0.5.8Updated Oct 24, 2026

Persistent codebase intelligence that gives AI assistants memory across sessions

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

In Memoria is a local MCP server that gives AI assistants persistent memory of a codebase across sessions.

What you can do
  • Provides persistent codebase intelligence so an assistant can recall a project's structure and context between sessions.
  • Keeps memory across sessions rather than rebuilding context each time.
  • Can use OpenAI embeddings when a key is supplied, otherwise falls back to local transformers.js embeddings.
  • Runs as a local stdio process on the user's machine; no tool list is published.
When to use it
Useful when you work with an assistant on the same codebase over many sessions and want it to retain project context instead of re-reading everything each time.
Requirements
Runs locally as an npm package (in-memoria) over stdio, so Node.js and a desktop MCP client are needed. Optionally set the OPENAI_API_KEY environment variable for OpenAI embeddings; without it, local transformers.js embeddings are used. No authentication is declared.
Before you install
The optional OPENAI_API_KEY is a secret; if set, code or text sent for embedding goes to OpenAI. Without it, embedding runs locally. The server indexes local source code, so consider what it stores on disk and whether that data is sensitive.

Installation

In SourceWeft

  1. Open In Memoria in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.5.8LatestSep 16, 2026

Score

15% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.