Skip to main content
OpenMetadata MCP in Action
Wednesay, Feb 25, 2026
Presented By
Alejandro Aboy, Erfan Hesami
OpenMetadata Monthly Community Meetup
Senior Data and AI Engineer | writer of The Pipe & the Line
Alejandro Aboy
About us
Erfan Hesami
Data Engineer and architect | writer of Pipelinetoinsights
thepipeandtheline
alejandro-aboy aboyalejandro
pipeline2insights
erfanhesami Hopefan
The New Stakeholders
Project Overview
OpenMetadata + MCP usecases
Impact Analysis
AI Readiness
Glossary Management
Airmaster Story
Agenda
The New Stakeholders
Consumer
Interface
Success Metric
Quality
Analysts, Decision
Makers
SQL, BI dashboards
"Dashboard loads?"
Correct types, no
nulls
AI agents, LLMs
Semantic layers,
MCP servers
"AI gives accurate
answers?"
Complete context,
AI readiness
BEFORE AFTER
The new stakeholders are AI systems or users reading AI outputs by those.
https://www.datagibberish.com/p/data-engineers-are-becoming-metadataops-engineers
Article link
Project Overview
Github Repo: https://github.com/aboyalejandro/agentic-data-modeling/blob/main/DEMO.md
Use Case 1: Impact Analysis on Schema Changes
Scenario:
Rename total_conversions in campaign_performance
What downstream models will break?
Which dashboards or reports are impacted?
Are there hidden dependencies we don’t know about?
/metadata-impact-analysis i need to rename
total_conversions from campaign_performance model,
can you check for downstream impact?
MCP:
Use Case 1: Impact Analysis on Schema Changes
Claude Code reviews dbt lineage, uses OpenMetadata MCP for further end to lineage
tracking and builds a report for impact analysis. Without the MCP, this change would
have silently break the linked dashboard on Metabase.
SKILL.md
Use Case 2: AI Readiness: Audit, Enrich and Validate
Scenario
Is the user_journey model ready to be consumed by an AI agent?
Can an AI understand this model correctly?
Are assumptions and edge cases documented?
Are there any ambiguous or vague definitions?
/metadata-ai-readiness
Is this model AI-ready?
MCP:
Use Case 2: AI Readiness: Audit, Enrich and Validate
Claude Code goes through dbt YAML files, checks OpenMetadata & PostgreSQL with
MCPs and proposes use cases, caveats and other AI readiness checks to document.
SKILL.md
Use Case 2: AI Readiness: Audit, Enrich and Validate
Upon approval, it will implement the changes to the YAMLs, and after re-ingestion
you will see the changes in OpenMetadata so next time they will be considered.
Note that
Use Case 3: Glossary Management
Scenario
Create a shared business glossary from existing dbt models
Do all teams mean the same thing by ROAS, CPA, or CTR?
Where is the official definition stored?
What does an AI agent use as the source of truth?
/metadata-glossary
Create a business glossary from our dbt models
MCP:
Use Case 3: Glossary Management
Claude Code goes through dbt YAML files and OpenMetadata glossary to
build a plan on new terms to add based on the business logic. Then it uses
the MCP tools to generate them directly.
SKILL.md
Before OpenMetadata (at Airmaster)
No data catalog
Knowledge locked in people
Slow and risky delivery
ERP migration risks
In Progress with OpenMetadata (What
Changed and Results)
Ownership defined
Who owns what,
who created it,
who to reach out
to.
Knowledge shared
No longer
dependent on 1–2
individuals
Context captured
once and reusable
Faster discovery Migration-ready
Visibility
into what to
migrate,
retire, or
preserve
AI-ready
Structured,
high-quality
metadata
supports MCP
and other AI
initiatives
spend less time on
data discovery and
more time on desiging
the system
thepipeandtheline.substack.com
Any question ?
pipeline2insights.substack.com