A2A Support similiar to mcp? #6639
Replies: 3 comments 2 replies
-
I was thinking about the same thing. I imagine an usage like this where the SDK handles the communication with the agents and tools. const mcpClient = await createMCPClient({
transport: { type: 'sse', url: 'https://example.com/sse' },
})
const tools = await mcpClient.tools()
const agentClient = await createAgent({
url: 'https://example.com/.well-known/agent.json',
})
const agent = await agentClient.getAgent()
const result = await generateText({ model, tools, agents: { agent1: agent }, messages: [...] })
// ... Maybe it's still early, at the moment A2A allows maximum one agent per domain by using the |
Beta Was this translation helpful? Give feedback.
-
I started an effort to make a custom ai provider at https://github.com/DracoBlue/a2a-ai-provider for making things like this possible in v5 of ai sdk:
I kind of like it :)! |
Beta Was this translation helpful? Give feedback.
-
I attached the discussion to #7442 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
What do you think about having a2a agent's https://google.github.io/A2A/ integrated similiar to a way how mcp tools https://ai-sdk.dev/docs/ai-sdk-core/tools-and-tool-calling#mcp-tools are currently integrated?
[edit]: I started a a2a provider at https://github.com/DracoBlue/a2a-ai-provider for v5 of the ai sdk
Beta Was this translation helpful? Give feedback.
All reactions