Azure AI Foundry Agent MCP
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Azure AI Foundry Agent MCPask my sales agent about Q4 revenue forecast"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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 metadatauv.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":

2. Setup
Clone the repository
Configure environment variables:
Copy the provided
.envfile or create your own. Example:PROJECT_ENDPOINT=your-ai-foundry-project-endpointThis variable is required for connecting to your Azure AI Agent Service.
Install dependencies:
Using uv:
uv pip install -r pyproject.tomlOr, to sync with the lockfile:
uv syncAlternatively, you can use
piporpipxif 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_serverWeb 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:
Connect to Azure AI Agent Service using the provided endpoint
Automatically discover all your agents
Create MCP tools for each agent
Periodically check for new or updated agents every 300 seconds
4. Querying Agents in VSCode / GitHub Copilot
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" } } } },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).
You can then use these tools directly in GitHub Copilot or any other MCP-compatible client.
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 modeSERVER_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=INFONote: 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.
See uv documentation for more details.
How Agent Tools Work
The system automatically:
Connects to Azure AI Agent Service on startup
Discovers all agents available in your service
Creates an MCP tool for each agent, converting the agent name to snake_case for the function name
Sets the tool description to match the agent description
Periodically checks for new, updated, or deleted agents
Updates the available tools accordingly
Example:
An agent named "Coding Guidelines" becomes a tool named
coding_guidelinesAn 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.
This server cannot be installed
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/sebafo/azure-ai-foundry-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server