chore: Add renaming changes across dataplex documentation

anikasharma03 · anikasharma03 · commit 21971532b36f · 2026-04-10T09:39:07.000Z
diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
@@ -15,3 +15,4 @@
 **/firestore/ @googleapis/toolbox-firestore-team @googleapis/senseai-eco-team
 **/looker/ @googleapis/toolbox-looker-team @googleapis/senseai-eco-team
 **/spanner/ @googleapis/toolbox-spanner-team @googleapis/senseai-eco-team
+**/knowledge-catalog/ @googleapis/toolbox-dataplex-team @googleapis/senseai-eco-team
diff --git a/.github/blunderbuss.yml b/.github/blunderbuss.yml
@@ -47,6 +47,10 @@ assign_issues_by:
     - 'product: dataplex'
     to:
     - 'googleapis/toolbox-dataplex-team'
+  - labels:
+    - 'product: knowledge-catalog'
+    to:
+    - 'googleapis/toolbox-dataplex-team'
   - labels:
     - 'product: firestore'
     to:
@@ -91,6 +95,10 @@ assign_prs_by:
     - 'product: dataplex'
     to:
     - 'googleapis/toolbox-dataplex-team'
+  - labels:
+    - 'product: knowledge-catalog'
+    to:
+    - 'googleapis/toolbox-dataplex-team'
   - labels:
     - 'product: firestore'
     to:
diff --git a/.github/labels.yaml b/.github/labels.yaml
@@ -123,6 +123,9 @@
 - name: 'product: dataplex'
   color: 5065c7
   description: 'Dataplex'
+- name: 'product: knowledge-catalog'
+  color: 5065c7
+  description: 'Knowledge Catalog'
 - name: 'product: dgraph'
   color: 5065c7
   description: 'Dgraph'
diff --git a/MCP-TOOLBOX-EXTENSION.md b/MCP-TOOLBOX-EXTENSION.md
@@ -166,16 +166,16 @@ instances, often by analyzing metrics and logs.
 
 ### Other Google Cloud Data Services
 
-#### Dataplex
+#### Knowledge Catalog (formerly known as Dataplex)
 
-* For interacting with Dataplex data lakes and assets:
+* For interacting with Knowledge Catalog data lakes and assets:
 
     ```bash
-    gemini extensions install https://github.com/gemini-cli-extensions/dataplex
+    gemini extensions install https://github.com/gemini-cli-extensions/knowledge-catalog
     ```
 
     Configuration:
-    https://github.com/gemini-cli-extensions/dataplex/tree/main?tab=readme-ov-file#configuration
+    https://github.com/gemini-cli-extensions/knowledge-catalog/tree/main?tab=readme-ov-file#configuration
 
 #### Looker
 
