Skip to main content

Using the MCP connection to interact with your catalog

Once connected, ask your AI assistant for what you need in plain language. The assistant determines which catalog operations to run and carries them out under your permissions. Actions that only read the catalog are available to anyone with view access; actions that change the catalog require edit permissions and may be unavailable if your organization has enabled lockdown mode. Search and lookup results are always limited to resources you already have permission to see.

Find and explore content

Table 1.

Feature

Details

Search the catalog (read)

Run a broad search across all asset types, or a filtered search by keyword, resource type, status, tags, or custom field.

Open a single resource (read)

Retrieve the full record for an asset—description, tags, steward, classification, status, and custom fields.



Example prompts:

  • Find anything related to sales analytics.

  • Show me all certified resources tagged 'finance'.

  • What's the full metadata for the 'Quarterly Revenue' resource?

Enrich your catalog metadata

Table 2.

Feature

Detains

Update metadata (changes the catalog)

Add or revise descriptions, tags, and custom properties on existing resources.

Create resources (changes the catalog)

Register new resources with their initial metadata.

Clear properties (changes the catalog)

Remove the values of metadata fields that are no longer accurate, leaving them empty.



Example prompts:

  • Add a plain-language description to every untagged resource in the sales domain.

  • Register this new resource in the analytics collection.

  • Clear the certification and owner fields on these deprecated resources.

Work with relationships

Table 3.

Feature

Details

Trace relationships (read)

See which resources connect to a given resource. Each request follows the graph one level, so questions that span the whole graph may take several steps.

Create or remove links (changes the catalog)

Link related resources—such as a glossary term and a column—or remove links that are no longer accurate.



Example prompts:

  • What downstream resources depend on the 'orders' table?

  • Link the 'Net Revenue' glossary term to the revenue column in this table.

  • Remove the lineage link between these two retired resources.

Understand your catalog's structure

Table 4.

Feature

Details

List structure (read)

Discover the resource types, custom metadata fields, and collections—domains, data products, glossary groupings, or folders—defined in your organization's catalog. Because organizations can define their own custom types and fields, this list varies, so it's worth checking before you create or update resources.



Example prompts:

  • What resource types can I create in this catalog?

  • Which custom fields does the 'Metrics' type support here?

  • What domains and data products exist in our catalog?

Check users, organizations, and access

Table 5.

Feature

Details

Confirm your identity (read)

Check who you're signed in as.Look up a user (read): Resolve another data.world user's public profile—for example, to identify a steward.

View organization details (read)

Retrieve an organization's profile, or list every organization you can reach.



Example prompts:

  • Who am I signed in as?

  • Who is the steward 'jsmith' on these resources?

  • Which data.world organizations do I have access to?

In this section: