Back to all workshops
MCP in a Day: From “What is it?” to Real Solutions with Power Platform
Register nowOct 26th, 9:00AM - 4:00PM
About
If you’ve heard people mention the Model Context Protocol (MCP) but aren’t sure what it is- or how it can simplify your integrations with the Power Platform then-this full-day, demo-heavy workshop is for you.
We’ll start at first principles, providing an overview of what an MCP server, why so many organizations are leaning towards them, and why should you care. Next, we will have a look under the hood to learn about the components that make up an MCP server. As an example, we will be reviewing the using native MCP integrations, connecting to Dataverse via the Dataverse MCP Server. In our final section, we will be building and wiring a custom MCP server into a Power Platform agent. We’ll bring a familiar scenario to use for the live demos, to be able to see exactly how MCP will benefit you.
Along the way, you’ll see how MCP plays better together with Copilot Studio, GitHub Copilot, Microsoft 365, and more -- so you leave with working patterns you can take back to your team.
Key Takeaways:
- Explain key MCP concepts and components-: clients vs. servers, and the three capabilities (tools, resources, prompts).
- Add an MCP server to a Copilot Studio agent and review how actions/knowledge flow through the connector governance model (auth, DLP, VNets).
- Use the Dataverse MCP Server to list tables, describe schemas, and perform CRUD safely with environment-aware permissions.
- Build a custom MCP server using Azure Functions or containers and expose a few business-specific tools that an agent can invoke.
- Wire up “Better Together” scenarios that combine Power Platform with GitHub Copilot (MCP server in VS Code) and Microsoft 365 Copilot federated connectors for live data.
We’ll start at first principles, providing an overview of what an MCP server, why so many organizations are leaning towards them, and why should you care. Next, we will have a look under the hood to learn about the components that make up an MCP server. As an example, we will be reviewing the using native MCP integrations, connecting to Dataverse via the Dataverse MCP Server. In our final section, we will be building and wiring a custom MCP server into a Power Platform agent. We’ll bring a familiar scenario to use for the live demos, to be able to see exactly how MCP will benefit you.
Along the way, you’ll see how MCP plays better together with Copilot Studio, GitHub Copilot, Microsoft 365, and more -- so you leave with working patterns you can take back to your team.
Key Takeaways:
- Explain key MCP concepts and components-: clients vs. servers, and the three capabilities (tools, resources, prompts).
- Add an MCP server to a Copilot Studio agent and review how actions/knowledge flow through the connector governance model (auth, DLP, VNets).
- Use the Dataverse MCP Server to list tables, describe schemas, and perform CRUD safely with environment-aware permissions.
- Build a custom MCP server using Azure Functions or containers and expose a few business-specific tools that an agent can invoke.
- Wire up “Better Together” scenarios that combine Power Platform with GitHub Copilot (MCP server in VS Code) and Microsoft 365 Copilot federated connectors for live data.