cloudflare · Oxyjun · Oct 27, 2025 · Oct 27, 2025
@@ -32,8 +32,8 @@ Add individual MCP servers to Cloudflare Access to bring them under centralized
 
 To add an MCP server:
 
-1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Access** > **Applications** > **AI controls**.
-2. Select the **MCP servers** tab.
+1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Access controls** > **AI controls**.
+2. Go to the **MCP servers** tab.
 3. Select **Add an MCP server**.
 4. Enter any name for the server.
 5. (Optional) Enter a custom string for the **Server ID**.
@@ -63,8 +63,8 @@ The MCP server status indicates the synchronization status of the MCP server to
 
 To reauthenticate an MCP server in Cloudflare Access:
 
-1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Access** > **Applications** > **AI controls**.
-2. Select the **MCP servers** tab.
+1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Access controls** > **AI controls**.
+2. Go to the **MCP servers** tab.
 3. Select the server that you want to reauthenticate, then select **Edit**.
 4. Select **Authenticate server**.
 
@@ -74,8 +74,8 @@ You will be redirected to log in to your OAuth provider. The account used to aut
 
 Cloudflare Access automatically synchronizes with your MCP server every 24 hours. To manually refresh the MCP server in Zero Trust:
 
-1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Access** > **Applications** > **AI controls**.
-2. Select the **MCP servers** tab and find the server that you want to refresh.
+1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Access controls** > **AI controls**.
+2. Go to the **MCP servers** tab and find the server that you want to refresh.
 3. Select the three dots > **Sync capabilities**.
 
 The MCP server page will show the updated list of tools and prompts. New tools and prompts are automatically enabled in the MCP server portal.
@@ -84,8 +84,8 @@ The MCP server page will show the updated list of tools and prompts. New tools a
 
 To create an MCP server portal:
 
