Repository navigation
Allow for vendor extensions in server.json #201
Description
Activity
To match #81, maybe we should allow top-level
x-<domain>properties which can be custom. E.g.x-github.com? I kind of like this because then that means clients can consume and handle extension data consistently, regardless if it's because it's an API extension or an extension to server.json.I think as per the discussion in #284 we are not going to allow vendor extensions in server.json, so I am going to close this for now.
If people do have clear use cases for why this would be needed (and that registry API extensions, #81, are insufficient), do share more :)
(Also just for the sake of record keeping, if we do reopen this I think we came to the conclusion in #284 that we preferred to keep extensions under one top level property called
_metato align with the rest of the MCP spec, should they be allowed in a server.json)
#81 solves this for the registry API's with
x-*, but we should have an equivalent on server.json itself.Probably either:
_meta, like in the main MCP specGut is the former might make sense - but open to other thinking on this.