The Catalog Enrichment MCP server enables AI agents to manage, enrich, and curate enterprise data assets in Data Governance and Catalog. It provides tools to enrich your catalog content directly through natural conversations so that stewards can capture business context as fast as they can describe it.
Use this MCP server to enrich and curate enterprise data assets in Data Governance and Catalog. The server uses write-capable AI tools to enrich and curate technical assets with business context, manage asset groups and stakeholders for assets, and certify or rate technical assets. These operations ensure data is properly governed, classified, and contextualized for enterprise consumption.
Key capabilities
Perform the following tasks with the MCP server:
•Add, remove, or edit data classifications on technical assets. Track the curation status for data classification associations. Examples of data classifications are data entity, data element, and document. The curation statuses are ACCEPTED and REJECTED.
•Update business names and descriptions on technical assets to bridge the gap between technical nomenclature and business concepts.
•Associate or dissociate business glossary terms with or from technical assets to provide business context and meaning.
•Manage stakeholders and asset groups for assets in the catalog.
•Certify or rate technical assets in the catalog.
Use cases
Use the MCP server to address the following use cases:
•Classify sensitive data assets for compliance and data protection. Examples of sensitive data assets are personally identifiably information (PII), financial data, and health data.
•Link glossary terms to technical assets so consumers understand their business meaning.
•Update asset metadata to provide human-readable business names and descriptions for cryptically-named technical assets.
•Enable AI-driven governance workflows to curate and contextualize at scale.
•Manage stakeholders and asset groups for assets to ensure clear governance, streamlined access control, and faster asset discovery across the platform.
•Certify and rate technical assets so data consumers can quickly identify trusted and quality data.
Prerequisites
Verify the following prerequisites before you start:
•Access to Data Governance and Catalog with permissions to view and update the assets that you want to enrich and curate.
•An authenticated Informatica Identity Service session for the MCP client or agent.
Server URL
Use the following format for server URLs to access the Catalog Enrichment server:
The following tools are available on this MCP server:
edit_asset_certification
Certifies or removes certification from technical assets such as tables, views, data sets, and files. When you certify an asset, you validate it for quality and trustworthiness.
Parameters:
- asset_identity. The unique internal identifier of the asset that you want to certify or uncertify.
- certify. Certify an asset or remove certification from an asset. Set to true to certify the asset as trusted. Set to false to remove the certification.
- comment. Optional. A comment explaining the certification action.
edit_asset_rating
Adds or updates the rating of assets in a range of 1 (lowest) through 5 (highest).
Parameters:
- asset_identity. The unique internal identifier of the asset that you want to rate.
- comment. Optional. A comment explaining the rating.
- rating_value. The rating value to assign to the asset, from 1 (lowest) to 5 (highest)
edit_data_asset_business_glossaries
Associates, removes, or edits business glossary terms on technical assets. Link glossary terms to assets to provide business context and meaning to technical data.
Parameters:
- asset_identity. The unique internal identifier of the asset that you want to update.
- curation_status. Optional. The curation status of the glossary term. This is required if you choose the "add" or "edit" operations. The default value is ACCEPTED.
- glossary_identity. The unique internal identifier of the glossary term that you want to associate, remove, or edit.
- identity_type. Optional. The type of asset identity you want to use. Valid values are INTERNAL or EXTERNAL. Internal identities are unique system identifiers. External IDs for business assets can be human-readable strings. External IDs for technical assets can be derived from the source system paths. Default is INTERNAL.
- operation. The type of operation you want to perform. Use "add" to associate a glossary term with an asset. Use "remove" to dissociate a glossary term from an asset. Use "edit" to change the curation status of a glossary association.
edit_data_asset_data_classifications
Associates, removes, or edits data classifications on technical assets.
You can associate technical assets with the following types of classifications:
- Data entity classifications. Use for data sets and tables.
- Data element classifications. Use for columns, fields, and files.
- Document classifications. Use for unstructured data such as PDFs and text files.
Parameters:
- asset_identity. The unique internal identifier of the asset that you want to update.
- classification_identity. The unique internal identifier of the classification asset that you want to associate, remove, or edit.
- curation_status. Optional. The curation status of the data classification. This is required if you choose the "add" or "edit" operation. The default value is ACCEPTED.
- identity_type. Optional. The type of asset identity you want to use. Valid values are INTERNAL or EXTERNAL. Internal identities are UUIDs. External IDs for business assets can be human-readable strings. External IDs for technical assets can be derived from the source system paths. Default is INTERNAL.
- operation. The type of operation you want to perform. Use "add" to associate a classification with an asset. Use "remove" to dissociate a classification from an asset. Use "edit" to change the curation status of a classification.
manage_asset_groups
Adds an asset group to an asset or removes it from an asset. You can't remove an asset group that isn't directly assigned to the asset, such as an asset group that is inherited from a parent asset.
Add or remove asset groups one at a time for an asset. Each request adds or removes one asset group.
If the change that you make with the tool starts a publish job, the response includes the job ID.
Changing asset group membership can affect stakeholder assignments, inherited asset groups, and access control.
Parameters:
- asset_groups. A list of asset groups that you want to add to or remove from the asset. For each asset group, enter the unique identifier or the name.
- asset_identity. The unique internal identifier of the asset for which you want to manage asset group memberships.
- identity_type. Optional. The type of asset identity you want to use. Valid values are INTERNAL or EXTERNAL. Default is INTERNAL.
- operation. The type of operation that you want to perform. You can add or remove asset groups. Valid values are "add" and "remove".
manage_asset_stakeholders
Adds a stakeholder to an asset or removes a stakeholder from an asset. Use this tool for every stakeholder change to an asset. Specify the asset, stakeholder, and role.
To identify an asset, use identity.
To identify a stakeholder, use stakeholder_identity or stakeholder_name. The stakeholder must belong to the specified role. To filter the results of a name match, specify stakeholder_email. To remove a stakeholder who no longer belongs to the role, use stakeholder_identity.
To identify a role, use role_identity or role_name. When you identify a role by its name, the role must apply to the type of the asset.
If you provide both an identity and a name, the tool uses the identity. Names are case sensitive. If a name matches no object or more than one object, the operation doesn't succeed.
Parameters:
- identity. The unique identifier of the asset that you want to update. This is interpreted as the supplied identity_type value.
- identity_type. Optional. The type of asset identity you want to use. Valid values are INTERNAL or EXTERNAL. Default is INTERNAL.
- operations. A list of the stakeholder role assignments that you want to add to or remove from the asset. Each entry has the following parameters:
▪ role_identity. The unique identifier of the role. This value takes precedence over role_name.
▪ role_name. The name of the stakeholder role. The name is case-sensitive and must be an exact match. The role must apply to the type of the asset. Use when the role_identity parameter isn't provided.
▪ stakeholder_email. The email address of the stakeholder. When you additionally specify stakeholder_name, the tool matches the stakeholder if both the name and the email address match.
▪ stakeholder_identity. The unique identifier of the user or user group. This value takes precedence over stakeholder_name.
▪ stakeholder_name. The name of the user or user group. The name is case-sensitive. If you provide the stakeholder_name without the stakeholder_email, the tool matches the name with the email address or the first or last name of the user. The tool matches the name with the users and user groups that belong to the specified role. Use this parameter when the stakeholder_identity parameter isn't provided.
▪ operation. The operation to perform on the stakeholder role assignment. Valid values are "add" and "remove".
update_asset_business_metadata
Updates the business names, descriptions, and custom attributes of technical assets.
Business names provide human-readable labels for cryptically-named technical assets. For example, you might give "ORA_CUST_TBL" the business name "Customer Master Table." Descriptions explain the business purpose and content of assets.
Parameters:
- asset_identity. The unique internal identifier of the technical asset that you want to update.
- business_description. Business description explaining the purpose and content of the asset.
- business_name. Meaningful business name for the asset. For example, enter 'Customer Master Table' for ORA_CUST_TBL.
- custom_attributes. Custom attributes to update. Each entry has the following parameters:
▪ name. Name of the custom attribute.
▪ value. Optional. The value of the custom attribute. To add a custom attribute, ensure that its value is not blank. To remove a custom attribute, omit the value to clear the attribute entirely. To remove a value from a multi-valued attribute, provide a new value that omits the value you want to remove.
▪ operation. Optional. The type of operation that you want to perform on the custom attribute. Valid values are “add”, “remove”, or “replace”. If you don't specify the operation, the custom attribute is replaced.
- identity_type. Optional. The type of identity of the technical asset. Valid values are INTERNAL or EXTERNAL. Internal identities are unique system identifiers. External IDs for business assets can be human-readable strings. External IDs for technical assets can be derived from the source system paths. Default is INTERNAL.