Wiring Impact into Claude Code and Cursor with MCP

Your agent is about to edit a shared service. Does it know what breaks in the other three repos? With Impact's MCP server, it can ask before it writes a line.

We expose six tenancy-scoped tools over the Model Context Protocol: blast_radius, who_calls, contract_drift, health_forecast, risk, and a fused review_change.

Connect it

Open Agent Tools in the sidebar, copy the endpoint, and add it to your client's MCP config:

json
{ "mcpServers": { "impact-code-analysis": {
  "url": "https://api.impactcodeanalysis.com/api/v1/mcp",
  "headers": { "Authorization": "Bearer <your-token>" } } } }

Now your agent can call review_change before proposing a diff, and blast_radius before touching a shared endpoint. It's the grounding that a vector store can't give — a real dependency graph, not embeddings.