Allow for vendor extensions in server.json #201

Activity

1. tadasant

   added

   product requirements workUpstream of development workUpstream of development work

   server.json

   on Jul 26, 2025
2. domdomegg commented on Aug 18, 2025

   

   domdomegg

   on Aug 18, 2025

   Member

   More actions

   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.
3. domdomegg commented on Aug 19, 2025

   

   domdomegg

   on Aug 19, 2025

   Member

   More actions

   To join up this and a couple other issues, I opened a discussion here with a concrete proposal for that tackles this and others: #284
4. domdomegg commented on Aug 20, 2025

   

   domdomegg

   on Aug 20, 2025

   Member

   More actions

   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 _meta to align with the rest of the MCP spec, should they be allowed in a server.json)
5. domdomegg

   closed this as not plannedon Aug 20, 2025