chore: fix formatting

Author: kmruiz

README.md

@@ -24,7 +24,7 @@ A Model Context Protocol server for interacting with MongoDB Databases and Mongo
     - [MCP Client Configuration](#mcp-configuration-file-examples)
     - [Proxy Support](#proxy-support)
 - [🚀 Deploy on Public Clouds](#deploy-on-public-clouds)
-    - [Azure Cloud](#azure)
+  - [Azure Cloud](#azure)
 - [🤝 Contributing](#contributing)
 
 <a name="getting-started"></a>
@@ -698,7 +698,6 @@ You can deploy the MongoDB MCP Server to your preferred cloud provider using the
 
 For detailed Azure instructions, see [deploy/azure/README.md](deploy/azure/README.md).
 
-
 ## 🤝Contributing
 
 Interested in contributing? Great! Please check our [Contributing Guide](CONTRIBUTING.md) for guidelines on code contributions, standards, adding new tools, and troubleshooting information.

deploy/azure/README.md

@@ -1,14 +1,17 @@
 # Deploy MongoDB MCP Server on Azure Container Apps
 
 ## Overview
+
 This directory contains an Azure Bicep template (`bicep/main.bicep`) and supporting parameter files for deploying the infrastructure required to run the MongoDB MCP (Model Context Protocol) server. Use this guide to prepare prerequisites, select the appropriate parameter file, and run the deployment end-to-end.
 
 ## Prerequisites
+
 - Azure CLI (2.55.0 or later) installed and signed in (`az login`).
 - Azure subscription with permissions to deploy the required resources.
 - MongoDB MCP server container image available in dockerhub registry (mongodb/mongodb-mcp-server:latest).
 
 ## Parameter Files
+
 Two sample parameter files are provided to help you tailor deployments:
 
 - `bicep/params.json`: Baseline configuration that deploys the MongoDB MCP server with authentication disabled or using default settings. Use this when testing in development environments or when external authentication is not required.
@@ -17,7 +20,9 @@ Two sample parameter files are provided to help you tailor deployments:
 > **Tip:** Update the image reference, secrets, networking, and any other environment-specific values in the chosen parameter file before deployment.
 
 ## Deploy the Bicep Template
+
 1. **Set common variables (PowerShell example):**
+
    ```powershell
    $location = "eastus"
    $resourceGroup = "mongodb-mcp-demo-rg"
@@ -26,11 +31,13 @@ Two sample parameter files are provided to help you tailor deployments:
    ```
 
 2. **Create the resource group (if it does not exist):**
+
    ```powershell
    az group create --name $resourceGroup --location $location
    ```
 
 3. **Validate the deployment (optional but recommended):**
+
    ```powershell
    az deployment group what-if \
       --resource-group $resourceGroup \
@@ -39,6 +46,7 @@ Two sample parameter files are provided to help you tailor deployments:
    ```
 
 4. **Run the deployment:**
+
    ```powershell
    az deployment group create \
       --resource-group $resourceGroup \
@@ -49,15 +57,19 @@ Two sample parameter files are provided to help you tailor deployments:
 5. **Monitor outputs:** Review the deployment outputs and logs for connection endpoints, credential references, or other values needed to complete integration.
 
 ## Post-Deployment Checklist
+
 - After the Azure Container Apps deployment completes, access the MCP server by visiting the application’s public endpoint with /mcp appended. Example: https://[CONTAINER_APP_NAME].<region>.azurecontainerapps.io/mcp.
 
 ## Updating the Deployment
+
 To apply changes:
+
 1. Update the parameter file or `main.bicep` as needed.
 2. Re-run the `az deployment group create` command with the same resource group.
 3. Use `az deployment group what-if` to preview differences before applying them.
 
 ## Cleanup
+
 Remove the deployed resources when no longer needed:
 
 ```powershell

deploy/azure/bicep/paramsWithAuthEnabled.json

@@ -24,6 +24,8 @@
     "authClientId": { "value": "<AUTH_CLIENT_ID>" },
     "authIssuerUrl": { "value": "<AUTH_ISSUER_URL>" },
     "authTenantId": { "value": "<AUTH_TENANT_ID>" },
-    "authAllowedClientApps": { "value": ["<AUTH_ALLOWED_CLIENT_APP_1>","<AUTH_ALLOWED_CLIENT_APP_2>"] }
+    "authAllowedClientApps": {
+      "value": ["<AUTH_ALLOWED_CLIENT_APP_1>", "<AUTH_ALLOWED_CLIENT_APP_2>"]
+    }
   }
 }