* Fix agent_with_hosted_mcp sample to use AzureOpenAIResponsesClient (#4861) The agent_with_hosted_mcp sample used AzureOpenAIChatClient with an MCP tool dict, but the Chat Completions API only supports 'function' and 'custom' tool types, not 'mcp'. This caused a 400 error at runtime. Switch the sample to AzureOpenAIResponsesClient which natively supports MCP tools via the Responses API. Use get_mcp_tool() to construct the tool config. Changes: - main.py: Replace AzureOpenAIChatClient with AzureOpenAIResponsesClient - requirements.txt: Update azure-ai-agentserver-agentframework to 1.0.0b16 and use agent-framework-azure-ai package - agent.yaml: Use AZURE_OPENAI_RESPONSES_DEPLOYMENT_NAME env var - Add regression test documenting chat client MCP tool passthrough behavior Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Python: Fix agent_with_hosted_mcp sample to use Responses API client for MCP tools Fixes #4861 * Remove REPRODUCTION_REPORT.md investigation artifact (#4861) Remove the reproduction report markdown file from the test directory. Investigation notes belong in the GitHub issue or PR description, not as committed files in the source tree. The regression test in test_openai_chat_client.py already provides automated verification. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add MCP tool API rejection regression test (#4861) Add test_mcp_tool_dict_causes_api_rejection to verify that MCP tool dicts passed through to the Chat Completions API result in a clear ChatClientException rather than being silently dropped. This completes the regression test coverage requested in code review. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * small fix * Revert deletion of dotnet local.settings.json files Restore the two local.settings.json files that were accidentally deleted in this PR. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <copilot@github.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Hosted Agent Samples
These samples demonstrate how to build and host AI agents in Python using the Azure AI AgentServer SDK together with Microsoft Agent Framework. Each sample runs locally as a hosted agent and includes Dockerfile and agent.yaml assets for deployment to Microsoft Foundry.
Samples
| Sample | Description |
|---|---|
agent_with_hosted_mcp |
Hosted MCP tool that connects to Microsoft Learn via https://learn.microsoft.com/api/mcp |
agent_with_text_search_rag |
Retrieval-augmented generation using a custom BaseContextProvider with Contoso Outdoors sample data |
agents_in_workflow |
Concurrent workflow that combines researcher, marketer, and legal specialist agents |
agent_with_local_tools |
Local Python tool execution for Seattle hotel search |
writer_reviewer_agents_in_workflow |
Writer/Reviewer workflow using FoundryChatClient |
Common Prerequisites
Before running any sample, ensure you have:
- Python 3.10 or later
- Azure CLI installed
- An Azure OpenAI resource or a Microsoft Foundry project with a chat model deployment
Authenticate with Azure CLI
All samples rely on Azure credentials. For local development, the simplest approach is Azure CLI authentication:
az login
az account show
Running a Sample
Each sample folder contains its own requirements.txt. Run commands from the specific sample directory you want to try.
Recommended: uv
The sample dependencies include preview packages, so allow prerelease installs:
cd <sample-directory>
uv venv .venv
uv pip install --prerelease=allow -r requirements.txt
uv run main.py
Alternative: venv
Windows PowerShell:
cd <sample-directory>
python -m venv .venv
.\.venv\Scripts\Activate.ps1
pip install -r requirements.txt
python main.py
macOS/Linux:
cd <sample-directory>
python -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
python main.py
Each sample starts a hosted agent locally on http://localhost:8088/.
Environment Variable Setup
You can either export variables in your shell or create a local .env file in the sample directory.
Example .env for Azure OpenAI samples:
AZURE_OPENAI_ENDPOINT=https://<your-openai-resource>.openai.azure.com/
AZURE_OPENAI_DEPLOYMENT_NAME=gpt-4.1
Example .env for Foundry project samples:
FOUNDRY_PROJECT_ENDPOINT=https://<your-resource>.services.ai.azure.com/api/projects/<your-project>
FOUNDRY_MODEL=gpt-4.1
Interacting with the Agent
After starting a sample, send requests to the Responses endpoint.
PowerShell:
$body = @{
input = "Your question here"
stream = $false
} | ConvertTo-Json
Invoke-RestMethod -Uri "http://localhost:8088/responses" -Method Post -Body $body -ContentType "application/json"
curl:
curl -sS -H "Content-Type: application/json" -X POST http://localhost:8088/responses \
-d '{"input":"Your question here","stream":false}'
Example prompts by sample:
| Sample | Example input |
|---|---|
agent_with_hosted_mcp |
What does Microsoft Learn say about managed identities in Azure? |
agent_with_text_search_rag |
What is Contoso Outdoors' return policy for refunds? |
agents_in_workflow |
Create a launch strategy for a budget-friendly electric SUV. |
agent_with_local_tools |
Find me Seattle hotels from 2025-03-15 to 2025-03-18 under $200 per night. |
writer_reviewer_agents_in_workflow |
Write a slogan for a new affordable electric SUV. |
Deploying to Microsoft Foundry
Each sample includes a Dockerfile and agent.yaml for deployment. For deployment steps, follow the hosted agents guidance in Microsoft Foundry:
Troubleshooting
Missing Azure credentials
If startup fails with authentication errors, run az login and verify the selected subscription with az account show.
Preview package install issues
These samples depend on preview packages such as azure-ai-agentserver-agentframework. Use uv pip install --prerelease=allow -r requirements.txt or pip install -r requirements.txt.
ARM64 container images fail after deployment
If you build images locally on ARM64 hardware such as Apple Silicon, build for linux/amd64:
docker build --platform=linux/amd64 -t image .