MCP.so
ログイン
M

Memoria

@byronwade

リポジトリ

Memoria について

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

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

基本情報

カテゴリ

その他

トランスポート

stdio

公開者

byronwade

投稿者

Byron Wade

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

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

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

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.

What dependencies or runtime are required?

You need Node.js and npm (to run npx) and git installed on your system. The server is published as an npm package @byronwade/memoria.

How do I verify Memoria is working?

After installation, ask your AI: "What MCP tools do you have available?" You should see analyze_file and ask_history in the list.

What transport protocol does Memoria use?

Memoria uses stdio MCP transport, as configured via the command and args fields in the MCP server JSON configuration.

コメント

「その他」の他のコンテンツ

Core Philosophy: Connect, Unify, Respond

mindsdb

Delegate anything. It comes back done.

39.4K

Codelf

unbug

A search tool helps dev to solve the naming things problem.

14.2K

Sequential Thinking

modelcontextprotocol

Model Context Protocol Servers

88.2K

🚀 Model Context Protocol (MCP) Curriculum for Beginners

microsoft

This open-source curriculum introduces the fundamentals of Model Context Protocol (MCP) through real-world, cross-language examples in .NET, Java, TypeScript, JavaScript, Rust and Python. Designed for developers, it focuses on practical techniques for building modular, scalable,

16.7K

MCP Toolbox for Databases

googleapis

MCP Toolbox for Databases is an open source MCP server for databases.

15.9K