Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"mcp-client-server-graphapi": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
This project demonstrates the use of the Model Context Protocol (MCP) with Azure Graph API to query application registrations in your Azure tenant.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in cloud
⚡ A Simple / Speedy / Secure Link Shortener with Analytics, 100% run on Cloudflare.
MCP Server for GCP environment for interacting with various Observability APIs.
MCP server for Hostinger API
Apideck Unified API MCP — 229 tools across 200+ SaaS connectors (accounting, HRIS, file storage).
MCP Security Weekly
Get CVE alerts and security updates for Mcp_client_server_graphapi and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
This project demonstrates the use of the Model Context Protocol (MCP) with Azure Graph API to query application registrations in your Azure tenant.
The application uses a Blazor WebAssembly client that communicates with an ASP.NET Core server implementing the MCP protocol. The server connects to Microsoft Graph API to retrieve application registration data, which is then processed and presented through an AI-assisted chat interface.
+---------------------+ +---------------------+
| MCP Client | | MCP Server |
| | | |
| +---------------+ | MCP API | +--------------+ |
| | LLM | | Requests & | | Graph API | |
| | Integration |<-+-->Functions | | Functions |<--+--> Microsoft Graph API
| | (SK + OpenAI) | | | | | |
| +---------------+ | | +--------------+ |
| | | |
| +---------------+ | | +--------------+ |
| | UI/UX | | | | Azure AD | |
| | (Blazor WASM)| | | | Integration |<--+--> Azure Active Directory
| +---------------+ | | +--------------+ |
+---------------------+ +---------------------+
Client handles: Server handles:
- User Interface - Function Definitions
- Prompt Engineering - Graph API Integration
- LLM Integration - Azure AD Authentication
- Function Orchestration - Data Processing
This architecture strictly follows MCP principles where:
MCP.Client: Blazor WebAssembly client that interacts with the MCP server
MCP.Server: ASP.NET Core server that implements the MCP protocol for Azure Graph API
MCP.Shared: Shared models and interfaces between client and server
The Model Context Protocol (MCP) is an architectural pattern for LLM-powered applications that separates:
MCP provides a clean separation of concerns:
This project implements MCP by:
Before running the application, you need to configure it with your own Azure credentials:
Edit MCP.Server/appsettings.json and update the following settings:
"AzureAd": {
"Instance": "https://login.microsoftonline.com/",
... [View full README on GitHub](https://github.com/ovaismehboob/mcp_client_server_graphapi#readme)