Ms 365 MCP Server

Ms 365 mcp server connects Ms 365 to AI assistants that speak the Model Context Protocol. A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API.

What Ms 365 does

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

Key capabilities

• Authentication via Microsoft Authentication Library (MSAL)
• Comprehensive Microsoft 365 service integration
• Read-only mode support for safe operations
• Tool filtering for granular access control
• Tool presets and dynamic discovery to shrink the tool surface and token usage

Tools it exposes

Once connected, the assistant can call this tool directly:

• Authentication — The Authentication tool exposed by this server

Installing the ms 365 mcp server

The server is distributed via npm as @softeria/ms-365-mcp-server, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Configuration

Before the server will start you need to supply 6 environment variables: MS365_MCP_CLIENT_ID, MS365_MCP_CLIENT_SECRET, OPENAI_API_KEY, MS365_MCP_TENANT_ID, MS365_MCP_OAUTH_TOKEN, MS365_MCP_EXPECTED_HOME_ACCOUNT_ID. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

• Node.js >= 20 (recommended) - Node.js 14+ may work with dependency warnings

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Ms 365 sits in that group, and the shape of its toolset — Authentication — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• Maintained by softeria, written in Go.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the ms 365 mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.