.NET OpenAI MCP Agent MCP Server

If you already use .NET OpenAI MCP Agent, the .net openai mcp agent mcp server is the piece that lets your assistant work with it directly. Sample to create an AI Agent using OpenAI models with any MCP server running on Azure Container Apps.

What the server does

This is an MCP agent app written in .NET, using Azure OpenAI, with a remote MCP server written in TypeScript.

• The MCP host + MCP client app is written in .NET Blazor
• The MCP client app connects to a to-do MCP server written in TypeScript
• Both MCP client and server apps are running on Azure Container Apps (ACA)
• The MCP client app is secured by the built-in auth of ACA
• The MCP server app is only accessible from the MCP client app

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• csharp — bicep
• azure-openai — azure-container-apps

Credentials and setup notes

Configuration is passed through the environment: AOAI_USE_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• .NET 9 SDK - Visual Studio Code + C# Dev Kit - node.js LTS - Docker Desktop or Podman Desktop -

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

This sits in the cloud and infrastructure group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. .NET OpenAI MCP Agent's toolset — csharp, azure-openai — is a fair guide to whether it matches your workflow. It is maintained by Azure-Samples; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against .NET OpenAI MCP Agent's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.