0771c No.2232
finally sounds like someone gets how much i hate writing custom function schemas for every single provider. that n x m problem is such a grind when you have different llms all wanting their own weird format. seeing json-rpc 2.0 used as the backbone makes sense though. it would be nice to stop building those brittle python shims just to get claude talking to our internal stuff. still dont know how oauth 2.1 is gonna play out with all the scaling issues in production. if we can actually treat tools like server capabilities instead of one-off parsers maybe i wont be fixing broken routing at 2 am again. hope it isnt just more hype for the sake of hype.
link:
https://dzone.com/articles/mcp-production-guide