M365 Graph Interface for Advanced Processing Servers

This server component establishes an MCP endpoint providing authenticated access to a user's Microsoft 365 environment, utilizing the official Microsoft Graph SDK for interaction with Exchange Online (Mail/Calendar) and OneDrive/SharePoint data stores.

---

🌟 Core Capabilities

• Email Management: Perform comprehensive operations including message composition, replies, inbox organization (sorting, filtering), advanced querying, and content analysis.
• Scheduling Functions: Query existing appointments, create new meeting entries, modify events, and transmit invitations.
• Document Access (OneDrive): Locate files, retrieve associated metadata, and facilitate content retrieval.
• Enterprise Document Access (SharePoint): Load drive structures, execute file searches, and obtain asset metadata across SharePoint sites.

---

🛠️ Implementation Details

• API Client: Built upon the official msgraph-sdk-python.
• Authentication Flow: Employs azure.identity library, configured specifically for device code flow (DeviceCodeCredential) coupled with token caching persistence.
• Server Framework: Implements the necessary interface using FastMCP for rapid deployment and compliance with the Machine Computation Protocol.
• Environment Management: Relies on uv for streamlined dependency resolution and virtual environment maintenance.

---

⚙️ Operational Prerequisites

This implementation is currently tailored for the following environment:

• Local execution targeted primarily for macOS.
• Designed for interoperability with the Claude Desktop application.
• Requires prior configuration of an Azure Active Directory application registration.

⚠️ Administrative Prerequisite: Successful deployment mandates administrative rights within the target Azure tenancy. Granting the necessary Graph API permissions (e.g., Mail.Read, Calendars.Read) often requires tenant-level administrative consent, as these scopes are typically restricted from standard delegated user authorization.

---

🚀 Initial Deployment Steps

1. Repository Acquisition and Navigation

git clone https://github.com/Norcim133/OutlookMCPServer.git
cd OutlookMCPServer

2. Environment Setup

uv venv
uv sync

3. Local Server Initialization via MCP Inspector

mcp dev main.py (Initial startup may report transient errors)

It is strongly recommended to validate functionality using the dedicated MCP Inspector utility prior to attempting integration with the Claude environment, as this simplifies initial debugging.

---

🔐 Credential Configuration

Before initiating the server process, the following setup steps for authentication must be completed:

1. Establish an auth_cache directory within the project's root location:

mkdir -p auth_cache

1. Generate and populate a configuration file named .env in the root directory:

touch .env

1. Inject required parameters into the .env file:

echo "AZURE_CLIENT_ID=<Your-App-Registration-Client-ID-Here>" > .env
echo "AZURE_TENANT_ID=<Your-Directory-Tenant-ID-Here>" >> .env
echo "AZURE_GRAPH_SCOPES=User.Read Mail.Read Mail.Send Mail.ReadWrite" >> .env

NOTE: Additional environment variables are needed specifically for file access services (OneDrive/SharePoint). NOTE: Upon successful execution of the device code flow on the first run, the resulting authentication token set will be persisted as auth_record.json inside the auth_cache directory.

Tenant Administrator Consent Required

Registration of the application and assignment of the broad permissions necessitate administrative privileges within the Azure Active Directory environment.

---

🖥️ Integration with Claude Desktop

To enable Claude Desktop to route requests to this server, modify your claude_desktop_config.json by appending the following configuration block:

{
  "mcpServers": {
    "outlook": {
      "command": "uv",
      "args": [
        "run",
        "--with",
        "azure-identity,mcp[cli],msgraph-core,msgraph-sdk",
        "mcp",
        "run",
        "/absolute/path/to/OutlookMCPServer"
      ]
    }
  }
}

This configuration file is accessible via Claude Desktop's Settings $\rightarrow$ Developer $\rightarrow$ Edit Config.

NOTE: If uv execution fails, it may be necessary to substitute the literal absolute path to the uv executable within the command field.

Configuration Persistence

Remember to restart the Claude Desktop application whenever modifications are made to either the configuration file or the server source code.

---

📁 Project Directory Layout

