get_impact_analysis

MCP tool from PhpCodeArcheology by PhpCodeArcheology

Impact analysis: what breaks if you change a method? Shows callers and call chains

How to use it

Project documentation lists get_impact_analysis for the PhpCodeArcheology 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 PhpCodeArcheology

$docker run --rm -v "$(pwd)":/project -v "$(pwd)/report":/output phpcodearcheology /project
FULL PHPCODEARCHEOLOGY LISTING

Other tools in PhpCodeArcheology (10)

get_class_list

All classes with key metrics, sortable and filterable

get_dependencies

Class dependency analysis (incoming/outgoing)

get_graph

Knowledge graph as JSON (nodes, edges, cycles)

get_health_score

Overall code health score, grade, and project statistics

get_hotspots

Git hotspots ranked by churn × complexity

get_metrics

Detailed metrics for a specific class, file, or function

get_problems

Code quality problems, filterable by severity and type

get_refactoring_priorities

Ranked refactoring candidates with recommendations

get_test_coverage

Test coverage summary — tested/untested classes, coverage gaps, test mapping

search_code

Search entities by name with metric overview