And there's a concrete PR open at https://github.com/modelcontextprotocol/specification/pull/1... which suggests that there will be an auth capability with both oauth and credential (api keys etc) which seems like it will make it's way into the next release of the spec
Ah interesting. I'll have to dive in deeper here. If I understand correctly this essentially gives you exclusive core pinning? Do you find that you this reduces total utilization when workloads burst but they don't leverage the other unused cores?
And there's a concrete PR open at https://github.com/modelcontextprotocol/specification/pull/1... which suggests that there will be an auth capability with both oauth and credential (api keys etc) which seems like it will make it's way into the next release of the spec