@W-20598954 MCP docs adjust menu order. integrate auth links

Author: patricksullivansf

docs/.vitepress/config.mts

@@ -166,8 +166,8 @@ export default defineConfig({
     nav: [
       {text: 'Guide', link: '/guide/'},
       {text: 'CLI Reference', link: '/cli/'},
-      {text: 'API Reference', link: '/api/'},
       {text: 'MCP Server', link: '/mcp/'},
+      {text: 'API Reference', link: '/api/'},
       {
         text: isReleaseBuild ? 'Latest Release' : 'dev',
         items: getVersionItems(),

docs/guide/index.md

@@ -33,5 +33,5 @@ See [Installation](./installation) for more options.
 - [Configuration](./configuration) - Configure instances and credentials
 - [IDE Integration](./ide-integration) - Connect Prophet VS Code to B2C CLI configuration
 - [CLI Reference](/cli/) - Browse available commands
-- [API Reference](/api/) - Explore the SDK API
 - [MCP Server](/mcp/) - AI-assisted development with Model Context Protocol
+- [API Reference](/api/) - Explore the SDK API

docs/index.md

@@ -16,12 +16,12 @@ hero:
     - theme: alt
       text: CLI Reference
       link: /cli/
-    - theme: alt
-      text: API Reference
-      link: /api/
     - theme: alt
       text: MCP Server
       link: /mcp/
+    - theme: alt
+      text: API Reference
+      link: /api/
 
 features:
   - icon: "\U0001F680"

docs/mcp/configuration.md

@@ -46,7 +46,7 @@ The server automatically loads this file when `--working-directory` points to yo
 | **PWAV3** | None (uses `--working-directory` only) |
 | **STOREFRONTNEXT** | None (uses `--working-directory` only) |
 
-**Note:** For `scapi_custom_apis_status`, OAuth credentials must include the `sfcc.custom-apis` scope.
+**Note:** Some tools require specific scopes. See [Configuring Scopes](../guide/authentication#configuring-scopes) in the Authentication Setup guide and individual tool pages for scope requirements.
 
 #### MRT Credentials (`~/.mobify`)
 
@@ -231,6 +231,8 @@ Enable specific tools instead of entire toolsets:
 
 ## Credential Details
 
+For authentication setup instructions, see the [Authentication Setup guide](../guide/authentication) which covers API client creation, WebDAV access, SCAPI authentication, and MRT API keys.
+
 ### B2C Credentials
 
 #### Username/Password (WebDAV)
@@ -240,24 +242,31 @@ Enable specific tools instead of entire toolsets:
 
 **Used by:** CARTRIDGES toolset
 
+See the [Authentication Setup guide](../guide/authentication#webdav-access) for detailed WebDAV access configuration.
+
 #### OAuth Client Credentials
 
 - `client-id` - API client ID from Account Manager
 - `client-secret` - API client secret from Account Manager
 
-**Used by:** SCAPI toolset (required for `scapi_custom_apis_status`)
+**Used by:** SCAPI toolset
 
-**Required scopes:**
-- `sfcc.custom-apis` - For custom API endpoint status queries
+**Note:** Some tools require specific scopes. See [Configuring Scopes](../guide/authentication#configuring-scopes) in the Authentication Setup guide and individual tool pages for scope requirements.
+
+See the [Authentication Setup guide](../guide/authentication#account-manager-api-client) for creating and configuring API clients, and [SCAPI Authentication](../guide/authentication#scapi-authentication) for SCAPI-specific setup.
 
 ### MRT Credentials
 
 - `api-key` - MRT API key from your Managed Runtime project
+- `project` - MRT project slug (required)
+- `environment` - MRT environment: `staging` or `production` (required when deploying)
 
 **Used by:** MRT toolset
 
 **Configuration location:** `~/.mobify` file
 
+See the [Authentication Setup guide](../guide/authentication#managed-runtime-api-key) for detailed MRT API key setup instructions.
+
 ## Telemetry Configuration
 
 Telemetry is enabled by default. Configure it via environment variables:

docs/mcp/index.md

@@ -59,6 +59,8 @@ The server automatically detects your project type and loads configuration from
 - Toolset selection (auto-discovery vs manual)
 - Required credentials per toolset
 
+For authentication setup instructions, see the [Authentication Setup guide](../guide/authentication) which covers API client creation, WebDAV access, SCAPI authentication, and MRT API keys.
+
 ### Available Toolsets
 
 The server provides five toolsets with specialized tools for different development workflows:

docs/mcp/installation.md

@@ -176,7 +176,7 @@ The server reads [`dw.json`](../guide/configuration#configuration-file) from you
 }
 ```
 
-See the [Configuration Guide](./configuration) for details on credential management.
+See the [Authentication Setup guide](../guide/authentication) for detailed instructions on setting up API clients, WebDAV access, and SCAPI authentication.
 
 ### 3. Scaffolding
 

docs/mcp/tools/cartridge-deploy.md

@@ -20,19 +20,10 @@ This tool is useful for deploying custom code cartridges for SFRA or other B2C C
 
 ## Authentication
 
-Requires B2C Commerce instance credentials. Supports two authentication methods:
+Supports two authentication methods:
 
-### Option 1: Basic Authentication (WebDAV)
-
-- `hostname` - B2C instance hostname
-- `username` - Username for Basic auth
-- `password` - Password or [WebDAV access key](https://help.salesforce.com/s/articleView?id=cc.b2c_account_manager_sso_use_webdav_file_access.htm&type=5)
-
-### Option 2: OAuth
-
-- `hostname` - B2C instance hostname
-- `client-id` - OAuth client ID from Account Manager
-- `client-secret` - OAuth client secret from Account Manager
+- **Basic Authentication (WebDAV)** - See [B2C Credentials](../configuration#b2c-credentials) (Username/Password section)
+- **OAuth** - See [B2C Credentials](../configuration#b2c-credentials) (OAuth Client Credentials section)
 
 **Configuration priority:**
 1. Flags (`--server`, `--username`, `--password`, `--client-id`, `--client-secret`)
@@ -106,5 +97,6 @@ Returns a deployment result object containing:
 ## See Also
 
 - [CARTRIDGES Toolset](../toolsets#cartridges) - Overview of cartridge development tools
+- [Authentication Setup](../../guide/authentication) - Set up WebDAV access and OAuth credentials
 - [Configuration](../configuration) - Configure credentials and instance settings
 - [CLI Reference](../../cli/code) - Equivalent CLI command: `b2c code deploy`

docs/mcp/tools/mrt-bundle-push.md

@@ -21,23 +21,13 @@ This tool is shared across the MRT, PWAV3, and STOREFRONTNEXT toolsets.
 
 ## Authentication
 
-Requires Managed Runtime (MRT) credentials:
-
-- `api-key` - MRT API key (from `~/.mobify` or `SFCC_MRT_API_KEY`)
-- `project` - MRT project slug (required, via `--project` flag or `SFCC_MRT_PROJECT`)
-- `environment` - MRT environment: `staging` or `production` (optional, required when `deploy: true`)
+Requires Managed Runtime (MRT) credentials. See [MRT Credentials](../configuration#mrt-credentials) for complete details.
 
 **Configuration priority:**
 1. Flags (`--api-key`, `--project`, `--environment`)
 2. Environment variables (`SFCC_MRT_API_KEY`, `SFCC_MRT_PROJECT`, `SFCC_MRT_ENVIRONMENT`)
 3. `~/.mobify` config file (or `~/.mobify--[hostname]` if `--cloud-origin` is set)
 
-You can also configure MRT credentials using the [B2C CLI](../../cli/mrt#b2c-mrt-config-set):
-
-```bash
-b2c mrt config set --api-key YOUR_API_KEY
-```
-
 ## Parameters
 
 | Parameter | Type | Required | Default | Description |
@@ -117,5 +107,6 @@ The tool will throw an error if:
 ## See Also
 
 - [MRT Toolset](../toolsets#mrt) - Overview of Managed Runtime tools
+- [Authentication Setup](../../guide/authentication#managed-runtime-api-key) - Set up MRT API key
 - [Configuration](../configuration) - Configure MRT credentials
 - [CLI Reference](../../cli/mrt) - Equivalent CLI command: `b2c mrt bundle push`

docs/mcp/tools/scapi-custom-apis-status.md

@@ -19,12 +19,9 @@ The `scapi_custom_apis_status` tool checks the registration status of custom API
 
 ## Authentication
 
-Requires OAuth credentials with the `sfcc.custom-apis` scope:
+Requires OAuth credentials. See [B2C Credentials](../configuration#b2c-credentials) (OAuth Client Credentials section) for complete details.
 
-- `hostname` - B2C instance hostname
-- `client-id` - OAuth client ID
-- `client-secret` - OAuth client secret
-- OAuth scope: `sfcc.custom-apis` (required)
+**Required scope:** `sfcc.custom-apis`
 
 **Configuration priority:**
 1. Flags (`--server`, `--client-id`, `--client-secret`)
@@ -199,5 +196,6 @@ Check the `message` field for detailed error information.
 
 - [SCAPI Toolset](../toolsets#scapi) - Overview of SCAPI discovery tools
 - [scapi_schemas_list](./scapi-schemas-list) - List and fetch SCAPI schemas
+- [Authentication Setup](../../guide/authentication#scapi-authentication) - Set up SCAPI authentication with required roles and scopes
 - [Configuration](../configuration) - Configure OAuth credentials
 - [CLI Reference](../../cli/custom-apis) - Equivalent CLI command: `b2c scapi custom status`

docs/mcp/tools/scapi-schemas-list.md

@@ -17,11 +17,9 @@ This tool works with both standard SCAPI (Shop, Admin, Shopper APIs) and custom
 
 ## Authentication
 
-Requires OAuth credentials with the `sfcc.scapi-schemas` scope:
+Requires OAuth credentials. See [B2C Credentials](../configuration#b2c-credentials) (OAuth Client Credentials section) for complete details.
 
-- `hostname` - B2C instance hostname
-- `client-id` - OAuth client ID
-- `client-secret` - OAuth client secret
+**Required scope:** `sfcc.scapi-schemas` (required for fetch mode)
 
 **Note:** OAuth credentials are optional for local schema discovery (list mode), but required for fetching full schemas.
 
@@ -166,5 +164,6 @@ Use the MCP tool to show me the full OpenAPI spec for shopper-products v1.
 
 - [SCAPI Toolset](../toolsets#scapi) - Overview of SCAPI discovery tools
 - [scapi_custom_apis_status](./scapi-custom-apis-status) - Check custom API endpoint registration status
+- [Authentication Setup](../../guide/authentication#scapi-authentication) - Set up SCAPI authentication with required roles and scopes
 - [Configuration](../configuration) - Configure OAuth credentials
 - [CLI Reference](../../cli/scapi-schemas) - Equivalent CLI commands: `b2c scapi schemas list` and `b2c scapi schemas get`