Add client credentials docs for MCP servers

ai/model-context-protocol.mdx

@@ -38,7 +38,7 @@
 The MCP search tool supports optional parameters that AI applications use to control and refine search results.
 
 - **`pageSize`**: Number of results to return, between 1 and 50. Defaults to 10.
 - **`scoreThreshold`**: Minimum relevance score between 0 and 1. Only returns results at or above this threshold. Use this to filter out low-relevance matches.
 - **`version`**: Filter results to a specific documentation version. For example, `'v0.7'`. Only returns content tagged with the specified version or content available across all versions.
 - **`language`**: Filter results to a specific language code. For example, `'en'`, `'zh'`, or `'es'`. Only returns content in the specified language or content available across all languages.
 
@@ -104,6 +104,57 @@
   </Step>
 </Steps>
 
+### Client credentials
+
+Client credentials let server-side applications access your authenticated MCP endpoints without a user login flow. Use client credentials when you need machine-to-machine access to your MCP server, such as from a backend service, CI/CD pipeline, or automated workflow.
+
+With client credentials, your application authenticates directly with a client ID and client secret instead of going through an interactive OAuth login. The MCP server issues a token that grants the same access as an authenticated user.
+
+<Steps>
+  <Step title="Create a client credential">
+    1. Navigate to the [MCP server page](https://dashboard.mintlify.com/products/mcp) in your dashboard.
+    2. In the **Client credentials** section, click **Create credential**.
+    3. Enter a label to identify this credential, such as `production-backend` or `ci-pipeline`.
+    4. Copy the **client ID** and **client secret**. The client secret is only shown once and cannot be retrieved later.
+  </Step>
+  <Step title="Exchange credentials for a token">
+    Send a POST request to your MCP server's token endpoint with your client ID and client secret to receive an access token.
+
+    ```bash
+    curl -X POST https://<your-docs-domain>/authed/mcp/oauth/token \
+      -H "Content-Type: application/json" \
+      -d '{
+        "grant_type": "client_credentials",
+        "client_id": "<your-client-id>",
+        "client_secret": "<your-client-secret>"
+      }'
+    ```
+
+    The response includes an access token:
+
+    ```json
+    {
+      "access_token": "<token>",
+      "token_type": "Bearer"
+    }
+    ```
+
+    Tokens expire after two weeks. Your application should request a new token before the current one expires.
+  </Step>
+  <Step title="Use the token with authenticated MCP endpoints">
+    Pass the token as a Bearer token when connecting to the `/authed/mcp` endpoint. Your MCP client or HTTP requests should include the token in the `Authorization` header.
+
+    ```bash
+    Authorization: Bearer <token>
+    ```
+  </Step>
+</Steps>
+
+You can manage your client credentials from the dashboard:
+
+- **Disable a credential** to temporarily revoke access without deleting it.
+- **Delete a credential** to permanently revoke access. Deleted credentials cannot be recovered.
+
 ### Rate limits
 
 To protect availability, Mintlify applies rate limits to MCP servers.