From b3ae1c2ac379d4d9713ee67177dd117c01732fba Mon Sep 17 00:00:00 2001 From: Juan Antonio Osorio Date: Mon, 25 Aug 2025 19:29:41 +0300 Subject: [PATCH] Add OpenAPI example demonstrating publisher extensions (#299) This PR adds a new example to the OpenAPI specification that demonstrates the publisher extensions feature recently added in #298. ## Changes - Added \`example_org_server\` example to the OpenAPI spec - Demonstrates \`x-publisher\` fields for contact email and build metadata - Shows organization-specific extensions (\`x-com.example\`) including: - Marketplace icon URL - Category classification - Documentation URL - Verified publisher status This example helps developers understand how to use the new vendor extensions functionality when publishing servers to the registry. Co-authored-by: adam jones --- docs/server-registry-api/openapi.yaml | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/docs/server-registry-api/openapi.yaml b/docs/server-registry-api/openapi.yaml index 98d120a..f3b5048 100644 --- a/docs/server-registry-api/openapi.yaml +++ b/docs/server-registry-api/openapi.yaml @@ -104,6 +104,32 @@ paths: build_info: commit: "abc123def456" timestamp: "2023-12-01T10:30:00Z" + example_org_server: + summary: Server with example.com organization extensions + value: + server: + name: "com.example/demo-server" + description: "Example MCP server demonstrating publisher extensions." + status: "active" + repository: + url: "https://github.com/example/mcp-demo" + source: "github" + version_detail: + version: "1.0.0" + packages: + - registry_name: "npm" + name: "@example/mcp-demo-server" + version: "1.0.0" + x-publisher: + contact_email: "maintainer@example.com" + build_metadata: + commit: "abc123" + timestamp: "2024-01-15T10:30:00Z" + x-com.example: + marketplace_icon: "https://example.com/icon.png" + category: ["software_development"] + documentation_url: "https://docs.example.org" + verified_publisher: true responses: '200': description: Successfully published server