MCP Microsoft Graph Server

MCP Microsoft Graph Server

An MCP (Model Context Protocol) server that provides secure access to Microsoft Entra ID (Azure AD) resources via Microsoft Graph API.

Features

• Users: Read user profiles, groups, licenses, and department information
• Devices: Access device inventory with OS and sign-in information
• Applications: Query application registrations and their properties
• Azure Integration: Logs all activities to Azure Blob Storage for audit purposes
• Security: Uses application permissions with client credentials flow

Prerequisites

• Azure tenant with admin access
• Python 3.8+
• Azure Storage account for logging

Setup

1. Azure App Registration

1. Go to Azure Portal → Microsoft Entra ID → App registrations → New registration
2. Configure:
   • Name: MCP-MSGraph-Server
   • Account types: Single tenant
   • No redirect URI needed
3. Note the Application (client) ID and Directory (tenant) ID

2. API Permissions

Add these Application permissions in API permissions:

• User.Read.All
• Group.Read.All
• Directory.Read.All
• Device.Read.All
• Application.Read.All

Important: Click "Grant admin consent" after adding permissions.

3. Client Secret

1. Go to Certificates & secrets → New client secret
2. Set expiration to 24 months (recommended)
3. Copy the secret value immediately

4. Azure Storage Setup

Create a storage account for logging:

1. Create storage account in Azure Portal
2. Get the connection string from Access keys
3. Container mcp-logs will be created automatically

Installation

Configuration

1. Copy .env.example to .env:

2. Update .env with your values:

Usage

Running the Server

Available Tools

1. get_entra_users

Get Microsoft Entra ID users with profile information.

Response includes:

• Display name and email
• Department information
• Group memberships
• Assigned licenses

2. get_entra_devices

Get registered devices in your tenant.

Response includes:

• Device name and OS
• Last sign-in timestamp
• Device ID

3. get_entra_applications

Get application registrations.

Response includes:

• Application name and ID
• Creation date
• Sign-in audience

OData Filtering

All tools support OData filter queries:

• startswith(displayName,'John') - Name starts with "John"
• mail eq 'user@domain.com' - Exact email match
• operatingSystem eq 'Windows' - Windows devices only
• createdDateTime ge 2024-01-01T00:00:00Z - Created after date

Logging

All API calls and operations are logged to Azure Blob Storage:

• Location: logs/YYYY/MM/DD/timestamp.json
• Format: Structured JSON with timestamp, level, message, and metadata
• Levels: INFO, ERROR
• Includes: Request details, response counts, error information

Security Best Practices

✅ Implemented:

• Application permissions (no user context required)
• Client credentials flow
• Token caching with expiration
• Secure environment variable configuration
• Comprehensive audit logging
• Request timeout protection

🔄 Recommended:

• Rotate client secrets every 24 months
• Monitor blob storage logs regularly
• Use Azure Key Vault for secrets in production
• Implement IP restrictions if needed
• Set up alerting on failed authentication attempts

Troubleshooting

Common Issues

1. "Insufficient privileges"
   • Verify admin consent was granted for API permissions
   • Check that application permissions (not delegated) were added
2. "Authentication failed"
   • Verify tenant ID, client ID, and client secret
   • Check that client secret hasn't expired
3. "Blob storage errors"
   • Verify storage connection string
   • Ensure storage account is accessible

Debugging

Enable verbose logging by checking blob storage logs:

• Authentication attempts
• API request details
• Error messages with context

License

This project follows security best practices for enterprise deployments.