jordanselig walks through how developers can connect Azure AI Foundry agents to any application using the Model Context Protocol (MCP) and App Service, with practical examples and deployment guidance.

Integrate Intelligent Agents with MCP and Azure AI Foundry on App Service

Introduction

Integrating AI into web applications is easier than ever thanks to MCP (Model Context Protocol) support within Azure AI Foundry Agent Service. This open standard enables developers to connect agents with remote tools and services through MCP servers, and with Azure App Service, both agents and MCP servers can be deployed and managed seamlessly—without custom code.

What is Model Context Protocol (MCP)?

MCP is an open protocol that serves as a standardized bridge between AI agents (such as those powered by large language models) and external applications, APIs, or data sources. With MCP:

  • Agents can dynamically discover available tools
  • Integration and tool sharing are standardized
  • Architecture is scalable for multiple apps and agents
  • Setup is simpler versus traditional API integration

Learn more about MCP: modelcontextprotocol.io.

Reference Implementation

This solution consists of two sample apps:

1. MCP Agent Client Application

2. Example MCP Server: To-do List

Deployment Guide

Prerequisites

  • Azure subscription
  • Azure Developer CLI (azd)
  • Python 3.11+

Steps

  1. Clone and deploy the MCP Agent Client:

    git clone https://github.com/Azure-Samples/app-service-mcp-foundry-agent-python.git
    cd app-service-mcp-foundry-agent-python
    azd auth login
    azd up
    

    Note: MCP support is in preview; select a supported region.

  2. Clone and deploy the Example MCP Server (to-do app):

    git clone https://github.com/Azure-Samples/app-service-python-todo-mcp.git
    cd app-service-python-todo-mcp
    azd up
    

Both apps will be provisioned as independent Azure App Service deployments.

Using the Solution

  • Obtain the MCP endpoint URL from the to-do server app
  • Enter it in the agent chat app
  • Chat with the agent in natural language to create and manage to-dos
  • See your operations reflected in real time

MCP vs. OpenAPI for Integrating AI Agents

Azure AI Foundry agents also support OpenAPI-defined tools. If you have legacy apps or lack MCP support, OpenAPI remains an alternative—and you can generate OpenAPI specs with GitHub Copilot if needed.

For more, see: How it works and App Service integration tutorial.

Expanding the Pattern

MCP means you can layer AI/LLM agent capabilities on nearly any application:

  • E-commerce (order management)
  • CRM (customer data queries)
  • Content management (AI-powered operations)
  • Finance (reporting, tracking)

Build an MCP-compatible service that exposes your app’s business logic, and connect agents without heavy refactoring.

Conclusion

The new MCP support in Azure AI Foundry enables rapid, low-effort integration of AI agents into Azure App Service-hosted applications. Follow the reference architecture to:

  • Quickly provision agent-connected solutions
  • Experiment with both MCP and OpenAPI models
  • Scale intelligent workflows across existing apps

For more details and related guidance, visit the Azure App Service documentation.

This post appeared first on “Microsoft Tech Community”. Read the entire article here