>AAP sits above transport protocols. MCP is a valid execution backend — so are function calling, REST, and CLI. AAP defines the what. Transport protocols define the how.

>[MCP] needs to die a SOAP death so REST can rise in it's place.

So is AAP a replacement for MCP or something that sits above it? If the latter, why use AAP over Skills?

Also, IMO the biggest problem with MCP is that it's over-specced and over-constrained. This feels even more over-specced.