Tag: a2a

The agent-framework-hosting packages are conversion helpers, not a runtime. One Agent instance, one AgentState, and three thin adapters give you a Telegram bot, an A2A peer, and an MCP tool from the same process. Here is the wiring, the per-channel session-ID policy, and the four things each channel refuses to do.

There is no single Skill type in the Microsoft Agent Framework, but you can package domain expertise as a reusable agent, reuse it in-process with AsAIFunction, and advertise it across frameworks as an A2A AgentSkill. Full walkthrough on Agent Framework 1.0 and .NET 11.

MCP connects one agent to its tools, A2A connects independent agents to each other. They are not competitors. Add MCP first, reach for A2A only when you have multiple separately deployed agents. Here is the wire-level difference and the code.