@davidmoore-io/ms-365-mcp-server v1.0.1

ms-365-mcp-server

Microsoft 365 MCP Server - Fork with Pre-authenticated Token Support

Fork Notice: This is a fork of the original @softeria/ms-365-mcp-server with added support for pre-authenticated tokens via environment variables. This allows for better integration with applications that already handle Microsoft authentication.

A Model Context Protocol (MCP) server for interacting with Microsoft 365 services through the Graph API.

Prerequisites

• Node.js >= 14

Features

• Authentication via Microsoft Authentication Library (MSAL)
• Excel file operations
• Calendar event management
• Mail operations
• OneDrive file management
• OneNote notebooks and pages
• To Do tasks and task lists
• Planner plans and tasks
• Outlook contacts

Quick Start Example

Test login in Claude Desktop:

Examples

Integration

Claude Desktop

To add this MCP server to Claude Desktop:

Edit the config file under Settings > Developer:

{
  "mcpServers": {
    "ms365": {
      "command": "npx",
      "args": [
        "-y",
        "@davidmoore-io/ms-365-mcp-server"
      ]
    }
  }
}

Claude Code CLI

claude mcp add ms365 -- npx -y @davidmoore-io/ms-365-mcp-server

For other interfaces that support MCPs, please refer to their respective documentation for the correct integration method.

Authentication

⚠️ You must authenticate before using tools.

Option 1: Pre-authenticated Token (New!)

If you already have a Microsoft 365 access token (e.g., from your application), you can pass it via environment variable:

MS365_ACCESS_TOKEN="your-access-token" npx @softeria/ms-365-mcp-server

Or in your MCP configuration:

{
  "mcpServers": {
    "ms365": {
      "command": "npx",
      "args": ["-y", "@softeria/ms-365-mcp-server"],
      "env": {
        "MS365_ACCESS_TOKEN": "your-access-token"
      }
    }
  }
}

The server will validate the token on startup and use it for all API calls. If the token is invalid or expires, it will fall back to the standard authentication flow.

Option 2: Interactive Device Code Flow (Original)

1. MCP client login:
   • Call the login tool (auto-checks existing token)
   • If needed, get URL+code, visit in browser
   • Use verify-login tool to confirm
2. Optional CLI login:

   npx @softeria/ms-365-mcp-server --login

   Follow the URL and code prompt in the terminal.

Tokens are cached securely in your OS credential store (fallback to file).

CLI Options

The following options can be used when running ms-365-mcp-server directly from the command line:

--login           Login using device code flow
--logout          Log out and clear saved credentials
--verify-login    Verify login without starting the server

Server Options

When running as an MCP server, the following options can be used:

-v                Enable verbose logging
--read-only       Start server in read-only mode, disabling write operations

Environment variables:

• READ_ONLY=true|1: Alternative to --read-only flag
• LOG_LEVEL: Set logging level (default: 'info')
• SILENT=true: Disable console output

License

MIT © 2025 Softeria