The A2A approach of putting agent cards at /.well-known/agent-card.json works well for point-to-point connections, but it skips the harder problem: how do you find the agents to connect to?
We have got at least three discovery mechanisms now. A2A well-known endpoints, MCP server listings, and agents.txt (which is an IETF draft that expires April 10, and nobody seems to be renewing it). Each assumes agents will discover peers through its own channel. None of them interoperate.
I have been building a cross-protocol registry that indexes agents across all three, so a tool like m2a could query "show me agents that do X" instead of requiring the exact URL upfront. The split between these protocols is only going to widen as more agents ship.
Are you thinking about adding any discovery layer, or staying focused on the "I already have the URL" use case?
1 comment
[ 6.0 ms ] story [ 13.2 ms ] threadWe have got at least three discovery mechanisms now. A2A well-known endpoints, MCP server listings, and agents.txt (which is an IETF draft that expires April 10, and nobody seems to be renewing it). Each assumes agents will discover peers through its own channel. None of them interoperate.
I have been building a cross-protocol registry that indexes agents across all three, so a tool like m2a could query "show me agents that do X" instead of requiring the exact URL upfront. The split between these protocols is only going to widen as more agents ship.
Are you thinking about adding any discovery layer, or staying focused on the "I already have the URL" use case?