What does this MCP server do exactly?
It acts as a protected MCP server that authenticates clients via Entra ID, dynamically registers client applications, and uses the on‑behalf‑of flow to securely call Microsoft Graph.
@localden
基本信息
Remote MCP server with auth gated by Azure API Management
使用下面的配置,将此服务器添加到你的 MCP 客户端。
{
"mcpServers": {
"remote-auth-mcp-apim-py": {
"command": "npx",
"args": [
"@modelcontextprotocol/inspector@0.9.0"
]
}
}
}工具列表暂未提供
当前收录暂时没有可展示的工具列表,不代表服务没有工具。请查阅项目文档了解支持的能力。
点击上方按钮,在临时沙箱中运行此服务器并实时获取工具列表。
It is an experimental sample that shows how to deploy an Entra ID‑protected MCP server on Azure. The server uses an OAuth 2.0 authorization pattern where the client acquires a token for the server, then uses the on‑behalf‑of flow to exchange it for a Microsoft Graph access token. This is done in a completely secretless manner.
Install the Azure Developer CLI, clone the repository, register the Microsoft.App resource provider, log in with azd auth login, and deploy with azd up. After deployment, copy the endpoint and use the Model Context Protocol Inspector (or Visual Studio Code) with SSE transport and Bearer token authentication to connect. Test the get_graph_user_details tool to retrieve the authenticated user’s Microsoft Graph data.
It acts as a protected MCP server that authenticates clients via Entra ID, dynamically registers client applications, and uses the on‑behalf‑of flow to securely call Microsoft Graph.
No. The README explicitly marks it as an experimental implementation and warns it should not be used in production scenarios.
The server runs on Azure Functions and Azure API Management, deployed with Bicep and Python. Testing requires Node.js (for the MCP Inspector) and the Azure Developer CLI.
User data is retrieved live from Microsoft Graph via the on‑behalf‑of flow. Tokens are cached in API Management with encrypted session keys; no persistent user data is stored locally.
Transport uses Server‑Sent Events (SSE) with a Bearer token. Authentication follows OAuth 2.0 with PKCE, dynamic client registration, and multiple secure cookies for state correlation and CSRF protection.

ArtiBot Cloud MCP (Zhijiangyun 智匠云) — cloud MCP server for robot manipulation data & GPU workloads. 15 tools: robot fleet management, data collection & video recording, post-processing pipelines, and benchmark evaluation

One case file per task — shared by every session, agent and person that touches it. Self-hosted MCP server and live board. MIT.

Routebase keeps your API's design, docs, contract tests, mocks and monitoring in one living OpenAPI spec so they can't drift apart. Agents work on that same source of truth, under your team's permissions.


Local-first credential broker for MCP. AI coding agents (Claude Code, Cursor, Codex…) call APIs, SSH and databases through scoped presets; secrets stay in your OS keychain and never enter the agent's context.
评论