Collibra MCP Server

Overview
The Collibra Model Context Protocol (MCP) server enables AI/ML developers, business users and LLMs to access and engage with governed metadata and business context information in the Collibra Platform. This offering additionally simplifies the integration of Collibra with agents that are built on LLMs and connected to other agents in complex workflows.
The MCP server provides a standardized access layer that addresses common challenges including inconsistent or low-quality context retrieval for LLMs, fragmented integration workflows, and lack of standardized communication among information sources.

# Read Tools
- **discover_business_glossary** | Searches for glossary definitions via Collibra AI Copilot.
- Note: this requires Collibra AI Copilot Public Preview to be enabled
- **discover_data_assets** | Searches for data assets via Collibra AI Copilot.
- Note: this requires Collibra AI Copilot Public Preview to be enabled
- **get_asset_details** | Retrieves a comprehensive, pre-formatted summary of a specific data asset by its ID
- **get_business_term_data** | Trace a business term back to its connected physical data assets
- **get_column_semantics** | Retrieve data attributes, measures, and business assets connected to a column
- **get_lineage_downstream** | Get downstream technical lineage (consumers) for a data entity
- **get_lineage_entity** | Get metadata about a specific entity in the technical lineage graph
- **get_lineage_transformation** | Get details and logic of a specific data transformation
- **get_lineage_upstream** | Get upstream technical lineage (sources) for a data entity
- **get_measure_data** | Trace a measure back to its underlying physical columns and tables
- **get_table_semantics** | Retrieve the semantic layer for a table: columns, data attributes, and connected measures
- **list_asset_types** | Lists available asset types in the system.
- **list_data_contract** | Retrieves the details of existing data contracts. Use this for general queries to view data contracts or get contract details, and always return both their IDs and names in the response.
- Note: requires Data Contracts Private Preview to be enabled
- **prepare_add_business_term** | Validate business term data, resolve domains, check for duplicates, and hydrate attribute schemas. Always call this before add_business_term.
- **prepare_create_asset** | Resolve asset type, domain, hydrate full attribute schema, and check duplicates. Always call this before create_asset.
- **pull_data_contract_manifest** | Downloads the manifest file for the currently active version of a specific data contract.
- Note: requires Data Contracts Private Preview to be enabled
- **search_asset_keyword** | Searches for data assets, business terms, communities, or other resources. This tool allows filtering by name, type, status, community or domain.
- **search_data_class** | Retrieves a list of available data classes with filtering capabilities.
- **search_data_classification_match** | Finds associations between data classes and assets.. Supports filtering by asset IDs, classification IDs, statuses, and - asset types.
- **search_lineage_entities** | Search for entities in the technical lineage graph
- **search_lineage_transformations** | Search for transformations in the technical lineage graph

# Write Tools
- **add_business_term** | Create a business term asset with definition and optional attributes in Collibra.
- **add_data_classification_match** | Assigns a data classification to a specific data asset. This tool allows for associating a data class with an asset.
- **create_asset** | Create a new data asset with optional attributes in Collibra.
- **push_data_contract_manifest** | Upload a new version of a data contract manifest to Collibra. The manifestID and version are automatically parsed from the manifest content if it adheres to the Open Data Contract Standard.
- Note: requires Data Contracts Private Preview to be enabled
- **remove_data_classification_match** | Removes a data classification from a specific data asset. This tool allows for the removal of a data class from an asset.
- **edit_asset** - Edit an existing asset via* *a list of typed operations:
- *update_attribute*, *add_attribute*, remove_attribute - change, append, or clear an attribute value (e.g. Definition, Note)
- *update_property* - rename the asset (name), change its displayName, or change its statusId (status name or UUID accepted)
- *add_relation*, *remove_relation* - link or unlink the asset to another asset by relation role (e.g. is synonym of)
- *add_tag* - append a free-text tag without replacing existing tags
- *set_responsibility* - assign a user or group to a resource role (e.g. Steward, Owner) by username, email, or UUID

# Documentation on integrating with Collibra
For integrating Collibra with Databricks, please see the Collibra Marketplace offering [here](https://marketplace.collibra.com/listings/databricks-mcp-marketplace-collibra-mcp-server/)