MCP Graph API Demo

Created By
ovaismehbooba year ago
Overview

What is MCP Graph API Demo?

MCP Graph API Demo is a project that demonstrates the use of the Model Context Protocol (MCP) with Azure Graph API to query application registrations in an Azure tenant. It features a Blazor WebAssembly client that communicates with an ASP.NET Core server implementing the MCP protocol.

How to use MCP Graph API Demo?

To use the MCP Graph API Demo, you need to configure the application with your Azure credentials, run the server and client, and then access the chat interface to query information about your Azure App Registrations.

Key features of MCP Graph API Demo?

  • Chat interface for querying Azure tenant information
  • Integration with Microsoft Graph API for application registration data
  • Semantic Kernel integration for LLM functions
  • Secure separation of LLM and Graph API interactions

Use cases of MCP Graph API Demo?

  1. Querying application registrations in Azure AD
  2. Retrieving details about specific app registrations
  3. Managing permissions for Azure applications

FAQ from MCP Graph API Demo?

  • What is the Model Context Protocol (MCP)?

MCP is an architectural pattern for LLM-powered applications that separates LLM integration from tool/function integration.

  • What are the prerequisites to run this project?

You need .NET 9.0, an Azure subscription with Application Registration permissions, and access to Azure OpenAI or OpenAI API.

  • How do I configure the application?

Update the configuration files with your Azure credentials and API keys as described in the setup instructions.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ovaismehboob
Star
0
Language
C#
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.

14 minutes ago