← Discover MCPs and Agents
i
MCPOtherMCP Registry

ignite25-LAB513-build-a2a-and-mcp-systems-using-swe-agents-and-agent-framework

Links

README

From the repo.

decorative banner

Microsoft Ignite 2025

🔥LAB513: Build A2A and MCP Systems using SWE Agents and agent-framework

Microsoft Foundry Discord Microsoft Foundry Developer Forum

Session Description

Learn to leverage Microsoft Agent Framework, the new unified platform from Semantic Kernel and AutoGen engineering teams, to build A2A compatible agents similar to magnetic-one. Use SWE Agents (GitHub Copilot coding agent and Codex with Azure OpenAI models) to accelerate development. Implement MCP tools for secure enterprise agentic workflows. Experience hands-on building, deploying, and orchestrating multi-agent systems with pre-release capabilities. Note: Contains embargoed content.

📁 Repository

For detailed lab instructions and hands-on exercises, navigate to the spec-to-agents repository. The Skillable related instructions can be found in lab/instructions directory.

🧠 Learning Outcomes

By the end of this session, learners will be able to:

  • Build A2A (Agent-to-Agent) compatible agents using Microsoft Agent Framework
  • Implement MCP (Model Context Protocol) tools for secure enterprise workflows
  • Deploy and orchestrate multi-agent workflows

🌟 Microsoft Learn MCP Server

Install in VS Code

The Microsoft Learn MCP Server is a remote MCP Server that enables clients like GitHub Copilot and other AI agents to bring trusted and up-to-date information directly from Microsoft's official documentation. Get started by using the one-click button above for VSCode or access the mcp.json file included in this repo.

For more information, setup instructions for other dev clients, and to post comments and questions, visit our Learn MCP Server GitHub repo at https://github.com/MicrosoftDocs/MCP. Find other MCP Servers to connect your agent to at https://mcp.azure.com.

Note: When you use the Learn MCP Server, you agree with Microsoft Learn and Microsoft API Terms of Use.

📚 Resources and Next Steps

ResourcesLinksDescription
Ignite 2025 Next Stepshttps://aka.ms/Ignite25-Next-StepsLinks to all repos for Ignite 2025 Sessions
Microsoft Foundry Community DiscordMicrosoft Foundry DiscordConnect with the Microsoft Foundry Community!
Learn at Ignitehttps://aka.ms/LearnAtIgniteContinue learning on Microsoft Learn

Content Owners

Core AI Engineering Team

🚀 Try Azure for Free!

Ready to build, experiment, or scale your next project? Kick things off with an Azure Free Trial and get access to popular services, generous monthly credits, and the tools you need to ship fast. 👉 Start your free journey here: https://aka.ms/devrelft

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit Contributor License Agreements.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.

Collected info

  • 19 stars
  • 15 forks
  • Source updated: 1/22/2026

Config for your environment

Replace {MCP_ENDPOINT_URL} with this MCP’s endpoint URL (from its repo or docs above). No API key — you connect directly.

Tool

OS

Config file: ~/.cursor/mcp.json

{
  "mcpServers": {
    "mcp-server": {
      "url": "{MCP_ENDPOINT_URL}"
    }
  }
}

Paste into mcpServers in the config file. Restart Cursor after saving.

If this MCP is also published on mcpchannel.ai, you can subscribe from Browse and use the gateway config there instead.