predict_impact

MCP tool from Memex by STiFLeR7

Given a file path, returns a ranked list of modules likely affected based on graph coupling (no LLM call)

How to use it

Project documentation lists predict_impact for the Memex MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), then check which tools your installed version makes available. Tool availability can depend on configuration and credentials. A server handshake does not verify this tool’s behavior. See the full listing for setup details.

Install Memex

$npx stifler-memex-mcp init --repo .

FULL MEMEX LISTING

Other tools in Memex (11)

explain_change

Given a commit SHA, cross-references the diff with linked Decision/Problem nodes and asks Gemini Pro for a grounded explanation

get_open_problems

Active bugs and tech debt, sorted by severity

get_project_context

Session start. Returns a cluster-level briefing under 1500 tokens regardless of repo size

get_recent_decisions

Last N days of architectural decisions, optionally module-scoped

get_stale_context

Edges whose composite confidence dropped below threshold

get_symbol_context

Before editing a function or class. Returns callers, callees, linked decisions

invalidate_edge

When a stored fact is no longer true

record_decision

After making a technical choice. Supports corroborates (reinforce) and supersedes (replace)

record_problem

When discovering a bug or piece of tech debt

resolve_problem

When a tracked problem is fixed

search_context

Hybrid search: semantic × keyword × graph traversal × RRF merge