Pls can we keep these in alphabetical order? Maybe the npm build script could reshuffle the file

Lets run that in check.yml workflow and if the clients are not sorted it will fail and user will need to run npm run sort locally and commit the correctly sorted version. I think we can somehow block the merge unless it is sorted.

This is interesting - how about we generate this table from the JSON file automatically using the build command? I'd keep the same columns as https://modelcontextprotocol.io/clients#feature-support-matrix

good idea 👍

Once we have a sufficient coverage, I think they might adopt our package too rather than having to maintain the table themselves

done - we are using the npm run generate-table

I would add this to the PR body template checklist and run that on release when updating changelog.

lets just keep that in the check workflow that runs on each PR (it will fail if not updated) - that will be simpler