Microsoft Cloud PlatformCAUTION
an local MCP server you can run on your env, connecting you to Microsoft Graph, and the complete M365 eco system.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
[](https://mseep.ai/app/aanerud-mcp-microsoft-office)
One MCP server. Multiple users. Real Microsoft 365 traffic on your test tenant.
The Problem
Test tenants sit empty. Static test data does not exercise real workflows. When you need agents that send real emails, schedule real meetings, and collaborate in real Teams channels, mocks and stubs fall short.
What This Solves
This project connects any MCP-compatible AI client to Microsoft 365 through the Graph API. Each agent authenticates as a distinct tenant user and performs real operations against real data.
- 117 tools across 12 modules: Mail, Calendar, Files, Excel, Word, PowerPoint, Teams, Contacts, To-Do, Groups, People, Search
- Multi-user: one server supports your entire team, each with isolated data
- Real Graph API calls: every operation hits the actual tenant, not a mock
- Secure: tokens encrypted at rest, no credentials stored on third-party servers
Architecture
┌──────────────────┐ │ MCP Client │ │ (Claude, etc.) │ └────────┬─────────┘ │ JSON-RPC (stdin/stdout) ┌────────▼─────────┐ │ MCP Adapter │ │ (runs locally) │ └────────┬─────────┘ │ HTTP + Bearer Token ┌────────▼─────────┐ │ MCP Server │ │ (local or │ │ remote) │ └────────┬─────────┘ │ Microsoft Graph API ┌────────▼─────────┐ │ Microsoft 365 │ │ (your tenant) │ └──────────────────┘
Three parts:
173b6605987cOBSERVED · 2026-10-08Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add mcp-web --env CLAUDE_API_KEY=${CLAUDE_API_KEY} --env DEVICE_REGISTRY_ENCRYPTION_KEY=${DEVICE_REGISTRY_ENCRYPTION_KEY} --env JWT_SECRET=${JWT_SECRET} --env MCP_BEARER_TOKEN=${MCP_BEARER_TOKEN} -- npx -y [email protected]{
"mcpServers": {
"mcp-web": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"CLAUDE_API_KEY": "${CLAUDE_API_KEY}",
"DEVICE_REGISTRY_ENCRYPTION_KEY": "${DEVICE_REGISTRY_ENCRYPTION_KEY}",
"JWT_SECRET": "${JWT_SECRET}",
"MCP_BEARER_TOKEN": "${MCP_BEARER_TOKEN}"
}
}
}
}Exposed tools (6)
1 read · 5 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
findPeople | read | Find people by name or email. Use this to get email addresses for scheduling or sending emails. |
initial_schema | write | Create initial database schema |
oauth_device_flow | write | Update devices table with OAuth device flow support |
query | write | Submit a natural language query to Microsoft 365 |
user_logs | write | Create user-specific logging table |
user_sessions | write | Create user sessions table for multi-user Microsoft Graph authentication |
Trust audit
CAUTIONgrade B · trust 81/100 Install with care. The audit found things worth knowing before you trust its output.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | WARN |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (6 observation(s))
- Network
- declared (7 observation(s))
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- found
Findings (11)
'http://127.0.0.1:3000',
'https://127.0.0.1:3000'
TOKEN: 'external-graph-token',
TOKEN: 'external-graph-token',
const ErrorService = require('../../core/error-service.cjs');const MonitoringService = require('../../core/monitoring-service.cjs');const { getConfig } = require('../../config/index.cjs');const templatePath = path.join(__dirname, '../../../dist/mcp-adapter-template.cjs');
const ErrorService = require('../../core/error-service.cjs');@azure/msal-node, @microsoft/microsoft-graph-client, @npmcli/fs, axios, body-parser, cors, docx, dotenv
Gates applied: no_behavioural_pass, no_license.
173b6605987cfull audit observations/trust-audit/mcp-server/aanerud__microsoft-cloud-platform.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-08 | 173b6605987c | CAUTION | B | 81 | first audit |
Questions
What is the Microsoft Cloud Platform MCP server?
an local MCP server you can run on your env, connecting you to Microsoft Graph, and the complete M365 eco system.
What tools does Microsoft Cloud Platform expose?
6 in total: 1 read-only, 5 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is Microsoft Cloud Platform safe to connect to an agent?
With care. The audit graded it B (81/100) and found 11 things worth knowing before you trust this server, listed below with the exact line each was found on.
What credentials does Microsoft Cloud Platform need?
It reads CLAUDE_API_KEY, DEVICE_REGISTRY_ENCRYPTION_KEY, JWT_SECRET, MCP_BEARER_TOKEN, MCP_BEARER_TOKEN_EXPIRY, MCP_ENCRYPTION_KEY, MCP_TOKEN_SECRET, MICROSOFT_CLIENT_SECRET, OPENAI_API_KEY, RATE_LIMIT_AUTH_MAX, SESSION_SECRET and SSL_KEY_PATH from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How current is this page?
The grade is for one exact copy of the source (173b6605987c), read on 2026-10-08. The repository is watched and re-audited when it changes.