Memoria

Name: Memoria
Author: byronwade

@byronwade

Repository

About Memoria

Prevents your AI from breaking code by revealing hidden file dependencies through git forensics.

#mcp #ai-code-assistant #git-forensics

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "memoria": {
      "command": "npx",
      "args": [
        "-y",
        "@byronwade/memoria"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Memoria?

Memoria is an MCP server that reveals hidden file dependencies in a codebase by analyzing git history, helping AI assistants avoid breaking code during refactoring. It targets developers using AI coding tools like Claude, Cursor, Windsurf, or Cline.

How to use Memoria?

Install via npx -y @byronwade/memoria and add the MCP server configuration to your AI tool (Claude Desktop, Cursor, etc.), then restart the tool. Ask your AI to use the analyze_file tool on any file before editing to get coupled files, risk scores, and stale dependencies.

Key features of Memoria

Volatility Engine – Tracks panic keywords with time-decay and bus factor.
Entanglement Engine – Finds files that change together >15% of the time.
Sentinel Engine – Detects stale dependencies (>7 days out of sync).
Static Import Engine – Finds explicit imports via git grep.
History Search (The Archaeologist) – Searches git history to understand why code was written.
100% local & private – No code uploaded, no API keys needed.

Use cases of Memoria

Refactor a file without accidentally breaking coupled, non-imported dependencies.
Assess the risk of modifying a file based on historical volatility and coupling.
Identify stale dependents that need updating before making changes.
Understand why a puzzling piece of code exists before deleting or modifying it.
Automatically check file forensics before every edit via auto-pilot rule files.

FAQ from Memoria

What makes Memoria different from static analysis tools?

Static analysis only finds explicit imports. Memoria uses git forensics to reveal implicit dependencies—files that change together even without imports.

Where does my code data go?

Memoria runs entirely on your machine. It reads your local .git folder directly; no code is uploaded to the cloud. Works offline and requires no API keys.