Swagger UI: Could not resolve reference: Could not resolve pointer: /components/schemas/ServerDetail does not exist in document

[dastrobu]

Describe the bug
Opening the POST endpoint in Swagger UI leads to the following error:

Could not resolve reference: Could not resolve pointer: /components/schemas/ServerDetail does not exist in document

To Reproduce
Steps to reproduce the behavior:

1. run the registry locally, following instructions from the Readme (docker build, docker compose up)

Expected behavior

Swagger UI is valid

Logs

Additional context

Tested revision: d42f11e

[joelverhagen]

This looks like another problem related to #159.

Essentially there are multiple schema definitions throughout the repo and it is very easy for them to get out of sync.

Stale? https://github.com/modelcontextprotocol/registry/blob/main/internal/docs/swagger.yaml
Stale? https://github.com/modelcontextprotocol/registry/blob/main/internal/docs/publish_swagger.yaml
Fresh? https://github.com/modelcontextprotocol/registry/blob/main/docs/server-registry-api/openapi.yaml

[tadasant]

Yeah, this is the source of truth:

Fresh? https://github.com/modelcontextprotocol/registry/blob/main/docs/server-registry-api/openapi.yaml

We need to get the rest in sync off that source of truth; have some WIP work moving in that direction (#176, #178)

I might not make much progress on #178 for a few days, so if someone is keen to work on it, happy to take help

[domdomegg]

Fixed in #262 :)