adam jones
adam jones
Related: https://github.com/modelcontextprotocol/registry/issues/291 (search for MCP servers by updated at timestamp)
Recording decision: in today's maintainer meeting we agreed on [this](https://github.com/modelcontextprotocol/registry/issues/135#issuecomment-3208729181) for go live, combined with #291.
Related: #291 (in that I think it might be trying to tackle the same problem)
Possibly similar to https://github.com/onnx/tensorflow-onnx/issues/2354? Or maybe (less confident): - https://github.com/onnx/tensorflow-onnx/issues/2275 - https://github.com/onnx/tensorflow-onnx/issues/2055 - https://github.com/onnx/tensorflow-onnx/issues/2059
Would need to double check, but Anthropic very likely happy to fund API keys for this purpose :)
For 'Forces absolute paths', could this not work with using a path upwards to the repository root if you know how deep you are? E.g. `mcp-server-git --repository ../..`
Not sure it's fixed - @Avish34 happy for you to pick it up.
@annaji-msft are you able to write up a spec for exactly what metadata is needed here, ideally in the next few days? (or find someone who can). I think that...
> The metadata in the registry can help guide consumers a ClientId is expected for the specific MCP server as well as where to acquire it, usually link to service...
On a meta level, I might propose we downgrade this from 'go-live blocker' - it seems like adding this metadata would be a non-breaking change to server.json (as it would...