diff --git a/README.md b/README.md
@@ -97,7 +97,7 @@ You can use the Toolbox in any MCP-compatible IDE or client (e.g., Gemini CLI, G
 When you run Toolbox with a `--prebuilt=<database>` flag, you instantly get access to standard tools to interact with that database. 
 
 Supported databases currently include:
-- **Google Cloud:** AlloyDB, BigQuery, Cloud SQL (PostgreSQL, MySQL, SQL Server), Spanner, Firestore, Dataplex
+- **Google Cloud:** AlloyDB, BigQuery, Cloud SQL (PostgreSQL, MySQL, SQL Server), Spanner, Firestore, Knowledge Catalog (formerly known as Dataplex).
 - **Other Databases:** PostgreSQL, MySQL, SQL Server, Oracle, MongoDB, Redis, Elasticsearch, CockroachDB, ClickHouse, Couchbase, Neo4j, Snowflake, Trino, and more.
 
 For a full list of available tools and their capabilities across all supported databases, see the [Prebuilt Tools Reference](https://mcp-toolbox.dev/documentation/configuration/prebuilt-configs/).
diff --git a/docs/KNOWLEDGE_CATALOG_README.md b/docs/KNOWLEDGE_CATALOG_README.md
@@ -1,12 +1,12 @@
-# Dataplex MCP Server
+# Knowledge Catalog MCP Server
 
-The Dataplex Model Context Protocol (MCP) Server gives AI-powered development tools the ability to work with your Google Cloud Dataplex Catalog. It supports searching and looking up entries and aspect types.
+The Knowledge Catalog (formerly known as Dataplex) Model Context Protocol (MCP) Server gives AI-powered development tools the ability to work with your Google Cloud Knowledge Catalog. It supports searching and looking up entries and aspect types.
 
 ## Features
 
-An editor configured to use the Dataplex MCP server can use its AI capabilities to help you:
+An editor configured to use the Knowledge Catalog MCP server can use its AI capabilities to help you:
 
-- **Search Catalog** - Search for entries in Dataplex Catalog
+- **Search Catalog** - Search for entries in Knowledge Catalog
 - **Explore Metadata** - Lookup specific entries and search aspect types
 
 ## Prerequisites
@@ -37,18 +37,18 @@ You'll now be able to see all enabled tools in the "Tools" tab.
 
 ## Usage
 
-Once configured, the MCP server will automatically provide Dataplex capabilities to your AI assistant. You can:
+Once configured, the MCP server will automatically provide Knowledge Catalog capabilities to your AI assistant. You can:
 
-*   "Search for entries related to 'sales' in Dataplex."
+*   "Search for entries related to 'sales' in Knowledge Catalog."
 *   "Look up details for the entry 'projects/my-project/locations/us-central1/entryGroups/my-group/entries/my-entry'."
 
 ## Server Capabilities
 
-The Dataplex MCP server provides the following tools:
+The Knowledge Catalog MCP server provides the following tools:
 
 | Tool Name             | Description                                                                                                                  |
 |:----------------------|:-----------------------------------------------------------------------------------------------------------------------------|
-| `search_entries`      | Search for entries in Dataplex Catalog.                                                                                      |
+| `search_entries`      | Search for entries in Knowledge Catalog.                                                                                      |
 | `lookup_entry`        | Retrieve specific subset of metadata (for example, schema, usage, business overview, and contacts) of a specific data asset. |
 | `search_aspect_types` | Find aspect types relevant to the query.                                                                                     |
 | `lookup_context`      | Retrieve rich metadata regarding one or more data assets along with their relationships.                                     |
@@ -79,4 +79,4 @@ Add the following configuration to your MCP client (e.g., `settings.json` for Ge
 
 ## Documentation
 
-For more information, visit the [Dataplex documentation](https://cloud.google.com/dataplex/docs).
+For more information, visit the [Knowledge Catalog documentation](https://cloud.google.com/dataplex/docs).
diff --git a/docs/en/documentation/connect-to/gemini-cli/_index.md b/docs/en/documentation/connect-to/gemini-cli/_index.md
@@ -36,7 +36,7 @@ Below are a list of Gemini CLI Extensions powered by MCP Toolbox:
 * [cloud-sql-postgresql-observability](https://github.com/gemini-cli-extensions/cloud-sql-postgresql-observability)
 * [cloud-sql-sqlserver](https://github.com/gemini-cli-extensions/cloud-sql-sqlserver)
 * [cloud-sql-sqlserver-observability](https://github.com/gemini-cli-extensions/cloud-sql-sqlserver-observability)
-* [dataplex](https://github.com/gemini-cli-extensions/dataplex)
+* [knowledge-catalog](https://github.com/gemini-cli-extensions/knowledge-catalog)
 * [firestore-native](https://github.com/gemini-cli-extensions/firestore-native)
 * [looker](https://github.com/gemini-cli-extensions/looker)
 * [mcp-toolbox](https://github.com/gemini-cli-extensions/mcp-toolbox)
diff --git a/docs/en/documentation/introduction/_index.md b/docs/en/documentation/introduction/_index.md
@@ -77,7 +77,7 @@ Set the appropriate environment variables to connect, see the [Prebuilt Tools Re
 When you run Toolbox with a `--prebuilt=<database>` flag, you instantly get access to standard tools to interact with that database. 
 
 Supported databases currently include:
-- **Google Cloud:** AlloyDB, BigQuery, Cloud SQL (PostgreSQL, MySQL, SQL Server), Spanner, Firestore, Dataplex
+- **Google Cloud:** AlloyDB, BigQuery, Cloud SQL (PostgreSQL, MySQL, SQL Server), Spanner, Firestore, Knowledge Catalog (formerly known as Dataplex).
 - **Other Databases:** PostgreSQL, MySQL, SQL Server, Oracle, MongoDB, Redis, Elasticsearch, CockroachDB, ClickHouse, Couchbase, Neo4j, Snowflake, Trino, and more.
 
 For a full list of available tools and their capabilities across all supported databases, see the [Prebuilt Tools Reference](https://mcp-toolbox.dev/documentation/configuration/prebuilt-configs/).
diff --git a/docs/en/integrations/bigquery/tools/bigquery-search-catalog.md b/docs/en/integrations/bigquery/tools/bigquery-search-catalog.md
@@ -8,7 +8,7 @@ description: >
 
 ## About
 
-A `bigquery-search-catalog` tool returns all entries in Dataplex Catalog (e.g.
+A `bigquery-search-catalog` tool returns all entries in Knowledge Catalog (e.g.
 tables, views, models) with system=bigquery that matches given user query.
 
 `bigquery-search-catalog` takes a required `query` parameter based on which
@@ -30,14 +30,14 @@ following parameters:
 ### IAM Permissions
 
 Bigquery uses [Identity and Access Management (IAM)][iam-overview] to control
-user and group access to Dataplex resources. Toolbox will use your
+user and group access to Knowledge Catalog(formerly known as Dataplex) resources. Toolbox will use your
 [Application Default Credentials (ADC)][adc] to authorize and authenticate when
-interacting with [Dataplex][dataplex-docs].
+interacting with [Knowledge Catalog][dataplex-docs].
 
 In addition to [setting the ADC for your server][set-adc], you need to ensure
 the IAM identity has been given the correct IAM permissions for the tasks you
-intend to perform. See [Dataplex Universal Catalog IAM permissions][iam-permissions]
-and [Dataplex Universal Catalog IAM roles][iam-roles] for more information on
+intend to perform. See [Knowledge Catalog IAM permissions][iam-permissions]
+and [Knowledge Catalog IAM roles][iam-roles] for more information on
 applying IAM permissions and roles to an identity.
 
 [iam-overview]: https://cloud.google.com/dataplex/docs/iam-and-access-control
diff --git a/docs/en/integrations/dataplex/_index.md b/docs/en/integrations/dataplex/_index.md
diff --git a/docs/en/integrations/dataplex/prebuilt-configs/_index.md b/docs/en/integrations/dataplex/prebuilt-configs/_index.md
diff --git a/docs/en/integrations/knowledge-catalog/_index.md b/docs/en/integrations/knowledge-catalog/_index.md
@@ -0,0 +1,4 @@
+---
+title: "Knowledge Catalog"
+weight: 1
+---
diff --git a/docs/en/integrations/knowledge-catalog/prebuilt-configs/_index.md b/docs/en/integrations/knowledge-catalog/prebuilt-configs/_index.md
@@ -0,0 +1,5 @@
+---
+title: "Prebuilt Configs"
+type: docs
+description: "Prebuilt configurations for Knowledge Catalog (formerly known as Dataplex)."
+---
diff --git a/docs/en/integrations/knowledge-catalog/prebuilt-configs/dataplex.md b/docs/en/integrations/knowledge-catalog/prebuilt-configs/dataplex.md
@@ -1,10 +1,10 @@
 ---
-title: "Dataplex"
+title: "Knowledge Catalog (formerly known as Dataplex)"
 type: docs
-description: "Details of the Dataplex prebuilt configuration."
+description: "Details of the Knowledge Catalog prebuilt configuration."
 ---
 
-## Dataplex
+## Knowledge Catalog
 
 *   `--prebuilt` value: `dataplex`
 *   **Environment Variables:**
@@ -14,9 +14,8 @@ description: "Details of the Dataplex prebuilt configuration."
         entries.
     *   **Dataplex Editor** (`roles/dataplex.editor`) to modify entries.
 *   **Tools:**
-    *   `search_entries`: Searches for entries in Dataplex Catalog.
-    *   `lookup_entry`: Retrieves a specific entry from Dataplex
-        Catalog.
+    *   `search_entries`: Searches for entries in Knowledge Catalog.
+    *   `lookup_entry`: Retrieves a specific entry from Knowledge Catalog.
     *   `search_aspect_types`: Finds aspect types relevant to the
         query.
     *   `lookup_context`: Retrieves rich metadata regarding one or more data assets along with their relationships.
diff --git a/docs/en/integrations/knowledge-catalog/source.md b/docs/en/integrations/knowledge-catalog/source.md
@@ -1,22 +1,22 @@
 ---
-title: "Dataplex Source"
+title: "Knowledge Catalog (formerly known as Dataplex) Source"
 type: docs
 linkTitle: "Source"
 weight: 1
 description: >
-  Dataplex Universal Catalog is a unified, intelligent governance solution for data and AI assets in Google Cloud. Dataplex Universal Catalog powers AI, analytics, and business intelligence at scale.
+  Knowledge Catalog is a unified, intelligent governance solution for data and AI assets in Google Cloud. Knowledge Catalog powers AI, analytics, and business intelligence at scale.
 no_list: true
 ---
 
 ## About
 
-[Dataplex][dataplex-docs] Universal Catalog is a unified, intelligent governance
-solution for data and AI assets in Google Cloud. Dataplex Universal Catalog
+[Knowledge Catalog][dataplex-docs] is a unified, intelligent governance
+solution for data and AI assets in Google Cloud. Knowledge Catalog
 powers AI, analytics, and business intelligence at scale.
 
 At the heart of these governance capabilities is a catalog that contains a
-centralized inventory of the data assets in your organization. Dataplex
-Universal Catalog holds business, technical, and runtime metadata for all of
+centralized inventory of the data assets in your organization. Knowledge Catalog
+holds business, technical, and runtime metadata for all of
 your data. It helps you discover relationships and semantics in the metadata by
 applying artificial intelligence and machine learning.
 
@@ -182,7 +182,7 @@ Entries are organized within Entry Groups, which are logical groupings of Entrie
 Entries can be linked together using EntryLinks to represent relationships between data assets (e.g. foreign keys).
 
 # Tool instructions
-## Tool: dataplex_search_entries
+## Tool: search_entries
 ## General
 - Do not try to search within search results on your own.
 - Do not fetch multiple pages of results unless explicitly asked.
@@ -359,10 +359,17 @@ This abbreviated syntax works for the qualified predicates except for `label` in
     1. Explain that no search result was found
     2. Suggest to provide a more specific search query.
 
-## Tool: dataplex_lookup_entry
+## Tool: lookup_entry
 ### Request
-1. Always try to limit the size of the response by specifying `aspect_types` parameter. Make sure to include to select view=CUSTOM when using aspect_types parameter. If you do not know the name of the aspect type, use the `dataplex_search_aspect_types` tool.
-2. If you do not know the name of the entry, use `dataplex_search_entries` tool
+1. Always try to limit the size of the response by specifying `aspect_types` parameter. Make sure to include to select view=CUSTOM when using aspect_types parameter. If you do not know the name of the aspect type, use the `search_aspect_types` tool.
+2. If you do not know the name of the entry, use `search_entries` tool
 ### Response
 1. Unless asked for a specific aspect, respond with all aspects attached to the entry.
+
+## Tool: lookup_context
+### Request
+1. Use this tool to retrieve rich metadata regarding one or more data assets along with their relationships.
+2. You must provide the `resources` list with full resource names.
+### Response
+1. Present the requested metadata and relationship information. 
 ```
diff --git a/docs/en/integrations/knowledge-catalog/tools/_index.md b/docs/en/integrations/knowledge-catalog/tools/_index.md
diff --git a/docs/en/integrations/knowledge-catalog/tools/knowledge-catalog-lookup-context.md b/docs/en/integrations/knowledge-catalog/tools/knowledge-catalog-lookup-context.md
@@ -1,16 +1,16 @@
 ---
-title: "dataplex-lookup-context"
+title: "lookup-context"
 type: docs
 weight: 1
 description: > 
-  A "dataplex-lookup-context" tool provides rich metadata of one or more data assets along with their relationships.
+  A "lookup-context" tool provides rich metadata of one or more data assets along with their relationships.
 ---
 
 ## About
 
-A `dataplex-lookup-context` tool provides rich metadata of one or more data assets along with their relationships.
+A `lookup-context` tool provides rich metadata of one or more data assets along with their relationships.
 
-`dataplex-lookup-context` takes a required `name` parameter which contains the
+`lookup-context` takes a required `name` parameter which contains the
 project and location to which the request should be attributed in the following
 form: projects/{project}/locations/{location} and also a required `resources`
 parameter which is a list of resource names for which metadata is needed in the 
@@ -24,15 +24,15 @@ following form: projects/{project}/locations/{location}/entryGroups/{group}/entr
 
 ### IAM Permissions
 
-Dataplex uses [Identity and Access Management (IAM)][iam-overview] to control
-user and group access to Dataplex resources. Toolbox will use your
+Knowledge Catalog (formerly known as Dataplex) uses [Identity and Access Management (IAM)][iam-overview] to control
+user and group access to Knowledge Catalog resources. Toolbox will use your
 [Application Default Credentials (ADC)][adc] to authorize and authenticate when
-interacting with [Dataplex][dataplex-docs].
+interacting with [Knowledge Catalog][dataplex-docs].
 
 In addition to [setting the ADC for your server][set-adc], you need to ensure
 the IAM identity has been given the correct IAM permissions for the tasks you
-intend to perform. See [Dataplex Universal Catalog IAM permissions][iam-permissions]
-and [Dataplex Universal Catalog IAM roles][iam-roles] for more information on
+intend to perform. See [Knowledge Catalog IAM permissions][iam-permissions]
+and [Knowledge Catalog IAM roles][iam-roles] for more information on
 applying IAM permissions and roles to an identity.
 
 **Note on Lookup Context Tool Behavior:** This specific tool utilizes a post-filtering
@@ -53,7 +53,7 @@ rather than an access denied error.
 
 ```yaml
 kind: tool
-name: lookup_context
+name: lookup-context
 type: dataplex-lookup-context
 source: my-dataplex-source
 description: Use this tool to retrieve rich metadata regarding one or more data assets along with their relationships.
diff --git a/docs/en/integrations/knowledge-catalog/tools/knowledge-catalog-lookup-entry.md b/docs/en/integrations/knowledge-catalog/tools/knowledge-catalog-lookup-entry.md
@@ -1,17 +1,16 @@
 ---
-title: "dataplex-lookup-entry"
+title: "lookup-entry"
 type: docs
 weight: 1
 description: >
-  A "dataplex-lookup-entry" tool returns details of a particular entry in Dataplex Catalog.
+  A "lookup-entry" tool returns details of a particular entry in Knowledge Catalog.
 ---
 
 ## About
 
-A `dataplex-lookup-entry` tool returns details of a particular entry in Dataplex
-Catalog.
+A `lookup-entry` tool returns details of a particular entry in Knowledge Catalog.
 
-`dataplex-lookup-entry` takes a required `name` parameter which contains the
+`lookup-entry` takes a required `name` parameter which contains the
 project and location to which the request should be attributed in the following
 form: projects/{project}/locations/{location} and also a required `entry`
 parameter which is the resource name of the entry in the following form:
@@ -37,15 +36,15 @@ It also optionally accepts following parameters:
 
 ### IAM Permissions
 
-Dataplex uses [Identity and Access Management (IAM)][iam-overview] to control
-user and group access to Dataplex resources. Toolbox will use your
+Knowledge Catalog uses [Identity and Access Management (IAM)][iam-overview] to control
+user and group access to Knowledge Catalog resources. Toolbox will use your
 [Application Default Credentials (ADC)][adc] to authorize and authenticate when
-interacting with [Dataplex][dataplex-docs].
+interacting with [Knowledge Catalog][dataplex-docs].
 
 In addition to [setting the ADC for your server][set-adc], you need to ensure
 the IAM identity has been given the correct IAM permissions for the tasks you
-intend to perform. See [Dataplex Universal Catalog IAM permissions][iam-permissions]
-and [Dataplex Universal Catalog IAM roles][iam-roles] for more information on
+intend to perform. See [Knowledge Catalog IAM permissions][iam-permissions]
+and [Knowledge Catalog IAM roles][iam-roles] for more information on
 applying IAM permissions and roles to an identity.
 
 [iam-overview]: https://cloud.google.com/dataplex/docs/iam-and-access-control
@@ -58,10 +57,10 @@ applying IAM permissions and roles to an identity.
 
 ```yaml
 kind: tool
-name: lookup_entry
+name: lookup-entry
 type: dataplex-lookup-entry
 source: my-dataplex-source
-description: Use this tool to retrieve a specific entry in Dataplex Catalog.
+description: Use this tool to retrieve a specific entry in Knowledge Catalog.
 ```
 
 ## Reference
diff --git a/docs/en/integrations/knowledge-catalog/tools/knowledge-catalog-search-aspect-types.md b/docs/en/integrations/knowledge-catalog/tools/knowledge-catalog-search-aspect-types.md
diff --git a/docs/en/integrations/knowledge-catalog/tools/knowledge-catalog-search-entries.md b/docs/en/integrations/knowledge-catalog/tools/knowledge-catalog-search-entries.md
