ripple
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@rippletriage "urn:li:dataset:(urn:li:dataPlatform:snowflake,prod.raw.orders_raw,PROD)""
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ripple
A triage tool for broken data tables in DataHub. Give it a table that's broken and it shows you:
every table, chart, and dashboard downstream that's affected
which of them matter most, and an overall severity (SEV1 to SEV3)
who owns them and should be told
Then it records the incident on the table in DataHub.
Try the online demo, no setup needed.
Requirements
A running DataHub (a local
datahub docker quickstartworks)Python 3.10+
A DataHub access token
Related MCP server: semley
Install
git clone https://github.com/chakri192/ripple.git
cd ripple
pip install -e .
cp .env.example .env # add your DataHub tokenTry it
Load a sample setup into DataHub (an orders table feeding five tables and three dashboards), then triage it:
python demo/seed_incident_demo.py
ripple triage "urn:li:dataset:(urn:li:dataPlatform:snowflake,prod.raw.orders_raw,PROD)" --no-write-backCommands
Command | |
| Find everything affected, rank it, and record the incident in DataHub |
| Report only, don't change DataHub |
| Also show which columns are affected |
| Also create a DataHub incident |
| Look upstream for where bad data probably came from |
| Watch for tables tagged |
| Open the dashboard at http://localhost:8000 |
Each triage prints a summary in the terminal and saves a Markdown report in examples/_scratch/.
Severity
SEV1: a dashboard or chart is affected (tag a dashboard
internalin DataHub if it isn't customer-facing)SEV2: something is affected, but nothing customer-facing
SEV3: nothing downstream is affected
What it changes in DataHub
Adds an
incidenttag to the broken tableAdds the incident report to the table's description, below anything already written there (running triage again replaces only the report)
With
--incident(and always inwatchmode), creates a DataHub incident
Use --no-write-back if you don't want DataHub changed at all.
Settings
In .env:
Variable | |
| DataHub address (default |
| Your access token |
| Optional. Writes a more readable report using Claude. Without it, a standard template is used |
License
Apache-2.0
Contributors
This server cannot be deployed
Maintenance
Related MCP Connectors
Cross-tool context for your data stack. Search, lineage, and impact across warehouse and BI tools.
- SuperlogOAuthsh.superlog
Open-source agent that observes and fixes your application. Query logs, traces, metrics, incidents.
AI agent run monitoring with incident replay and SLA receipts.
The grounded data layer for any LLM: governed SQL, metrics, lineage and catalog over your data.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI clients to automatically investigate dbt test failures, trace root cause through BigQuery lineage, and generate plain-English incident reports.1-
- AlicenseNot gradedqualityDmaintenanceEnables autonomous SRE incident investigation by allowing users to describe incidents in natural language. The agent follows a governed state machine to gather read-only evidence and produce grounded conclusions.MIT
- AlicenseAqualityCmaintenanceEnables agents to resolve data incidents by preparing remediation, inspecting verification results, and staging for human approval, while integrating with DataHub for evidence.5Apache 2.0
- AlicenseAqualityBmaintenanceAn on-call agent for data incidents, built on a bio-inspired context protocol. It triages data quality and freshness issues using DataHub, computing severity, blast radius, and ownership from the catalogue before generating prose.9Apache 2.0