.
├── README.md
├── main.py
├── settings.py
├── auth_cache/
│   └── auth_record.json
├── mcpserver/
│   └── graph/
│       ├── __init__.py
│       ├── calendar_service.py
│       ├── controller.py
│       ├── file_service.py
│       ├── mail_service.py
│   ├── __init__.py
│   ├── auth_wrapper.py
│   ├── context_manager.py
│   ├── mail_query.py
│   ├── message_info.py
│   └── server.py
├── tests/
├── .env
├── __init__.py
├── main.py

---

📌 Development Milestones Achieved

• Email Interaction Module (Completed)
• Desktop Authentication Mechanism (Completed)
• Calendar Event Handling (Completed)
• Personal File Storage Access (Completed)
• Enterprise File Storage Access (Completed)

---

📄 Licensing Information

MIT License

Copyright (c) 2024 Enthoosa AI

Permission is hereby granted, free of charge, to any individual obtaining a copy of this software and associated documentation files (the "Software"), to engage in the Software without limitation, including without restriction the rights to employ, duplicate, alter, combine, disseminate, sublicense, and/or offer for sale copies of the Software, subject to the following stipulations:

The preceding copyright notice and this full permission statement must be integrated into all derivative works or substantial portions of the Software.

THE SOFTWARE IS FURNISHED "AS IS," WITHOUT WARRANTY OF ANY NATURE, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO WARRANTIES OF MERCHANTABILITY, SUITABILITY FOR A SPECIFIC PURPOSE, AND NON-INFRINGEMENT. IN NO INSTANCE SHALL THE COPYRIGHT HOLDERS OR AUTHORS BE LIABLE FOR ANY SUIT, DAMAGES, OR OTHER LIABILITY, WHETHER IN AN AGREEMENT, TORT, OR OTHERWISE, ARISING FROM, OUTSIDE OF, OR IN CONNECTION WITH THE SOFTWARE OR THE USAGE OR OTHER DEALINGS WITHIN THE SOFTWARE.

WIKIPEDIA REFERENCE: Cloud computing describes a model where dynamically provisioned, scalable, and elastic computing resources are accessed over a network on an on-demand basis, as defined by ISO. This concept is ubiquitously termed "the cloud."

== Defining Characteristics (NIST 2011) == The National Institute of Standards and Technology (NIST) established five foundational attributes for cloud systems in 2011. The precise definitions are as follows:

On-demand self-service: "A consumer autonomously secures computing capacity, such as processor time or network storage, as required, automatically, without requiring direct personnel intervention from the service provider for each request." Broad network accessibility: "Services are reachable via the network utilizing standardized protocols, promoting consumption across diverse endpoint platforms (e.g., mobile devices, workstations, laptops)." Resource pooling: "The provider aggregates computational assets to serve a multi-tenant user base, where underlying physical or virtual infrastructure is dynamically allocated and reallocated based on fluctuating user demands." Rapid elasticity: "Capabilities can be scaled up or down swiftly, sometimes automatically, to match evolving demand profiles. From the consumer's perspective, the available capacity often appears limitless and instantly obtainable in any volume." Metered service: "Cloud systems incorporate automated metering to track, govern, and optimize resource consumption at an appropriate service abstraction layer (e.g., bandwidth, CPU cycles, storage volume). This transparency allows for precise monitoring, control, and reporting for both the service consumer and the operator." Subsequent refinement of these criteria occurred through updates by the International Organization for Standardization (ISO) by the year 2023.

== Historical Context == The genesis of cloud computing traces back to the 1960s, focusing on the nascent concept of time-sharing via remote job entry (RJE) systems. In this period, the centralized "data center" paradigm prevailed, where users submitted batch jobs to dedicated operators managing mainframe systems. The primary goal was exploring methods to democratize access to significant computational power through optimized infrastructure, platform deployment, and application efficiency. The visual representation of shared services as a "cloud" originated in 1994, employed by General Magic to depict the conceptual domain accessible by agents within their Telescript architecture. David Hoffman, a communications strategist at General Magic, is credited with adapting this metaphor from its pre-existing usage within telecommunications networking. The term "cloud computing" gained broader market recognition in 1996 following a strategic business plan developed by Compaq Computer Corporation concerning future internet-based computation. The firm's objective focused on significantly enhancing...