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.
@byronwade
Basic information
Prevents your AI from breaking code by revealing hidden file dependencies through git forensics.
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"memoria": {
"command": "npx",
"args": [
"-y",
"@byronwade/memoria"
]
}
}
}Returns forensic history, hidden dependencies, and risk assessment. USE THIS before modifying files.
Search git history for WHY code was written. IMPORTANT: Use SHORT, SPECIFIC KEYWORDS (e.g., 'serialization', 'race condition', 'timeout'). Do NOT use full sentences or long descriptions - they will return 0 results. Use when asking 'why does this exist?' or before removing code.
Get relevant memories and context before modifying a file. Returns memories, code graph relationships, and recent high-risk commits. Auto-saves critical discoveries when cloud is configured.
Save a lesson, context, or decision for future AI sessions. Use this when you discover important context that should be remembered.
Extract memories from code comments (IMPORTANT, WARNING, HACK, TODO, etc.). When cloud is configured, automatically saves high-confidence (>=70%) memories. Use to find and capture implicit knowledge in code.
Search extracted memories using BM25 keyword matching. FREE feature. Find relevant context from code comments using natural language queries.
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.
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.
git grep.Static analysis only finds explicit imports. Memoria uses git forensics to reveal implicit dependencies—files that change together even without imports.
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.
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`.
After installation, ask your AI: "What MCP tools do you have available?" You should see `analyze_file` and `ask_history` in the list.
Memoria uses stdio MCP transport, as configured via the `command` and `args` fields in the MCP server JSON configuration.
Open-source MCP to use Blender with any LLM
不止于 CSS

Handl speaks the Model Context Protocol. Your whole billing operation — projects, invoices, clients, reports, approvals — as tools any AI assistant can call, inside your autonomy rules.

B2B competitive intelligence, live sales battlecards, 5-axis ICP prospect fit scoring, and tech stack teardowns over MCP and REST with cited public-web evidence.
A search tool helps dev to solve the naming things problem.
Comments