Azure Container Apps - AI & MCP Playground

Created By
manekinekkoa year ago
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.
Overview

What is Azure OpenAI MCP Example?

Azure OpenAI MCP Example is a project that demonstrates how to use the MCP protocol with Azure OpenAI, providing a simple way to interact with OpenAI's API through an MCP server and client.

How to use Azure OpenAI MCP Example?

To use this project, clone the repository, install the dependencies, configure your Azure OpenAI endpoint or OpenAI API key, and then run the MCP server and client.

Key features of Azure OpenAI MCP Example?

  • Seamless interaction with OpenAI's API via MCP protocol.
  • Support for both Azure OpenAI and OpenAI API key authentication.
  • Easy setup and configuration with Node.js.

Use cases of Azure OpenAI MCP Example?

  1. Integrating OpenAI capabilities into applications using MCP protocol.
  2. Developing AI-driven applications that require natural language processing.
  3. Experimenting with OpenAI's models in a controlled environment.

FAQ from Azure OpenAI MCP Example?

  • What are the prerequisites for using this project?

You need Node.js (version 22 or higher), npm, and an OpenAI compatible endpoint.

  • Is there a license for this project?

Yes, this project is licensed under the MIT License.

  • Can I use this project with Azure OpenAI?

Yes, the project supports Azure OpenAI with keyless authentication.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
manekinekko
Star
3
Language
TypeScript
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago