feat(Asgardeo): update

Author: VivekVinushanth

docs/tutorials/todo-manager/README.mdx

@@ -280,13 +280,6 @@ Keycloak will include the granted scopes in the access token's `scope` claim.
     - Create the resource
 
 3. Create roles:
-    - Navigate to **Application > MCP Inspector Application > Roles tab**
-    - Select **Application Role** as the audience type, then click **New Role**
-    - Create an `Admin` role and attach all three scopes
-    - Create a `User` role and attach only the `create:todos` scope
-
-    OR
-
     - Use the **User Management > Roles** to create roles and assign scopes directly.
     - Click **New Role** role
     - Provide the role name (e.g., `Admin` or `User`) in **Basic Details** section
@@ -295,6 +288,12 @@ Keycloak will include the granted scopes in the access token's `scope` claim.
     - Select the scopes you want to assign to this role (e.g., `create:todos`, `read:todos`, `delete:todos`)
     - Click **Finish** to create the role
 
+    If you have created the application in prior
+    - Navigate to **Application > MCP Inspector Application > Roles tab**
+    - Select **Application Role** as the audience type, then click **New Role**
+    - Create an `Admin` role and attach all three scopes
+    - Create a `User` role and attach only the `create:todos` scope
+
 4. Assign roles to users:
     - Go to **User Management > Roles**
     - Select the role you created (e.g., `Admin` or `User`) and move to **Users** tab
@@ -680,6 +679,42 @@ Since Logto does not support Dynamic Client Registration yet, you will need to m
 7. Go back to the MCP inspector and paste the "App ID" value in the "OAuth Configuration" section under "Client ID".
 8. Enter the value `{"scope": "create:todos read:todos delete:todos", "resource": "https://todo.mcp-server.app"}` in the "Auth Params" field. This will ensure that the access token returned by Logto contains the necessary scopes to access the todo manager.
 
+</TabItem>
+<TabItem value="asgardeo" label="Asgardeo">
+
+[Asgardeo](https://wso2.com/asgardeo) is a cloud-native identity as a service (IDaaS) platform that supports OAuth 2.0 and OpenID Connect (OIDC), enabling secure identity and access management for your applications.
+
+While Asgardeo supports dynamic client registration via a standard API, the endpoint is protected and requires an access token with the necessary permissions. In this tutorial, we’ll register the client manually through the Asgardeo Console.
+
+:::note
+If you don’t have an Asgardeo account, you can [sign up for free](https://asgardeo.io).
+:::
+
+Follow these steps to configure Asgardeo for MCP Inspector:
+
+1. Log in to the [Asgardeo Console](https://console.asgardeo.io) and select your organization.
+
+2. Create a new application:
+    - Go to **Applications** → **New Application**
+    - Choose **Single-Page Application**
+    - Enter an application name like `MCP Inspector`
+    - In the **Authorized Redirect URLs** field, paste the **Redirect URL** copied from MCP Inspector client application(e.g:`http://localhost:6274/oauth/callback`)
+    - Click **Create**
+
+3. Configure the protocol settings:
+    - Under the **Protocol** tab:
+    - Copy the **Client ID** that was auto generated.
+    - Ensure switching to `JWT` for the `Token Type` in **Access Token** section
+    - Click **Update**
+
+4. In MCP Inspector client application:
+    - Open the **OAuth Configuration** section
+    - Paste the copied **Client ID**
+    - Enter the following in the **Auth Params** field to request the necessary scopes:
+
+```json
+{ "scope": "openid profile email" }
+```
 </TabItem>
 <TabItem value="oauth-oidc" label="OAuth 2.0 / OIDC">
 

docs/tutorials/whoami/README.mdx

@@ -432,18 +432,14 @@ Follow these steps to configure Asgardeo for MCP Inspector:
 
 2. Create a new application:
     - Go to **Applications** → **New Application**
-    - Choose **Standard-Based Application**
-    - In the **Protocol** section, select **OpenID Connect (OIDC)**
+    - Choose **Single-Page Application**
     - Enter an application name like `MCP Inspector`
+    - In the **Authorized Redirect URLs** field, paste the **Redirect URL** copied from MCP Inspector client application(e.g:`http://localhost:6274/oauth/callback`)
     - Click **Create**
 
 3. Configure the protocol settings:
     - Under the **Protocol** tab:
     - Copy the **Client ID** that was auto generated.
-    - Ensure **Authorization Code** grant is enabled
-    - In the **Authorized Redirect URLs** field, paste the **Redirect URL** copied from MCP Inspector (e.g:`http://localhost:6274/oauth/callback`)
-    - In the **Allowed Origins** field, add the base URL of MCP Inspector (e.g:`http://localhost:6274`) to allow browser-based requests
-    - Ensure enabling `Public client` in **Client Authentication** section
     - Ensure switching to `JWT` for the `Token Type` in **Access Token** section
     - Click **Update**