You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: api-playground/openapi-setup.mdx
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -208,7 +208,7 @@ Selectively expose endpoints as Model Context Protocol (MCP) tools by using `x-m
208
208
</ResponseField>
209
209
210
210
<CodeGroup>
211
-
```json Selective enablement {6-10, 21} wrap
211
+
```json Selective enablement {6-9} wrap
212
212
{
213
213
"paths": {
214
214
"/users": {
@@ -233,7 +233,7 @@ Selectively expose endpoints as Model Context Protocol (MCP) tools by using `x-m
233
233
}
234
234
```
235
235
236
-
```json Global enablement {3-5, 9-12} wrap
236
+
```json Global enablement {3-5, 9-13} wrap
237
237
{
238
238
"openapi": "3.1.0",
239
239
"x-mcp": {
@@ -368,7 +368,7 @@ Any page entry matching the format `METHOD /path` will generate an API page for
368
368
369
369
OpenAPI specifications are inherited down the navigation hierarchy. Child navigation elements inherit their parent's OpenAPI specification unless they define their own:
370
370
371
-
```json {5, 12-13, 18, 20-21}
371
+
```json {3, 7-8, 11, 13-14}
372
372
{
373
373
"group": "API reference",
374
374
"openapi": "/path/to/openapi-v1.json",
@@ -386,7 +386,7 @@ OpenAPI specifications are inherited down the navigation hierarchy. Child naviga
0 commit comments