Merge pull request #280 from auth0/mcp-docs-tweaks

Updating Early Access message, removing images for Resource Param Com…

Author: KarimTantawy5

auth4genai/img/mcp/enable_resource_param_compatibility_dark.png

@@ -31,7 +31,7 @@ When an MCP server needs to call underlying APIs, it needs to perform a Custom T
 1. To the MCP client (e.g., an IDE, an AI assistant), the MCP server acts as a **Resource Server** (an API).
 2. To the underlying API (e.g., your own API), the MCP server acts as a **Client**.
 
-Because of this duality, you need to set up the MCP server twich on your Auth0 tenant, both as an API and as a Client, as described below.
+Because of this, you will set up the MCP server twice on your Auth0 tenant, both as an API and as a Client.
 
 ### Create an API to represent your MCP server
 

auth4genai/img/mcp/enable_resource_param_compatibility_light.png

@@ -8,7 +8,7 @@ Before your MCP client application can interact with a protected MCP server, it
 
 You can register your client in two ways: statically or dynamically. For most scenarios, especially in production, we strongly recommend static client registration for its superior security and control.
 
-<Note>In the upcoming authorization specification from MCP, CIMD will be introduced as the recommended method for client registration. Support for this new approach in Auth0 is planned and will be available soon.</Note>
+<Note>In the upcoming authorization specification from MCP, [Client ID Metadata Documents (CIMD)](https://modelcontextprotocol.io/specification/draft/basic/authorization#client-id-metadata-documents) will be introduced as the recommended method for client registration. Support for this new approach in Auth0 is planned and will be available soon.</Note>
 
 ## Static client registration (recommended for production)
 

auth4genai/mcp/get-started/call-your-apis-on-users-behalf.mdx

@@ -4,32 +4,13 @@ description: Learn how to enable the resource parameter in Auth0.
 sidebarTitle: Enable Resource Parameter Compatibility Profile
 ---
 
+import MCPGetStartedEnableResourceParamStep from "/snippets/mcp/get-started/pre-reqs/enable-resource-param-step.mdx";
+
 The Model Context Protocol (MCP) specification requires the use of the standards-compliant `resource` parameter as defined in [RFC 8707](https://www.rfc-editor.org/rfc/rfc8707.html). Auth0's Authentication API has historically used the `audience` parameter to specify a target resource server (API). This document outlines the new `resource` parameter and provides instructions for enabling the new compatibility profile.
 
 ## Enabling Resource Parameter Compatibility Profile
 
-The Resource Parameter Compatibility Profile is disabled by default. To enable it, you should:
-
-1. Create an Auth0 Account
-   To continue with this quickstart, you need to have an [Auth0 account](https://auth0.com/signup).
-2. Enable your Tenant to use the Resource Parameter Compatibility Profile
-   To use the `resource` parameter in your access tokens, you need to enable the compatibility profile
-1. Navigate to Settings and click on the **Advanced** tab
-2. Scroll down to the Settings section, find and enable **Resource Parameter Compatibility Profile**.
-
-<Frame>
-  <img
-    className="hidden dark:block"
-    src="/img/mcp/enable_resource_param_compatibility_dark.png"
-    alt="Resource Parameter Compatibility Profile enabled"
-  />
-  <img
-    className="block dark:hidden"
-    src="/img/mcp/enable_resource_param_compatibility_light.png"
-    alt="Resource Parameter Compatibility Profile enabled"
-  />
-</Frame>
-
+<MCPGetStartedEnableResourceParamStep />
 
 ## How it works
 

auth4genai/mcp/guides/registering-your-mcp-client-application.mdx

@@ -5,10 +5,10 @@ sidebarTitle: Why use Auth for MCP
 ---
 
 <Note>
-  Auth for MCP is currently available in Early Access and it's available for Universal Login flows only.
+Auth for MCP is currently available in Early Access. To join the Early Access program, please complete [this form](https://forms.gle/hvJ1ZRLmHr9YjV2a9). We'll reach out to you when your request is processed.
 </Note>
 
-Auth0’s Universal Login supports social, enterprise, and custom identity providers so users can sign in with existing credentials. Every access token issued through Auth0 carries verified identity context, ensuring all MCP interactions start from a trusted source.
+Auth for MCP supports Auth0’s Universal Login, which allows users to sign in using social, enterprise, or custom identity providers. Every access token issued through Auth0 carries verified identity context, ensuring all MCP interactions start from a trusted source.
 
 ## Why authentication matters for MCP
 

auth4genai/mcp/guides/resource-param-compatibility-profile.mdx

@@ -4,19 +4,4 @@ The quickest way to enable it is through the [Auth0 Dashboard](https://manage.au
 
 1. Navigate to **Settings** on the left sidebar.
 2. Click on [**Advanced**](https://manage.auth0.com/dashboard/#/tenant/advanced) on the top right corner.
-3. Scroll down to the Settings section, find and enable **Resource Parameter Compatibility Profile**.
-
-  <Frame>
-    <img
-      className="hidden dark:block"
-      src="/img/mcp/enable_resource_param_compatibility_dark.png"
-      alt="Resource Parameter Compatibility Profile enabled"
-    />
-    <img
-      className="block dark:hidden"
-      src="/img/mcp/enable_resource_param_compatibility_light.png"
-      alt="Resource Parameter Compatibility Profile enabled"
-    />
-  </Frame>
-
-Resource Parameter Compatibility Profile is available under the Early Access program. Go to the [Early Access section](/mcp/intro/overview#early-access) to learn how to gain access.
+3. Scroll down to the Settings section, find and enable the **Resource Parameter Compatibility Profile** toggle.