>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.
You're right that I say both "above and not in place of" and "MCP needs to die"... I should that (but cant edit anymore).. it's unclear.... someday I see MCP being replaced by something else. But it's not my intention to completely replace MCP, but to solve the problem above it today.... I think that will be sufficient for today.
>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.
You're right that I say both "above and not in place of" and "MCP needs to die"... I should that (but cant edit anymore).. it's unclear.... someday I see MCP being replaced by something else. But it's not my intention to completely replace MCP, but to solve the problem above it today.... I think that will be sufficient for today.