What does this agent do versus other MCP implementations?
This agent provides a full C#/.NET MCP host and client that talks to a remote TypeScript MCP server. It is a sample to illustrate the MCP pattern using Azure OpenAI and Azure Container Apps.
@Azure-Samples
Basic information
Sample to create an AI Agent using OpenAI models with any MCP server running on Azure Container Apps
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
This is an MCP agent sample app written in .NET, using Azure OpenAI, that connects to a remote MCP to-do server written in TypeScript. The agent’s host and client are built with .NET Blazor, and both the client and server are deployed to Azure Container Apps. It is intended for developers who want to see a full MCP implementation with a Blazor UI and Azure OpenAI.
Use GitHub Codespaces or clone the repository with azd init -t openai-mcp-agent-dotnet. Set the environment name, then deploy with azd up. After deployment, navigate to the client app URL, log in (or bypass login by setting USE_LOGIN false), and enter natural‑language prompts like “Give me list of to do.” or “Set meeting at 1pm.” Clean up with azd down --force --prune.
azd up.This agent provides a full C#/.NET MCP host and client that talks to a remote TypeScript MCP server. It is a sample to illustrate the MCP pattern using Azure OpenAI and Azure Container Apps.
You need the .NET 9 SDK, Visual Studio Code with C# Dev Kit, node.js LTS, Docker Desktop or Podman Desktop, and an Azure subscription with an Azure AI Foundry instance.
The to‑do data is managed by the remote MCP server, which is deployed in your own Azure Container Apps environment. No data is stored outside your Azure subscription.
The sample uses the GPT-5-mini model by default and is intended for demo/prototyping. In production, you may need to adjust the model, auth mode (keyless vs. API key), and login settings.
The MCP client and server communicate over HTTP/HTTPS. The client app is secured by Azure Container Apps built‑in authentication (can be toggled off). The server is only accessible from the client app. Azure OpenAI can use either keyless (Microsoft Entra) or API key authentication, controlled by the `AOAI_USE_API_KEY` environment variable.
XDC AI is a remote MCP server available at https://xdcai.tech.
Model Context Protocol (MCP) server for Hostinger API. If you don't want to install or run anything locally, connect directly to Hostinger's hosted MCP server: This opens a browser window to authorize via OAuth. Once app
Run free live audience Q&A and polls from your agent: start an AskOne room, add and launch a poll, approve or hide questions and mark them answered, close the room, then read the questions as a FAQ draft and get the resu

Timestamp and verify evidence on-chain. Let your agent prove what it saw and when. bsv.cx gives an AI agent verifiable memory. Timestamp a hash of any output, archive a web page as it looked, or fetch a URL with a recei

scvd.store is an evidence observatory for agentic commerce. Independent signed observation of what other people's endpoints, artifacts and payments actually did among other things. USDC on Base, Arbitrum One, World Chain
Comments