entra-id -demo

This MCP server demonstrates Entra ID authentication integrated with MCP using the HTTP+SSE transport. It exposes a minimal yet functional authentication flow suitable for exploration and testing, rather than production workloads. To interact with the server, you’ll use an MCP client (such as MCP Inspector) to connect over HTTP+SSE, authenticate via Entra ID, and then issue MCP commands or subscribe to data streams as defined by the MCP protocol. The example focuses on showing how an Entra ID token can be validated and used to authorize MCP operations in an event-driven, streaming context.

Once running, you can connect your MCP client to the server endpoint, initiate the Entra ID login flow, and observe the authentication handshake, token validation, and subsequent authorized MCP messages. The included samples are designed to be adapted for stricter caching, token handling, and error scenarios in real-world deployments. If you’re evaluating tooling, MCP Inspector provides a convenient UI to inspect the HTTP+SSE MCP messages and verify auth behavior.

Prerequisites:

• Node.js (LTS version recommended)
• npm (comes with Node.js)
• Internet access to install dependencies

Install and run locally:

# Optional: clone the repository
# git clone https://github.com/your-organization/dend-entra-id-mcp-server-demo.git
# cd dend-entra-id-mcp-server-demo

# Install dependencies
npm install

# Build the project (if a build step exists)
npm run build

# Start the MCP server
npm run start

Notes:

• The server relies on Entra ID authentication scaffolding. Ensure you have the appropriate Entra ID app registrations configured or mocked during development.
• If you modify environment-specific settings (such as Entra ID tenant, client IDs, or redirect URIs), update the corresponding environment variables or configuration files before starting the server.

Tips and caveats:

• This repository is archived; use it for reference and learning rather than production deployment. For up-to-date patterns and samples, consult the reference collection linked in the README.
• If you customize token handling, consider adding proper caching, token refresh logic, and secure storage of credentials.
• When testing with MCP Inspector or similar tools, verify that the HTTP+SSE transport is correctly established and that Entra ID token validation occurs as expected.
• Ensure network access to Entra ID endpoints from your development environment and handle potential CORS or TLS-related issues during local testing.