[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-71252":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":17,"stars7d":18,"stars30d":19,"stars90d":16,"forks30d":16,"starsTrendScore":20,"compositeScore":21,"rankGlobal":10,"rankLanguage":10,"license":22,"archived":23,"fork":23,"defaultBranch":24,"hasWiki":25,"hasPages":23,"topics":26,"createdAt":10,"pushedAt":10,"updatedAt":47,"readmeContent":48,"aiSummary":49,"trendingCount":16,"starSnapshotCount":16,"syncStatus":50,"lastSyncTime":51,"discoverSource":52},71252,"OpenMetadata","open-metadata\u002FOpenMetadata","open-metadata","The Open Context Layer for Data and AI ,  OpenMetadata is the open platform for building trusted data context and business semantics for humans, AI assistants, and agents.","https:\u002F\u002Fopen-metadata.org",null,"TypeScript",14157,2155,56,578,0,37,93,274,111,120,"Apache License 2.0",false,"main",true,[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"context","context-layer","data-catalog","data-collaboration","data-contracts","data-discovery","data-governance","data-lineage","data-observability","data-profiling","data-quality","data-quality-checks","datadiscovery","dataengineering","dataquality","mcp","mcp-server","metadata","metadata-management","semantics","2026-06-12 04:01:00","\u003Cbr \u002F>\u003Cbr \u002F>\n\u003Cp align=\"center\">\n    \u003Ca href=\"https:\u002F\u002Fopen-metadata.org\">\n        \u003Cimg alt=\"Logo\" src=\"https:\u002F\u002Fgithub.com\u002Fopen-metadata\u002FOpenMetadata\u002Fassets\u002F40225091\u002Fe794ced8-7220-4393-8efc-3faf93bfb503\" width=\"49%\">\n    \u003C\u002Fa>\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\u003Cb>Empower your Data Journey with OpenMetadata\u003C\u002Fb>\u003C\u002Fp>\n\n\u003Cdiv align=\"center\">\n    \n![Commit Activity](https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Fcommit-activity\u002Fm\u002Fopen-metadata\u002FOpenMetadata?style=for-the-badge)\n[![Release](https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Frelease\u002Fopen-metadata\u002FOpenMetadata\u002Fall.svg?style=for-the-badge)](https:\u002F\u002Fgithub.com\u002Fopen-metadata\u002FOpenMetadata\u002Freleases)\n\n\u003C\u002Fdiv>\n\n# OpenMetadata\n\n## The Open Semantic Context Platform for Data and AI\n\nOpenMetadata is the open platform for building trusted data context and business semantics for humans, AI assistants, and agents.\n\nOpenMetadata connects technical metadata, data quality signals, data lineage, column-level lineage, ownership, usage, policies, conversations, glossaries, classifications, metrics, domains, and data products into a unified metadata knowledge graph. With 120+ connectors, open metadata standards, semantic search, APIs, SDKs, and an MCP server, OpenMetadata gives every user and AI system the governed context it needs to discover, understand, trust, and use data.\n\nAI does not need another raw database connector. AI needs context.\n\nOpenMetadata provides that context:\n\n- what data exists\n- what it means\n- who owns it\n- how it is used\n- where it came from\n- where it flows\n- whether it is fresh, tested, and trusted\n- which business concepts, glossary terms, classifications, and policies apply\n- what downstream assets, dashboards, pipelines, metrics, and ML models depend on it\n\n---\n\n## Contents\n\n- [Why OpenMetadata for AI?](#why-openmetadata-for-ai)\n- [Context: Give AI the Full Picture of Your Data](#context-give-ai-the-full-picture-of-your-data)\n- [Semantics: Give AI Business Meaning](#semantics-give-ai-business-meaning)\n- [Knowledge Graphs and Ontologies](#knowledge-graphs-and-ontologies)\n- [Automation: Activate Context and Semantics with AI](#automation-activate-context-and-semantics-with-ai)\n- [What You Can Build](#what-you-can-build)\n- [How OpenMetadata Works](#how-openmetadata-works)\n- [MCP: Connect AI Assistants and Agents](#mcp-connect-ai-assistants-and-agents)\n- [Semantic Search](#semantic-search)\n- [OpenMetadata Standards](#openmetadata-standards)\n- [Core Platform Capabilities](#core-platform-capabilities)\n- [Quickstart](#quickstart)\n- [Documentation and Community](#documentation-and-community)\n- [Contributing](#contributing)\n- [License](#license)\n\n---\n\n## Why OpenMetadata for AI?\n\nAI needs more than data access. It needs context, semantics, trust, lineage, governance, and operational awareness.\n\nConnecting an AI assistant directly to a database, warehouse, dashboard, or pipeline only gives it raw access to data structures. It does not give the AI enough context to understand what the data means, whether it can be trusted, who owns it, how it is governed, or what downstream systems depend on it.\n\nOpenMetadata gives AI systems the context and semantics they need to safely discover, understand, govern, and use enterprise data.\n\nOpenMetadata does this by combining four capabilities:\n\n1. **Context** — technical, operational, trust, and lineage metadata from the data ecosystem.\n2. **Semantics** — business meaning through glossaries, metrics, classifications, domains, policies, and ontologies.\n3. **Knowledge Graph** — relationships connecting assets, columns, people, teams, policies, lineage, quality, and business concepts.\n4. **Automation** — MCP, Semantic Search, APIs, SDKs, events, and workflows that let AI assistants and agents act on governed metadata.\n\nWith OpenMetadata, AI can answer questions such as:\n\n- What does this metric mean?\n- Which datasets power this dashboard?\n- Who owns this data product?\n- Is this dataset certified, fresh, and high quality?\n- What downstream dashboards or ML models are affected by this column change?\n- Which assets are related to customer purchase behavior, even if they use different names?\n- Which columns contain sensitive customer information?\n- Which glossary terms and business concepts apply to this dataset?\n\n---\n\n## Context: Give AI the Full Picture of Your Data\n\nContext is the metadata that describes how data exists, behaves, changes, flows, and is used across the organization.\n\nOpenMetadata collects context from across your data stack and connects it into a unified metadata graph.\n\n### Technical Metadata\n\nOpenMetadata gives AI access to technical metadata such as:\n\n- databases, schemas, tables, columns, topics, dashboards, charts, pipelines, APIs, search indexes, ML models, and storage assets\n- schemas, column names, data types, constraints, descriptions, sample queries, joins, and service metadata\n- service configuration, ingestion metadata, and operational metadata\n- owners, teams, users, personas, domains, data products, and usage patterns\n\n### Data Quality and Trust Signals\n\nAI should not treat every dataset as equally trustworthy.\n\nOpenMetadata gives AI access to trust signals such as:\n\n- data quality tests\n- test suites and test results\n- freshness checks\n- volume checks\n- null, uniqueness, distribution, and custom tests\n- profiling results\n- observability signals\n- data quality history\n- incidents, alerts, and operational health signals\n\n### Data Lineage and Impact\n\nAI needs to understand where data comes from and where it goes.\n\nOpenMetadata captures:\n\n- upstream and downstream lineage\n- table-level lineage\n- dashboard lineage\n- pipeline lineage\n- metric lineage\n- ML model lineage\n- API and topic dependencies\n- impact analysis across the data estate\n\n### Column-Level Lineage\n\nFor precise AI reasoning, table-level lineage is not enough.\n\nOpenMetadata helps AI understand:\n\n- which source columns produce which downstream columns\n- how columns flow through transformations\n- which dashboards, reports, metrics, or ML models depend on a specific column\n- what may break when a column changes\n\n### Connected from 120+ Data Services\n\nOpenMetadata brings this context together from databases, warehouses, lakes, dashboards, pipelines, messaging systems, ML platforms, storage systems, APIs, search systems, and metadata systems.\n\nContext answers questions like:\n\n- What data exists?\n- Where did this data come from?\n- Who owns it?\n- Is it fresh?\n- Is it tested?\n- Is it trusted?\n- What systems depend on it?\n- What happens if it changes?\n\n---\n\n## Semantics: Give AI Business Meaning\n\nSemantics is the business meaning layered on top of technical context.\n\nWithout semantics, AI may see a column named `cust_id`, `acct_id`, or `buyer_key`, but it may not know whether those fields represent a customer, an account, a buyer, a household, or a legal entity.\n\nOpenMetadata lets teams define, govern, and connect business meaning across the metadata graph.\n\n### Business Concepts\n\nDefine the concepts that matter to the business, such as:\n\n- Customer\n- Account\n- Order\n- Revenue\n- Product\n- Consent\n- Churn\n- Risk\n- Lifetime Value\n- Net Retention\n- Active User\n- Sensitive Data\n\n### Glossaries and Glossary Terms\n\nOpenMetadata lets teams create governed vocabularies with:\n\n- business definitions\n- synonyms and abbreviations\n- owners and reviewers\n- related terms\n- hierarchical terms\n- links to tables, columns, dashboards, metrics, and data products\n\n### Metrics and KPIs\n\nMetrics are one of the most important semantic objects for AI.\n\nOpenMetadata helps AI understand:\n\n- what a metric means\n- how it is calculated\n- who owns it\n- which dashboards use it\n- which tables power it\n- which glossary terms define it\n- which downstream consumers depend on it\n\n### Classifications and Tags\n\nOpenMetadata lets teams classify and label data with governed tags such as:\n\n- PII\n- Sensitive\n- Confidential\n- Certified\n- Deprecated\n- Tier 1\n- Finance\n- Marketing\n- GDPR\n- HIPAA\n- SOX\n- ML Feature\n- Customer Data\n\n### Domains and Data Products\n\nOpenMetadata connects assets to business ownership boundaries through:\n\n- domains\n- data products\n- teams\n- owners\n- policies\n- personas\n- data product consumers\n\n### Policies and Governance\n\nOpenMetadata connects semantics to governance so AI systems can reason with policy-aware context, not just metadata.\n\nThis includes:\n\n- ownership\n- stewardship\n- classification\n- access control context\n- certification\n- review workflows\n- governance policies\n- lifecycle states\n\nSemantics answers questions like:\n\n- What does this data mean?\n- What business concept does this column represent?\n- Is this metric officially defined?\n- Is this asset certified?\n- Is this data sensitive?\n- Which glossary terms apply?\n- Which domain owns this data product?\n\n---\n\n## Knowledge Graphs and Ontologies\n\nOpenMetadata connects context and semantics into a unified metadata knowledge graph.\n\nThe graph does not just store data assets. It stores the relationships between data assets, people, teams, policies, quality tests, lineage, classifications, glossary terms, metrics, domains, and data products.\n\nThis makes OpenMetadata a semantic context layer for AI.\n\nExample relationships:\n\n```text\nTable ──hasColumn────────────> Column\nColumn ──classifiedAs────────> PII\nColumn ──represents──────────> Customer Identifier\nTable ──ownedBy──────────────> Data Engineering Team\nTable ──partOf───────────────> Customer 360 Data Product\nDashboard ──dependsOn────────> Table\nMetric ──definedBy───────────> Glossary Term\nPipeline ──produces──────────> Table\nColumn ──flowsTo─────────────> Column\nTest Case ──validates────────> Table\nDomain ──contains────────────> Data Product\nGlossary Term ──relatedTo────> Business Concept\nPolicy ──governs─────────────> Classification\n```\n\nWith this graph, AI can reason across relationships:\n\n- Which datasets power this dashboard?\n- What does this metric mean?\n- Who owns this data product?\n- Is this table fresh, certified, and high quality?\n- Which downstream dashboards or ML models are affected by this column change?\n- Which assets are related to customer purchase behavior, even if they use different names?\n- Which columns represent sensitive customer information?\n- Which business concepts are connected to this data product?\n\n### Ontologies and Semantic Interoperability\n\nOpenMetadata is built on open metadata standards.\n\n[OpenMetadata Standards](https:\u002F\u002Fopenmetadatastandards.org\u002F) provides schemas, ontologies, and semantic specifications for interoperable metadata management, including:\n\n- JSON Schemas for metadata entities, APIs, configurations, events, and relationships\n- RDF\u002FOWL ontologies for semantic web, linked data, and knowledge graph use cases\n- SHACL shapes for validation\n- JSON-LD contexts for semantic interoperability\n- standards for governance, lineage, quality, observability, teams, users, policies, and events\n\nThese standards make OpenMetadata more than a catalog. They make it a foundation for interoperable semantic metadata, linked data, and enterprise knowledge graphs.\n\n---\n\n## Automation: Activate Context and Semantics with AI\n\nOpenMetadata makes the metadata graph actionable.\n\nAI assistants, coding agents, data teams, governance teams, and applications can use OpenMetadata through:\n\n- MCP\n- Semantic Search\n- APIs\n- SDKs\n- events\n- webhooks\n- ingestion workflows\n- metadata applications\n\n### MCP Server\n\nOpenMetadata includes an MCP server that lets AI assistants and MCP-compatible clients interact with the metadata graph through natural language.\n\nWith OpenMetadata MCP, AI assistants can:\n\n- search metadata\n- run semantic search\n- retrieve entity details\n- inspect upstream and downstream lineage\n- create glossaries and glossary terms\n- create lineage\n- update descriptions, tags, owners, and other metadata\n- list data quality test definitions\n- create data quality test cases\n- analyze root causes of data quality failures\n\nGet started with MCP:\n[OpenMetadata MCP Server Documentation](https:\u002F\u002Fdocs.open-metadata.org\u002Fhow-to-guides\u002Fmcp)\n\n### Semantic Search\n\nSemantic Search lets users and AI assistants search by meaning, not just by exact keywords.\n\nFor example, a user can ask:\n\n> Find tables related to customer purchase behavior and transaction history.\n\nOpenMetadata can return conceptually related assets even when the exact words in the query do not appear in the asset names.\n\nThis helps AI answer questions such as:\n\n- Which datasets are related to customer behavior?\n- What dashboards do we have for revenue forecasting?\n- Show me assets related to user engagement metrics.\n- Find pipelines that process financial compliance data.\n\n### AI SDK\n\nDevelopers can use OpenMetadata’s AI SDK to build custom AI applications that use OpenMetadata MCP tools programmatically.\n\nThe AI SDK enables AI applications to use OpenMetadata context from Python, TypeScript, and Java.\n\n### APIs, Events, and Webhooks\n\nOpenMetadata exposes APIs, events, and webhooks so teams can automate metadata workflows across their data ecosystem.\n\nUse them to:\n\n- ingest and update metadata\n- react to metadata changes\n- trigger governance workflows\n- integrate with collaboration tools\n- build custom metadata applications\n- synchronize context across systems\n\n### Coding Agents and AI Assistants\n\nOpenMetadata can connect to MCP-compatible assistants and agents such as:\n\n- Claude Desktop\n- Claude Code\n- Goose\n- Cursor\n- VS Code\n- Codex\n- custom LLM applications\n- internal enterprise AI assistants\n\nThis allows coding agents and data assistants to understand schemas, glossary definitions, ownership, lineage, quality requirements, and downstream dependencies before generating SQL, dbt models, documentation, tests, migration plans, or impact analysis.\n\n---\n\n## What You Can Build\n\n### AI Data Discovery\n\nAsk natural-language questions over your metadata graph and find relevant assets, even when names and keywords do not match exactly.\n\nExample:\n\n> Find datasets related to customer purchase behavior and transaction history.\n\n### Trusted AI Assistants\n\nGround AI responses in governed metadata: owners, descriptions, glossary terms, tags, classifications, quality signals, freshness, usage, and lineage.\n\nExample:\n\n> Explain what this dashboard measures and whether the underlying data is trusted.\n\n### Impact Analysis Agents\n\nAsk what will break if a table, column, pipeline, dashboard, metric, or ML feature changes.\n\nExample:\n\n> What downstream dashboards and ML models are affected if `customer_id` changes in this table?\n\n### Governance Automation\n\nUse agents to suggest descriptions, assign glossary terms, identify sensitive data, create classifications, propose ownership, and manage stewardship workflows.\n\nExample:\n\n> Review this new table, suggest glossary terms, and identify possible PII columns.\n\n### Data Quality Automation\n\nUse AI workflows to create tests, summarize failures, identify root causes, and recommend remediation steps.\n\nExample:\n\n> Investigate why this data quality test failed and identify upstream changes that may have caused it.\n\n### Semantic Knowledge Graphs\n\nBuild interoperable metadata knowledge graphs using OpenMetadata Standards, RDF\u002FOWL, JSON-LD, SHACL, and OpenMetadata’s entity relationships.\n\nExample:\n\n> Find all assets related to customer risk that contain sensitive data and are used by revenue dashboards.\n\n### Developer and Coding Agent Workflows\n\nConnect coding agents to OpenMetadata so they can understand schemas, owners, lineage, business definitions, and quality requirements before generating code, queries, dbt models, tests, or migration plans.\n\nExample:\n\n> Generate a dbt model for this customer table and include tests based on OpenMetadata quality expectations.\n\n---\n\n## How OpenMetadata Works\n\nOpenMetadata is built around an open, schema-first metadata graph.\n\n```text\n                  ┌──────────────────────────────────────────┐\n                  │              Data Ecosystem              │\n                  │ Warehouses | Lakes | BI | Pipelines | ML │\n                  │ APIs | Topics | Storage | Search | SaaS  │\n                  └─────────────────────┬────────────────────┘\n                                        │\n                              120+ Connectors\n                                        │\n                                        ▼\n┌────────────────────────────────────────────────────────────────────┐\n│                         OpenMetadata                               │\n│                                                                    │\n│  Context Layer                                                     │\n│  - technical metadata                                              │\n│  - quality and observability signals                               │\n│  - table and column-level lineage                                  │\n│  - ownership, usage, domains, data products                        │\n│                                                                    │\n│  Semantics Layer                                                   │\n│  - business concepts                                               │\n│  - glossaries and glossary terms                                   │\n│  - classifications and tags                                        │\n│  - metrics and KPIs                                                │\n│  - ontologies and semantic standards                               │\n│                                                                    │\n│  Knowledge Graph                                                   │\n│  - assets, people, teams, policies, lineage, quality, semantics    │\n└─────────────────────────────────────┬──────────────────────────────┘\n                                      │\n        ┌─────────────────────────────┼─────────────────────────────┐\n        ▼                             ▼                             ▼\n   Semantic Search                  APIs                         MCP Server\n        │                             │                             │\n        └─────────────────────────────┼─────────────────────────────┘\n                                      ▼\n                         AI Assistants and Agents\n              Claude | Claude Code | Cursor | VS Code | Codex\n                    Goose | Custom Apps | AI SDK Workflows\n```\n\n### Platform Components\n\nOpenMetadata consists of five core layers:\n\n1. **Open Metadata Standards**  \n   Canonical schemas, APIs, RDF\u002FOWL ontologies, SHACL shapes, JSON-LD contexts, and event models for metadata interoperability.\n\n2. **Metadata Store and Knowledge Graph**  \n   A central repository that stores and connects metadata entities, relationships, quality signals, usage, lineage, ownership, and semantics.\n\n3. **Ingestion Framework and Connectors**  \n   A pluggable framework for collecting metadata from databases, warehouses, dashboards, pipelines, messaging systems, ML platforms, storage systems, APIs, and more.\n\n4. **APIs, Search, Events, and Webhooks**  \n   Interfaces for consuming, updating, searching, subscribing to, and automating metadata.\n\n5. **MCP and AI SDK**  \n   AI-facing tools that expose OpenMetadata context and semantics to assistants, coding agents, and custom LLM applications.\n\n---\n\n## MCP: Connect AI Assistants and Agents\n\nOpenMetadata’s MCP server lets AI assistants and agents interact with your metadata graph through natural language.\n\nUse MCP to give AI assistants governed access to OpenMetadata context, including descriptions, owners, lineage, glossary terms, tags, classifications, data quality results, and semantic search.\n\n### MCP Tools\n\nOpenMetadata MCP tools include:\n\n| Tool | What it does |\n| --- | --- |\n| `search_metadata` | Search across tables, dashboards, pipelines, topics, glossaries, metrics, and more |\n| `semantic_search` | Search by meaning and context beyond keyword matching |\n| `get_entity_details` | Retrieve detailed metadata for a specific entity |\n| `get_entity_lineage` | Retrieve upstream and downstream lineage for an entity |\n| `create_glossary` | Create a new glossary |\n| `create_glossary_term` | Create a glossary term |\n| `create_lineage` | Create a lineage edge between entities |\n| `patch_entity` | Update metadata such as descriptions, tags, and owners |\n| `get_test_definitions` | List data quality test definitions |\n| `create_test_case` | Create a data quality test case |\n| `root_cause_analysis` | Analyze root causes of data quality failures |\n\n### Supported MCP Workflows\n\nOpenMetadata documentation includes setup guides for:\n\n- Claude Desktop\n- Claude Code\n- Goose\n- Cursor\n- VS Code\n- Semantic Search through MCP\n\nCodex and other MCP-compatible coding agents can use the OpenMetadata MCP endpoint as an external context and tool server.\n\nGet started:\n[OpenMetadata MCP Server Documentation](https:\u002F\u002Fdocs.open-metadata.org\u002Fv1.12.x\u002Fhow-to-guides\u002Fmcp)\n\n### MCP Endpoint\n\n```text\nhttps:\u002F\u002F\u003CYOUR-OPENMETADATA-SERVER>\u002Fmcp\n```\n\n### Example Prompts\n\nAfter connecting an MCP client, try prompts such as:\n\n```text\nWhat is the definition of the Revenue metric?\n\nShow me the lineage of the data feeding the Executive Revenue dashboard.\n\nWho owns the Customer 360 data product and when was it last updated?\n\nFind tables related to customer purchase behavior and transaction history.\n\nWhich downstream dashboards are affected if this column changes?\n\nCreate a glossary term for Net Retention and link it to related metrics.\n```\n\n---\n\n## Semantic Search\n\nSemantic Search lets users and AI assistants find data assets by meaning, not only by exact keyword matches.\n\nWhen Semantic Search is enabled, OpenMetadata can convert natural-language queries into embeddings and search conceptually related metadata assets.\n\nExample:\n\n```text\nFind tables related to customer purchase behavior and transaction history.\n```\n\nThis can surface assets such as:\n\n```text\norder_transactions\nbuyer_activity\ncustomer_events\nrevenue_orders\n```\n\nSemantic Search helps with:\n\n- natural-language discovery\n- AI data exploration\n- concept-based search\n- cross-domain asset discovery\n- finding related data even when names differ\n- grounding LLM responses in relevant metadata context\n\nLearn more:\n[Semantic Search MCP Tool](https:\u002F\u002Fdocs.open-metadata.org\u002Fv1.12.x\u002Fhow-to-guides\u002Fmcp\u002Fsemantic-search)\n\n---\n\n## OpenMetadata Standards\n\nOpenMetadata is built on open metadata standards.\n\n[OpenMetadata Standards](https:\u002F\u002Fopenmetadatastandards.org\u002F) is the open-source home for the schemas, ontologies, and specifications behind OpenMetadata.\n\nIt provides:\n\n- 700+ JSON Schemas for metadata entities, APIs, configurations, events, and relationships\n- RDF\u002FOWL ontologies for semantic web, linked data, and knowledge graph use cases\n- SHACL shapes for metadata validation\n- JSON-LD contexts for semantic interoperability\n- API and event schemas for search, feeds, webhooks, and bulk operations\n- standards for governance, lineage, quality, observability, teams, users, roles, policies, and events\n\nOpenMetadata Standards enables:\n\n- interoperable metadata management\n- semantic metadata modeling\n- enterprise knowledge graph construction\n- linked data and RDF integrations\n- metadata validation using SHACL\n- extensibility through schema-first design\n\nLearn more:\n[OpenMetadata Standards](https:\u002F\u002Fopenmetadatastandards.org\u002F)\n\n---\n\n## Core Platform Capabilities\n\n### Discovery and Understanding\n\n- asset search and discovery\n- semantic search\n- descriptions and documentation\n- sample data and usage context\n- ownership and stewardship\n- conversations, tasks, and announcements\n\n### Governance and Semantics\n\n- glossaries and glossary terms\n- classifications and tags\n- metrics and KPIs\n- domains and data products\n- policies and roles\n- certification and lifecycle states\n\n### Data Quality and Observability\n\n- test cases and test suites\n- profiling\n- freshness, volume, null, uniqueness, and distribution checks\n- custom tests\n- data quality dashboards\n- alerts and incidents\n- root-cause analysis workflows\n\n### Lineage and Impact Analysis\n\n- table lineage\n- column-level lineage\n- dashboard lineage\n- pipeline lineage\n- metric lineage\n- ML model lineage\n- upstream and downstream impact analysis\n\n### Collaboration\n\n- conversations\n- tasks\n- announcements\n- notifications\n- ownership workflows\n- documentation workflows\n- shared stewardship between producers and consumers\n\n### Security and Access Control\n\n- authentication\n- authorization\n- roles and policies\n- SSO integration\n- bot and user tokens\n- MCP authentication\n- governed metadata actions\n\n### Extensibility and Automation\n\n- APIs\n- SDKs\n- webhooks\n- events\n- applications\n- ingestion framework\n- custom connectors\n- custom properties\n- MCP tools\n- AI SDK workflows\n\n---\n\n## Quickstart\n\n### 1. Try OpenMetadata\n\nExplore OpenMetadata using the sandbox:\n\n[OpenMetadata Sandbox](https:\u002F\u002Fsandbox.open-metadata.org)\n\n### 2. Install OpenMetadata\n\nFollow the installation guide:\n\n[OpenMetadata Quickstart](https:\u002F\u002Fdocs.open-metadata.org\u002Flatest\u002Fquick-start)\n\n### 3. Ingest Metadata\n\nConnect your data sources and build your metadata graph.\n\nStart with:\n\n- a warehouse or database\n- a BI\u002Fdashboard tool\n- an orchestration or pipeline system\n- data quality and profiling\n- lineage ingestion\n\n### 4. Build Context\n\nAdd the operational and trust metadata AI needs:\n\n- descriptions\n- owners\n- teams\n- domains\n- data products\n- quality tests\n- freshness checks\n- usage\n- lineage\n- column-level lineage\n\n### 5. Add Semantics\n\nAdd business meaning:\n\n- glossaries\n- glossary terms\n- classifications\n- tags\n- metrics\n- KPIs\n- policies\n- domains\n- data products\n\n### 6. Enable Semantic Search\n\nConfigure Semantic Search so users and AI assistants can search by meaning.\n\nLearn more:\n\n```text\nhttps:\u002F\u002Fdocs.open-metadata.org\u002Fv1.12.x\u002Fhow-to-guides\u002Fmcp\u002Fsemantic-search\n```\n\n### 7. Connect an MCP Client\n\nInstall or enable the MCP application in OpenMetadata and connect your preferred MCP-compatible client.\n\nMCP endpoint:\n\n```text\nhttps:\u002F\u002F\u003CYOUR-OPENMETADATA-SERVER>\u002Fmcp\n```\n\nMCP guide:\n\n```text\nhttps:\u002F\u002Fdocs.open-metadata.org\u002Fv1.12.x\u002Fhow-to-guides\u002Fmcp\n```\n\n### 8. Build Custom AI Applications\n\nUse the AI SDK to connect any LLM to OpenMetadata’s MCP tools.\n\nAI SDK documentation:\n\n```text\nhttps:\u002F\u002Fdocs.open-metadata.org\u002Fv1.12.x\u002Fapi-reference\u002Fsdk\u002Fai-sdk\n```\n\n---\n\n## Documentation and Community\n\n- Documentation: [docs.open-metadata.org](https:\u002F\u002Fdocs.open-metadata.org\u002F)\n- MCP Server: [OpenMetadata MCP Documentation](https:\u002F\u002Fdocs.open-metadata.org\u002Fv1.12.x\u002Fhow-to-guides\u002Fmcp)\n- OpenMetadata Standards: [openmetadatastandards.org](https:\u002F\u002Fopenmetadatastandards.org\u002F)\n- Website: [open-metadata.org](https:\u002F\u002Fopen-metadata.org\u002F)\n- Slack Community: [slack.open-metadata.org](https:\u002F\u002Fslack.open-metadata.org\u002F)\n- Blog: [blog.open-metadata.org](https:\u002F\u002Fblog.open-metadata.org\u002F)\n\n---\n\n## Open Source and Enterprise AI\n\nOpenMetadata is the open-source foundation for metadata, context, semantics, governance, quality, lineage, APIs, MCP, and AI SDK workflows.\n\nFor managed enterprise capabilities, AI agents, automation, AI Studio, enterprise MCP workflows, commercial support, and managed operations, see Collate:\n\n- [Collate](https:\u002F\u002Fwww.getcollate.io\u002F)\n- [Collate AI](https:\u002F\u002Fwww.getcollate.io\u002Fcollate-ai)\n\n---\n\n## Contributing\n\nWe welcome contributions from the community.\n\nYou can contribute by:\n\n- improving metadata schemas and standards\n- adding connectors\n- improving ingestion workflows\n- enhancing MCP tools\n- improving semantic search\n- adding documentation\n- fixing bugs\n- improving the UI and user experience\n- proposing new governance, lineage, quality, and AI use cases\n\nSee the contribution guide in the repository to get started.\n\n---\n\n\n## Stargazers\n\n[![Stargazers of @open-metadata\u002FOpenMetadata repo](http:\u002F\u002Freporoster.com\u002Fstars\u002Fopen-metadata\u002FOpenMetadata)](https:\u002F\u002Fgithub.com\u002Fopen-metadata\u002FOpenMetadata\u002Fstargazers)\n\n## License\nOpenMetadata is released under [Apache License, Version 2.0](http:\u002F\u002Fwww.apache.org\u002Flicenses\u002FLICENSE-2.0)\n","OpenMetadata 是一个统一的元数据平台，旨在通过集中的元数据存储库、深入到列级别的血缘关系以及无缝团队协作来支持数据发现、数据可观测性和数据治理。其核心功能包括技术元数据连接、数据质量信号整合、所有权和使用情况追踪等，并构建了一个统一的知识图谱，为用户提供全面的数据上下文信息。此外，该平台还支持120多种连接器，具备语义搜索能力，提供APIs和SDKs，适用于需要增强数据理解、信任度及使用效率的各种场景，如企业级数据管理、AI辅助决策系统等。基于TypeScript开发，遵循Apache License 2.0开源许可协议。",2,"2026-06-11 03:36:49","high_star"]