Log inSubmit server
Microsoft 365 Admin logo

Microsoft 365 Admin

Administers Microsoft 365 through Graph API application permissions, with read-only defaults and security, audit, identity, and reporting tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Microsoft 365 Admin

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "microsoft-365-admin": {
      "command": "npx",
      "args": [
        "-y",
        "@okapi-ca/ms-365-admin-mcp-server"
      ],
      "env": {
        "MS365_ADMIN_MCP_CLIENT_ID": "YOUR_VALUE_HERE",
        "MS365_ADMIN_MCP_CLIENT_SECRET": "YOUR_VALUE_HERE",
        "MS365_ADMIN_MCP_TENANT_ID": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 412 tools correctly (3d ago).

Overview

Microsoft 365 Admin MCP server connects MCP clients to Microsoft Graph using Azure AD application permissions and client credentials. It exposes tools for security alerts and incidents, attack simulations, directory audits, sign-ins, service health, usage reports, and user lookups. Operations are read-only by default, while supported write actions require explicit write enablement and carry risk classifications. Reach for it when an agent needs tenant-level administration without delegated user interaction.

Use cases

  • Review Microsoft 365 security alerts and incidents
  • Inspect directory audits, sign-ins, and provisioning logs
  • Check Microsoft 365 service health and service issues
  • Generate usage reports across Microsoft 365 workloads
  • Look up users and their group memberships

Key features

  • Microsoft Graph access with application permissions
  • Read-only operation by default
  • Risk classifications for write tools
  • Security, audit, identity, health, and usage tools
  • Stdio and Streamable HTTP transports
  • Global and China cloud support

Tools412

What Microsoft 365 Admin lets your agent do. Expand a tool for its parameters.

Verified live~112.9k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

9/9 checks healthy over the last 51d

What it can do

From the 412 tools this server returned when we ran it; 412 declare their own safety hints.

Runs commands · 4Handles credentials · 29Makes network requests · 412Read-only tools · 408
Network at startup3 connections
Files written at startup2
Install scriptsNone
npm provenanceSigned build
Package age190 days
Maintainers1

Observed 2026-10-25 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 17h ago via OSV.dev · @okapi-ca/ms-365-admin-mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars18Stargazers on the source repository.
npm downloads248Package downloads in the last 30 days.
Last commit2d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed412Callable tools this server registers over MCP.

How Microsoft 365 Admin works

What Microsoft 365 Admin does

The Microsoft 365 Admin MCP server gives an MCP client access to Microsoft 365 administration through Microsoft Graph application permissions. It is designed for tenant-level work rather than end-user productivity tasks, using client credentials so an interactive user sign-in is not required.

The listed tools cover several administrative areas:

  • Security alerts and incidents, including retrieval and supported updates
  • Attack simulation discovery, retrieval, creation, updates, and deletion
  • Directory audit events, sign-in records, provisioning logs, and deleted users or groups
  • Microsoft 365 service health, issues, and service messages
  • Usage reports for Teams, email, active users, SharePoint, OneDrive, mailboxes, and Microsoft 365 apps
  • User listing, individual user lookup, and user membership lookup

The repository also describes a larger generated tool catalog covering additional Microsoft 365 administration domains. The exact tools exposed to a client can be narrowed with configuration.

How it works

Authentication uses an Azure AD app registration with application permissions and a specific tenant ID. The server obtains access with the client ID, client secret, and tenant ID, then calls Microsoft Graph on behalf of the application. It does not use delegated permissions or the common tenant authority.

The Microsoft 365 Admin MCP server supports stdio as its default transport and Streamable HTTP for remote deployments. It can target the global Microsoft cloud or the China cloud operated by 21Vianet. Tool exposure can be filtered with presets or an enabled-tools regular expression, and result sizes can be constrained through the maximum $top setting.

Read operations are the default operating mode. Write-capable actions are explicitly identified by risk level, and write access can be enabled with the server's command-line option. The available listing marks alert and incident updates as medium risk, attack simulation creation as high risk, and other attack simulation mutations as medium risk.

Setup and configuration

Install the package globally with npm, run the published Docker image, or build it from source with Node.js 18 or later. Before starting, create an Azure AD app registration, grant the required application permissions, and record its client ID, client secret, and tenant ID.

Required environment variables are:

  • MS365_ADMIN_MCP_CLIENT_ID
  • MS365_ADMIN_MCP_CLIENT_SECRET
  • MS365_ADMIN_MCP_TENANT_ID

Optional settings select the cloud, configure Azure Key Vault, cap Graph result sizes, force read-only behavior, or restrict the exposed tools. Key Vault configuration can override the environment-based credentials. Claude Desktop can start the server through a stdio command configuration, and VS Code provides a corresponding MCP configuration with secret prompts. Remote HTTP deployments require an HTTP URL configuration and may use an MCP bridge where native client support is unavailable.

Limitations and notes

The Microsoft 365 Admin MCP server requires application permissions approved for the target tenant. Its access level therefore depends on the permissions granted to the Azure AD app, and exposing write tools increases the operational impact of an agent's actions.

The server is administrative in scope. It should not be selected solely for ordinary user productivity workflows that depend on delegated permissions. A specific tenant ID is mandatory, and credentials should be protected through an appropriate secret-management approach such as Azure Key Vault.

Review the required Graph permissions and enabled tool set before connecting an agent to a production tenant.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Microsoft 365 Admin

Microsoft 365 Admin is an MCP server that connects AI clients to Microsoft Graph through Azure AD application permissions and client credentials. Its main tools retrieve security alerts, incidents, audits, service health, usage reports, users, and memberships, with selected tools supporting controlled administrative changes.

Install it globally from npm with `npm install -g @okapi-ca/ms-365-admin-mcp-server`, or run the published Docker image. You can also clone the repository, install dependencies, generate the sources, and build it with Node.js 18 or later.

It requires an Azure AD app registration with application permissions, a client ID, a client secret, and a specific tenant ID. Set these through `MS365_ADMIN_MCP_CLIENT_ID`, `MS365_ADMIN_MCP_CLIENT_SECRET`, and `MS365_ADMIN_MCP_TENANT_ID`; the server does not use the `common` tenant.

Yes, it is read-only by default. Supported write operations require explicit write enablement, and the server assigns risk classifications to those tools. The listed medium- and high-risk actions include updating alerts or incidents and creating, updating, or deleting attack simulations.

VS Code uses its own `servers` configuration format and can prompt for tenant, client, and secret values; remote HTTP deployments use a URL-based configuration.

Related MCP servers

All in Workplace & Productivity All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMicrosoft 365 Admin AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/microsoft-365-admin?style=directory)](https://allmcps.com/mcp/microsoft-365-admin)
HTML Embed
<a href="https://allmcps.com/mcp/microsoft-365-admin"><img src="https://allmcps.com/api/badge/microsoft-365-admin?style=directory" alt="Microsoft 365 Admin on AllMCPs" /></a>