Document x-mint.mcp for MCP tool configuration

api-playground/openapi-setup.mdx

@@ -130,7 +130,7 @@
 
 ## Customize your endpoint pages
 
 Customize your endpoint pages by adding the `x-mint` extension to your OpenAPI specification. The `x-mint` extension provides additional control over how your API documentation is generated and displayed.
 
 ### Metadata
 
@@ -208,7 +208,73 @@
 }
 ```
 
+### MCP
+
+Control which API endpoints are exposed as tools in your [MCP server](/ai/model-context-protocol) using `x-mint: mcp`. By default, all endpoints are available as MCP tools. Use this extension to exclude endpoints or customize how they appear to AI applications.
+
+```json {8-12}
+{
+  "paths": {
+    "/users": {
+      "get": {
+        "summary": "Get users",
+        "description": "Retrieve a list of users",
+        "x-mint": {
+          "mcp": {
+            "enabled": false
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+The `x-mint: mcp` extension supports these properties:
+
+| Property | Type | Description |
+| :------- | :--- | :---------- |
+| `enabled` | `boolean` | Set to `false` to exclude this endpoint from your MCP server. Defaults to `true`. |
+| `name` | `string` | Override the tool name that appears in AI applications. Defaults to the operation's `summary`. |
+| `description` | `string` | Override the tool description. Defaults to the operation's `description`. |
+
+This example excludes an internal endpoint and customizes another:
+
+```json {8-10, 21-25}
+{
+  "paths": {
+    "/internal/metrics": {
+      "get": {
+        "summary": "Get internal metrics",
+        "description": "Returns system metrics for monitoring",
+        "x-mint": {
+          "mcp": {
+            "enabled": false
+          }
+        }
+      }
+    },
+    "/users/search": {
+      "post": {
+        "summary": "Search users",
+        "description": "Search for users by various criteria",
+        "x-mint": {
+          "mcp": {
+            "name": "search_users",
+            "description": "Find users by name, email, or other attributes. Returns matching user profiles."
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+<Note>
+  The legacy `x-mcp` extension is still supported but deprecated. Use `x-mint: mcp` for new configurations.
+</Note>
+
 ### Href
 
 Set the URL of the autogenerated endpoint page using `x-mint: href`. When `x-mint: href` is present, the generated API page uses the specified URL instead of the default autogenerated URL.
 
@@ -239,11 +305,11 @@
 
 Add an `openapi` field to any navigation element in your `docs.json` to automatically generate pages for OpenAPI endpoints. You can control where these pages appear in your navigation structure, as dedicated API sections or with other pages.
 
 The `openapi` field accepts either a file path in your docs repo or a URL to a hosted OpenAPI document.
 
 Generated endpoint pages have these default metadata values:
 
 - `title`: The operation's `summary` field, if present. If there is no `summary`, the title is generated from the HTTP method and endpoint.
 - `description`: The operation's `description` field, if present.
 - `version`: The `version` value from the parent anchor or tab, if present.
 - `deprecated`: The operation's `deprecated` field. If `true`, a deprecated label appears next to the endpoint title in the side navigation and on the endpoint page.
@@ -259,7 +325,7 @@
 
 ### Dedicated API sections
 
 Generate dedicated API sections by adding an `openapi` field to a navigation element and no other pages. All endpoints in the specification are included.
 
 ```json {5}
 "navigation": {
@@ -301,7 +367,7 @@
 ```
 
 <Note>
   The `directory` field is optional and specifies where generated API pages are stored in your docs repo. If not specified, defaults to the `api-reference` directory of your repo.
 </Note>
 
 ### Selective endpoints
@@ -340,7 +406,7 @@
 
 #### OpenAPI spec inheritance
 
 OpenAPI specifications are inherited down the navigation hierarchy. Child navigation elements inherit their parent's OpenAPI specification unless they define their own.
 
 ```json {3, 7-8, 11, 13-14}
 {
@@ -365,7 +431,7 @@
 
 #### Individual endpoints
 
 Reference specific endpoints without setting a default OpenAPI specification by including the file path. You can reference endpoints from multiple OpenAPI specifications in the same documentation section.
 
 ```json {5-6}
 "navigation": {
@@ -419,7 +485,7 @@
 
 The method and path must exactly match your OpenAPI spec. If you have multiple OpenAPI specifications, include the path to the correct specification in your reference. You can also reference external OpenAPI URLs in `docs.json`.
 
 #### Autogenerate endpoint pages
 
 To autogenerate MDX files from your OpenAPI specification, use the Mintlify [scraper](https://www.npmjs.com/package/@mintlify/scraping).
 
@@ -471,7 +537,7 @@
 
 ## Webhooks
 
 Webhooks are HTTP callbacks that your API sends to notify external systems when events occur. Webhooks are supported in OpenAPI 3.1+ documents.
 
 Add a `webhooks` field to your OpenAPI document alongside the `paths` field.