Azure Container Apps MCP Server

This project showcases how to use the MCP protocol with Azure OpenAI. It provides a simple example to interact with OpenAI's API seamlessly via an MCP server and client. Exposed over MCP by the azure container apps mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

This project showcases how to use the MCP protocol with OpenAI, Azure OpenAI and GitHub Models. It provides a simple demo terminal application that interacts with a TODO list Agent. The agent has access to a set of tools provided by the MCP server.

Its toolset

Everything the assistant can do here goes through one of these:

• Prerequisites — The Prerequisites tool exposed by this server
• Installation — The Installation tool exposed by this server
• OpenAI — To use the OpenAI API, you need to set your OPENAI_API_KEY key in the .env file:

Configuration

You will need 3 environment variables: AZURE_OPENAI_API_KEY, OPENAI_API_KEY, GITHUB_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js and npm (version 22 or higher) - Docker (recommended for running the MCP servers, and DocumentDB Local in Docker) - An OpenAI compatible endpoint: - An OpenAI API key - Or, a GitHub token, if you want to use the GitHub models: https://gh.io/models - Or, if you are using Azure OpenAI, you need to have an [Azure OpenAI

Adding it to your client

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

When to reach for it

Among the AI and media services options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Azure Container Apps's toolset — Prerequisites, Installation, OpenAI — is a fair guide to whether it matches your workflow. It is maintained by manekinekko; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Azure Container Apps's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• 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.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the azure container apps mcp server does with a few real requests.