-1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Access** > **Applications** > **AI controls**.
-2. Select **Add an MCP server portal**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Access controls** > **AI controls**.
+2. Select **Add MCP server portal**.
 3. Enter any name for the portal.
 4. Under **Custom domain**, select a domain for the portal URL. Domains must belong to an active zone in your Cloudflare account. You can optionally specify a subdomain.
 5. [Add MCP servers](#add-an-mcp-server) to the portal.
@@ -102,14 +102,14 @@ Users can now [connect to the portal](#connect-to-a-portal) at `https://<subdoma
 
 Cloudflare Access automatically creates an Access application for each MCP server portal. You can customize the portal login experience by updating Access application settings:
 
-1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Access** > **Applications**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Access controls** > **Applications**.
 2. Find the portal that you want to configure, then select the three dots > **Edit**.
 3. To configure identity providers for the portal:
-   1. Select the **Login methods** tab.
+   1. Go to the **Login methods** tab.
    2. Select the [identity providers](/cloudflare-one/integrations/identity-providers/) that you want to enable for your application.
    3. (Recommended) If you plan to only allow access via a single identity provider, turn on **Instant Auth**. End users will not be shown the [Cloudflare Access login page](/cloudflare-one/reusable-components/custom-pages/access-login-page/). Instead, Cloudflare will redirect users directly to your SSO login event.
 4. To customize the block page:
-   1. Select the **Experience settings** tab.
+   1. Go to the **Experience settings** tab.
    2. <Render file="access/access-block-page" product="cloudflare-one" />
 5. Select **Save application**.
 
@@ -161,7 +161,7 @@ rm -rf ~/.mcp-auth
 
 Portal logs allow you to monitor user activity through an MCP server portal. You can view logs on a per-portal or per-server basis.
 
-1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Access** > **Applications** > **AI controls**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Access controls** > **AI controls**.
 2. Find the portal or server that you want to view logs for, then select the three dots > **Edit**.
 3. Select **Logs**.
 

@@ -87,25 +87,26 @@ The Worker will be deployed to your `*.workers.dev` subdomain at `mcp-server-cf-
 <Tabs syncKey="dashPlusAPI">
 <TabItem label="Dashboard">
 
-1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Access** > **Applications**.
-2. Select **SaaS**.
-3. In **Application**, enter a custom name (for example, `MCP server`) and select the textbox that appears below.
-4. Select **OIDC** as the authentication protocol.
-5. Select **Add application**.
-6. In **Redirect URLs**, enter the authorization callback URL for your MCP server. The callback URL for our [example MCP server](#1-deploy-an-example-mcp-server) is
+1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**.
+2. Select **Add an application**.
+3. Select **SaaS**.
+4. In **Application**, enter a custom name (for example, `MCP server`) and select the textbox that appears below.
+5. Select **OIDC** as the authentication protocol.
+6. Select **Add application**.
+7. In **Redirect URLs**, enter the authorization callback URL for your MCP server. The callback URL for our [example MCP server](#1-deploy-an-example-mcp-server) is
    `txt
 https://mcp-server-cf-access.<YOUR_SUBDOMAIN>.workers.dev/callback
 `
-7. Copy the following values to input into our example MCP server. Other MCP servers may require different sets of input values.
+8. Copy the following values to input into our example MCP server. Other MCP servers may require different sets of input values.
    - **Client secret**
    - **Client ID**
    - **Token endpoint**
    - **Authorization endpoint**
    - **Key endpoint**
 
-8. (Optional) Under **Advanced settings**, turn on [**Refresh tokens**](/cloudflare-one/access-controls/applications/http-apps/saas-apps/generic-oidc-saas/#advanced-settings) if you want to reduce the number of times a user needs to log in to the identity provider.
-9. Configure [Access policies](/cloudflare-one/access-controls/policies/) to define the users who can access the MCP server.
-10. Save the application.
+9. (Optional) Under **Advanced settings**, turn on [**Refresh tokens**](/cloudflare-one/access-controls/applications/http-apps/saas-apps/generic-oidc-saas/#advanced-settings) if you want to reduce the number of times a user needs to log in to the identity provider.
+10. Configure [Access policies](/cloudflare-one/access-controls/policies/) to define the users who can access the MCP server.
+11. Save the application.
 
 </TabItem>
 <TabItem label="API">

@@ -6,23 +6,23 @@ sidebar:
   order: 2
 ---
 
-This guide covers how to configure [Adobe Acrobat Sign](https://helpx.adobe.com/sign/using/enable-saml-single-sign-on.html) as a SAML application in Cloudflare Zero Trust.
+This guide covers how to configure [Adobe Acrobat Sign](https://helpx.adobe.com/sign/using/enable-saml-single-sign-on.html) as a SAML application in Cloudflare One.
 
 ## Prerequisites
 
-- An [identity provider](/cloudflare-one/integrations/identity-providers/) configured in Cloudflare Zero Trust
+- An [identity provider](/cloudflare-one/integrations/identity-providers/) configured in Cloudflare One
 - Admin access to a Adobe Acrobat Sign account
 - A [claimed domain](https://helpx.adobe.com/sign/using/claim-domain-names.html) in Adobe Acrobat Sign
 
-## 1. Add a SaaS application to Cloudflare Zero Trust
+## 1. Add a SaaS application to Cloudflare One
 
-1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Access** > **Applications**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**.
 2. Select **Add an application** > **SaaS**.
 3. For **Application**, enter `Adobe Sign` and select the corresponding textbox that appears.
 4. For the authentication protocol, select **SAML**.
 5. Select **Add application**.
 6. Copy the **Access Entity ID or Issuer**, **Public key**, and **SSO endpoint**.
-7. Keep this window open without selecting **Select configuration**. You will finish this configuration in step [3. Finish adding a SaaS application to Cloudflare Zero Trust](#3-finish-adding-a-saas-application-to-cloudflare-zero-trust).
+7. Keep this window open without selecting **Select configuration**. You will finish this configuration in step [3. Finish adding a SaaS application to Cloudflare One](#3-finish-adding-a-saas-application-to-cloudflare-one).
 
 ## 2. Add a SAML SSO provider to Adobe Sign
 
@@ -31,15 +31,15 @@ This guide covers how to configure [Adobe Acrobat Sign](https://helpx.adobe.com/
 3. Enter a hostname (for example, `yourcompanyname`). Users can use this URL or `https://secure.adobesign.com/public/login` to sign in via SSO.
 4. (Optional) For **Single Sign On Login Message**, enter a custom message (for example, `Log in via SSO`). The default message is **Sign in using your corporate credentials**.
 5. Fill in the following fields:
-   - **Entity ID/Issuer URL**: Access Entity ID or Issuer from application configuration in Cloudflare Zero Trust.
-   - **Login URL/SSO Endpoint**: SSO endpoint from application configuration in Cloudflare Zero Trust.
-   - **IdP Certificate**: Public key from application configuration in Cloudflare Zero Trust. Wrap the certificate in `-----BEGIN CERTIFICATE-----` and `-----END CERTIFICATE-----`.
+   - **Entity ID/Issuer URL**: Access Entity ID or Issuer from application configuration in Cloudflare One.
+   - **Login URL/SSO Endpoint**: SSO endpoint from application configuration in Cloudflare One.
+   - **IdP Certificate**: Public key from application configuration in Cloudflare One. Wrap the certificate in `-----BEGIN CERTIFICATE-----` and `-----END CERTIFICATE-----`.
 6. Copy the **Entity ID/SAML Audience** and **Assertion Consumer URL**.
 7. Select **Save**.
 
-## 3. Finish adding a SaaS application to Cloudflare Zero Trust
+## 3. Finish adding a SaaS application to Cloudflare One
 
-1. In your open Zero Trust window, fill in the following fields:
+1. In your open Cloudflare One window, fill in the following fields:
    - **Entity ID**: Entity ID/SAML Audience from Adobe Acrobat Sign SAML SSO configuration.
    - **Assertion Consumer Service URL**: Assertion Consumer URL from Adobe Acrobat Sign SAML SSO configuration.
    - **Name ID format**: _Email_

@@ -10,17 +10,17 @@ import { Render } from "~/components";
 
 <Render file="contact-support" product="email-security" />
 
-[Cloudflare Area 1](https://www.cloudflare.com/products/zero-trust/email-security/) is an email security platform that protects your organization's inbox from phishing, spam, and other malicious messages. This guide covers how to configure Area 1 as a SAML application in Cloudflare Zero Trust.
+[Cloudflare Area 1](https://www.cloudflare.com/products/zero-trust/email-security/) is an email security platform that protects your organization's inbox from phishing, spam, and other malicious messages. This guide covers how to configure Area 1 as a SAML application in Cloudflare One.
 
 ## Prerequisites
 
-- An [identity provider](/cloudflare-one/integrations/identity-providers/) configured in Cloudflare Zero Trust
+- An [identity provider](/cloudflare-one/integrations/identity-providers/) configured in Cloudflare One
 - Admin access to your Area 1 account
-- Your user's email in Area 1 matches their email in Zero Trust
+- Your user's email in Area 1 matches their email in Cloudflare One
 
-## 1. Add Area 1 to Zero Trust
+## 1. Add Area 1 to Cloudflare One
 
-1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Access** > **Applications**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**.
 
 2. Select **Add an application**.
 
@@ -52,9 +52,9 @@ Finally, you will need to configure Area 1 to allow users to log in through Clou
 4. In **SAML SSO Domain**, enter `<your-team-name>.cloudflareaccess.com`.
 
 5. Get your Metadata XML file:
-   1. In Zero Trust, copy the **SSO Endpoint** for your application.
+   1. In Cloudflare One, copy the **SSO Endpoint** for your application.
 
-      ![Copy SSO settings for a SaaS application from Zero Trust](~/assets/images/cloudflare-one/applications/saas-sso-endpoint.png)
+      ![Copy SSO settings for a SaaS application from Cloudflare One](~/assets/images/cloudflare-one/applications/saas-sso-endpoint.png)
 
    2. In a new browser tab, paste the **SSO Endpoint** and append `/saml-metadata` to the end of the URL. For example, `https://<your-team-name>.cloudflareaccess.com/cdn-cgi/access/sso/saml/<app-id>/saml-metadata`.
 

@@ -6,16 +6,16 @@ sidebar:
   order: 4
 ---
 
-This guide covers how to configure [Asana](https://help.asana.com/hc/en-us/articles/14075208738587-Authentication-and-access-management-options-for-paid-plans#gl-saml) as a SAML application in Cloudflare Zero Trust.
+This guide covers how to configure [Asana](https://help.asana.com/hc/en-us/articles/14075208738587-Authentication-and-access-management-options-for-paid-plans#gl-saml) as a SAML application in Cloudflare One.
 
 ## Prerequisites
 
-- An [identity provider](/cloudflare-one/integrations/identity-providers/) configured in Cloudflare Zero Trust
+- An [identity provider](/cloudflare-one/integrations/identity-providers/) configured in Cloudflare One
 - Super admin access to an Asana Enterprise, Enterprise+, or Legacy Enterprise account
 
-## 1. Add a SaaS application to Cloudflare Zero Trust
+## 1. Add a SaaS application to Cloudflare One
 
-1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Access** > **Applications**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**.
 2. Select **Add an application** > **SaaS** > **Select**.
 3. For **Application**, select _Asana_.
 4. For the authentication protocol, select **SAML**.
@@ -33,8 +33,8 @@ This guide covers how to configure [Asana](https://help.asana.com/hc/en-us/artic
 1. In Asana, select your profile picture > **Admin console** > **Security** > **SAML authentication**.
 2. Under **SAML options**, select _Optional_.
 3. Fill in the following fields:
-   - Sign-in page URL: SSO endpoint from application configuration in Cloudflare Zero Trust.
-   - X.509 certificate: Public key from application configuration in Cloudflare Zero Trust. Wrap the public key in `-----BEGIN CERTIFICATE-----` and `-----END CERTIFICATE-----`.
+   - Sign-in page URL: SSO endpoint from application configuration in Cloudflare One.
+   - X.509 certificate: Public key from application configuration in Cloudflare One. Wrap the public key in `-----BEGIN CERTIFICATE-----` and `-----END CERTIFICATE-----`.
 4. Select **Save changes**.
 
 ## 3. Test the integration and require SSO

@@ -6,24 +6,24 @@ sidebar:
   order: 5
 ---
 
-This guide covers how to configure [Atlassian Cloud](https://support.atlassian.com/security-and-access-policies/docs/configure-saml-single-sign-on-with-an-identity-provider/) as a SAML application in Cloudflare Zero Trust.
+This guide covers how to configure [Atlassian Cloud](https://support.atlassian.com/security-and-access-policies/docs/configure-saml-single-sign-on-with-an-identity-provider/) as a SAML application in Cloudflare One.
 
 ## Prerequisites
 
-- An [identity provider](/cloudflare-one/integrations/identity-providers/) configured in Cloudflare Zero Trust
+- An [identity provider](/cloudflare-one/integrations/identity-providers/) configured in Cloudflare One
 - Admin access to an Atlassian Cloud account
 - Atlassian Guard Standard subscription
 - A [domain](https://support.atlassian.com/user-management/docs/verify-a-domain-to-manage-accounts/) verified in Atlassian Cloud
 
-## 1. Add a SaaS application to Cloudflare Zero Trust
+## 1. Add a SaaS application to Cloudflare One
 
-1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Access** > **Applications**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**.
 2. Select **Add an application** > **SaaS**.
 3. For **Application**, select _Atlassian_.
 4. For the authentication protocol, select **SAML**.
 5. Select **Add application**.
 6. Copy the **Access Entity ID or Issuer**, **Public key**, and **SSO endpoint**.
-7. Keep this window open. You will finish this configuration in step [4. Finish adding a SaaS application to Cloudflare Zero Trust](#4-finish-adding-a-saas-application-to-cloudflare-zero-trust).
+7. Keep this window open. You will finish this configuration in step [4. Finish adding a SaaS application to Cloudflare One](#4-finish-adding-a-saas-application-to-cloudflare-one).
 
 ## 2. Create a x.509 certificate
 
@@ -42,18 +42,18 @@ This guide covers how to configure [Atlassian Cloud](https://support.atlassian.c
         :::
 
 5.  Fill in the following fields:
-    - **Identity provider Entity ID**: Access Entity ID or Issuer from application configuration in Cloudflare Zero Trust.
-    - **Identity provider SSO URL**: SSO endpoint from application configuration in Cloudflare Zero Trust.
+    - **Identity provider Entity ID**: Access Entity ID or Issuer from application configuration in Cloudflare One.
+    - **Identity provider SSO URL**: SSO endpoint from application configuration in Cloudflare One.
     - **Public x509 certificate**: Paste the entire x.509 certificate from step [2. Create a x.509 certificate](#2-create-a-x509-certificate).
 6.  Select **Next**.
 7.  Copy the **Service provider entity URL** and **Service provider assertion consumer service URL**.
 8.  Select **Next**.
 9.  Under **Link domain**, select the domain you want to use with SAML SSO.
 10. Select **Next** > **Stop and save SAML**.
 
-## 4. Finish adding a SaaS application to Cloudflare Zero Trust
+## 4. Finish adding a SaaS application to Cloudflare One
 
-1. In your open Zero Trust window, fill in the following fields:
+1. In your open Cloudflare One window, fill in the following fields:
    - **Entity ID**: Service provider entity URL from Atlassian Cloud SAML SSO set-up.
    - **Assertion Consumer Service URL**: Service provider assertion consumer service URL from Atlassian Cloud SAML SSO set-up.
    - **Name ID format**: _Email_