Sync open source content 🐝 (from c6f1b53acdeec386c95bf3fd18ce758565ad78e0)

Author: beezythebot

_meta.global.tsx

@@ -940,6 +940,9 @@ const meta = {
             title: "Catalog",
             display: "children",
             items: {
+              overview: {
+                title: "Catalog overview",
+              },
               "sub-catalogs": {
                 title: "Sub catalogs",
               },

docs/mcp/catalog/index.mdx docs/mcp/catalog/overview.mdxdocs/mcp/catalog/index.mdx renamed to docs/mcp/catalog/overview.mdx

@@ -1,7 +1,6 @@
 ---
-title: Catalog
+title: Catalog overview
 description: "Discover curated third-party MCP servers and publish internal catalogs to share across organizations."
-asIndexPage: true
 ---
 
 import { Callout } from "@/mdx/components";

docs/mcp/catalog/sub-catalogs.mdx

@@ -5,7 +5,7 @@ description: "Share private MCP server catalogs with partner organizations using
 
 import { Callout } from "@/mdx/components";
 
-**Sub catalogs** enable sharing private [catalogs](/docs/mcp/catalog) with other organizations. This is useful when distributing internal MCP tools to partners, customers, or other teams within a company that operate as separate Gram organizations.
+**Sub catalogs** enable sharing private [catalogs](/docs/mcp/catalog/overview) with other organizations. This is useful when distributing internal MCP tools to partners, customers, or other teams within a company that operate as separate Gram organizations.
 
 ## The peered organization model
 
@@ -88,5 +88,5 @@ This merged view means sub organizations can seamlessly use tools from their own
 
 ## Next steps
 
-- Learn how to [create catalogs](/docs/mcp/catalog) to organize toolsets
+- Learn how to [create catalogs](/docs/mcp/catalog/overview) to organize toolsets
 - Read about [controlling server visibility](/docs/mcp/secure/public-private-servers) for fine-grained access control