Azure AI Foundry Agent MCP

Azure AI Foundry Agent MCP

Enables interaction with Azure AI Agent Service by automatically discovering agents and creating MCP tools for querying and managing agent workflows.

Category
Visit Server

README

Azure AI Foundry Agent MCP

This project provides an MCP (Model Context Protocol) server for integrating with Azure AI Agent Service. It is designed to help you interact with Azure-hosted AI agents, query them, and manage agent-related workflows in a secure and scalable way.

Features

  • Automatic discovery and registration of all Azure AI Agents from your service
  • Dynamically creates MCP tools for each agent in your Azure AI Agent Service
  • Supports both local and web transport modes
  • Regular background sync to detect new or changed agents

Project Structure

  • azure_agent_mcp_server/ — Main server code and tools
  • .env — Environment variables for configuration (see below)
  • pyproject.toml — Project dependencies and metadata
  • uv.lock — Lockfile for reproducible installs (managed by uv)

Notes

  • The most recent version of the AI Foundry SDK requires an AI Foundry Project. It doesn't support a hub based project currently. For more information about Azure AI Foundry project types, see the official documentation.

Getting Started

1. Prerequisites

  • Python 3.13+
  • uv (recommended for dependency management)
  • Azure AI Foundry project (no hub-based projects supported)
  • You get the project endpoint from the Azure AI Foundry portal. It looks like this:
    https://<your-ai-foundry-project-ressource>.services.ai.azure.com/api/projects/<your-ai-foundry-project-name>
    
  • You can find the project endpoint in the Azure AI Foundry portal under "Overview": AI Foundry Endpoint Location

2. Setup

  1. Clone the repository

  2. Configure environment variables:

    • Copy the provided .env file or create your own. Example:
      PROJECT_ENDPOINT=your-ai-foundry-project-endpoint
      
    • This variable is required for connecting to your Azure AI Agent Service.
  3. Install dependencies:

    • Using uv:
      uv pip install -r pyproject.toml
      
    • Or, to sync with the lockfile:
      uv sync
      
    • Alternatively, you can use pip or pipx if you prefer.

3. Running the Server

The server can run in two modes:

  • Local mode (default):

    uv run -m azure_agent_mcp_server  
    # Alternatively, you can run:
    # python -m azure_agent_mcp_server
    
  • Web mode (accessible via HTTP):

    # Set SERVER_TYPE=web in your .env file, or run with:
    SERVER_TYPE=web uv run -m azure_agent_mcp_server 
    # Alteratively, you can run:
    # SERVER_TYPE=web python -m azure_agent_mcp_server
    

When started, the server will:

  1. Connect to Azure AI Agent Service using the provided endpoint
  2. Automatically discover all your agents
  3. Create MCP tools for each agent
  4. Periodically check for new or updated agents every 300 seconds

4. Querying Agents in VSCode / GitHub Copilot

  1. Add MCP Server to VSCode settings:

    "mcp": {
         "servers": {
             "Azure AI Agents Server": {
                 "command": "uv",
                 "args": [
                     "--directory",
                     "/YOUR/PROJECT/PATH",
                     "run",
                     "-m",
                     "azure_agent_mcp_server"
                 ],
                 "env": {
                     "PROJECT_ENDPOINT": "your-ai-foundry-project-endpoint"
                 }
             }
         }
     },
    
  2. After the server starts, it automatically discovers all agents from your Azure AI Agent Service and makes them available as MCP tools with names based on the agent names (converted to snake_case).

  3. You can then use these tools directly in GitHub Copilot or any other MCP-compatible client.

  4. Good to know: Create a copilot-instructions.md file in the .github directory in your project to instruct copilot to streamline the usage of the MCP tools. For more information about repository custom instructions, see the GitHub documentation.

Environment Variables and Configuration

The MCP server can be configured using the following environment variables in your .env file:

  • PROJECT_ENDPOINT: Azure AI Foundry project endpoint (required)
  • SERVER_TYPE: Set to "local" (default) or "web" to choose the transport mode
  • SERVER_PORT: Port number for web mode (default: 8000)
  • SERVER_PATH: Path for web mode (default: "/")
  • UPDATE_INTERVAL: How often (in seconds) to check for new or updated agents (default: 300)
  • LOG_LEVEL: Set the logging level (default: "WARNING"). Options include "DEBUG", "INFO", "WARNING", "ERROR", and "CRITICAL".

Example .env file:

PROJECT_ENDPOINT=your-ai-foundry-project-endpoint
SERVER_TYPE=web
SERVER_PORT=9000
UPDATE_INTERVAL=120
LOG_LEVEL=INFO

Note: Never commit secrets to version control.

About uv

uv is a fast, modern Python package and project manager. It replaces tools like pip, pip-tools, pipx, poetry, and virtualenv, and is recommended for reproducible, efficient dependency management in this project.

How Agent Tools Work

The system automatically:

  1. Connects to Azure AI Agent Service on startup
  2. Discovers all agents available in your service
  3. Creates an MCP tool for each agent, converting the agent name to snake_case for the function name
  4. Sets the tool description to match the agent description
  5. Periodically checks for new, updated, or deleted agents
  6. Updates the available tools accordingly

Example:

  • An agent named "Coding Guidelines" becomes a tool named coding_guidelines
  • An agent named "Python Expert" becomes a tool named python_expert

License

This project is licensed under the MIT License. See the LICENSE file for details.

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured