---
title: "Debugging and Impact Analysis - Recording | Summer of MCP"
url: "https://atlan.com/summer-of-atlan-mcp-debugging-impact-analysis-recording/"
description: "Trace what broke and what's about to break, without spelunking through lineage UIs and Slack threads. Root-cause a broken dashboard and run impact analysis before you ship a change, in one prompt."
keywords: "Atlan MCP, impact analysis, data lineage, root-cause analysis, broken dashboard, blast radius, Model Context Protocol, data engineering, debugging data pipelines, Summer of MCP"
---

> Atlan is hosting Context Conference, bringing together the leaders and builders at the frontier of giving AI the context it needs to understand their business. It runs online on October 28, 2026, from 11:00 AM to 2:00 PM ET. Atlan co-founder Prukalpa Sankar opens and closes the day. Leaders from AstraZeneca, BNY and Verizon share why they invest in context and what they get from it. Registrants get early access to The AI Context Gap, a new study from MIT Technology Review Insights. Register: https://atlan.com/context-conference/

Recording of the Summer of MCP episode "Debugging and Impact Analysis" (EP 01 of the Build with Atlan MCP series). Trace what broke and what's about to break, without spelunking through lineage UIs and Slack threads. Root-cause a broken dashboard and run impact analysis before you ship a change, in one prompt.

- Recording: [Debugging and Impact Analysis on Vimeo](https://vimeo.com/1211304290) (uploaded 2026-07-16)
- Learn more: [Atlan MCP](https://atlan.com/mcp/)

## What you'll see

1. **Root-cause a broken dashboard.** Start from a real ticket: "the numbers look wrong." Atlan MCP walks upstream through lineage to the asset that caused it (a failed data quality check, a deprecated certification, a stale upstream table) and surfaces the owner. A multi-hour hunt becomes one prompt.
2. **Run impact analysis before you ship.** Before changing how a metric is calculated, Atlan MCP maps the blast radius downstream: every dashboard, model, and report that depends on it. You decide with evidence whether it's safe to ship, and exactly who needs a heads-up.
3. **A community member shows it in production.** Someone working in the same stack, with the same Monday-morning questions, walks through how their team actually uses this: the prompt they ran, what came back, and what it changed.
4. **Ship changes without the guesswork.** Blast-radius and root-cause questions stop being a half-day investigation. You leave knowing how to get the same answer, before you ship and after something breaks, without leaving your editor. That's the half-day back, and the confidence to make the call yourself.

## More from the series

- [Build Your Dashboard on Trusted Data (recording)](https://atlan.com/summer-of-atlan-mcp-dashboards-recording/)
- [Bring Context to Every Data Question](https://atlan.com/summer-of-atlan-mcp-data-discovery/)