diff --git a/content/guides/box-mcp/remote/index.md b/content/guides/box-mcp/remote/index.md
index 4687e3974..fbcfa46e8 100644
--- a/content/guides/box-mcp/remote/index.md
+++ b/content/guides/box-mcp/remote/index.md
@@ -18,8 +18,8 @@ The remote Box MCP Server allows third party AI systems to securely connect and
 1. Click **Integrations** in the sidebar of Box Admin Console. 
 2. Click **Box Integrations & Clients** in the Integrations window.
 3. Scroll down to **Individual Integration Controls**.
-4. Go to the **Box MCP Server for Copilot Studio (Beta)**, or **Box MCP Server for Azure API Center (Beta)** sections. 
-5. Click the state icon for the selected MCP server, then choose the state you want to enable.
+4. Search for predefined Box MCP Server, for example the **Box MCP Server for Copilot Studio (Beta)**. 
+5. Hover on the chosen integration, then click **Configure**.
 6. Click Save.
 
 ## Create an unlisted Box MCP Server
@@ -31,9 +31,9 @@ To create a new, unlisted Box MCP Server:
 3. Search for **Box MCP Server**. 
 4. Hover on the **Box MCP Server** application, then click **Configure**.
 5. In the **Additional Configuration** section, click on **+ Add Integration Credentials**.
-6. Copy the generated Client ID and Client Secret.
-7. Enter the Redirect URI provided by the external MCP Client.
-8. Under Scopes, ensure that *Manage AI* is selected.
+6. Enter the Redirect URI provided by the external MCP Client. 
+7. Copy the generated Client ID and Client Secret.
+8. Under Scopes, ensure that *Manage AI Requests* is selected.
 
 ## Add Box MCP Server to MCP clients
 
diff --git a/content/guides/box-mcp/self-hosted/index.md b/content/guides/box-mcp/self-hosted/index.md
index 3be3e4a15..e05fe1365 100644
--- a/content/guides/box-mcp/self-hosted/index.md
+++ b/content/guides/box-mcp/self-hosted/index.md
@@ -446,6 +446,35 @@ Alternatively, in the main Claude navigation choose `Settings`. Select the Devel
   </tbody>
 </table>
 
+### Box Metadata tools
+
+<table>
+  <thead>
+    <tr>
+      <th>Tool</th>
+      <th>Description</th>
+      <th>Parameters</th>
+      <th>Returns</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>`box_metadata_template_get_by_key_tool`</td>
+      <td>Retrieves a metadata template by its key.</td>
+      <td>
+        `template_name (str)`: The key of the metadata template to retrieve.
+      </td>
+      <td>The metadata template associated with the provided key.</td>
+    </tr>
+    <tr>
+      <td>`box_metadata_template_get_by_name_tool`</td>
+      <td>Retrieve a metadata template by its name.</td>
+      <td>`template_name (str)`: The name of the metadata template to retrieve.</td>
+      <td>The metadata template associated with the provided name.</td>
+    </tr>
+  </tbody>
+</table>
+
 ## Troubleshooting
 
 In case of an `Error: spawn uv ENOENT` on MacOS when running the MCP server with Claude Desktop, you can:
diff --git a/content/guides/getting-started/sandbox.md b/content/guides/getting-started/sandbox.md
index 2b836e184..77881183d 100644
--- a/content/guides/getting-started/sandbox.md
+++ b/content/guides/getting-started/sandbox.md
@@ -10,11 +10,11 @@ related_guides:
 
 Developer sandboxes in Box provide a secure, controlled environment where developers can build, test, and collaborate on applications without affecting the actual data of your enterprise. They offer a safe space to experiment with Box APIs, test settings, try new integrations, and work alongside external partners.
 
-## What is a developer sandbox?
+## What is a developer sandbox
 
 A developer sandbox is an environment isolated from your production (live) enterprise setup that keeps development activities separate from real business data.
 
-## Why use a sandbox?
+## Why use a sandbox
 
 Using a sandbox allows you to: