Graph Atlas MCP server
Tracks documented and undocumented Microsoft Graph API schema changes, with an MCP Apps visualiser
1 stars160 downloads/wk
Reviews
Write oneNobody has reviewed Graph Atlas yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Graph Atlas tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it
- Code scansource not scanned: tarball over 25MB25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 1 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Graph Atlas compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 92/100
- higher than 93% of 48,243 servers
- GitHub stars
- 1
- more than 65% of 28,706 servers
- Downloads a week
- 160
- more than 71% of 12,306 servers with a package
Release history: 2 versions in the registry since 2026-08-17, latest 2026-10-22, typically one every 66 days.
Install Graph Atlas in Claude Code, Cursor or VS Code
Runs npx -y graph-atlas-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add graph-atlas-mcp -- npx -y graph-atlas-mcp
What the publisher says
From the Graph Atlas repository's README, as published. We do not edit it. Read it on GitHub
Microsoft Graph Atlas MCP
An MCP server that tracks schema changes across the Microsoft Graph API — both the changes Microsoft documents and the ones it doesn't. Covers the full Entra ID, Entra ID Governance, Identity & Access Management, Entra Agent ID, and Information Protection surface, seeded with a year of history at launch. Ships with an interactive schema visualiser rendered inside the MCP client via MCP Apps.
Why
Microsoft Graph evolves continuously across v1.0 and beta. The official changelog is curated and incomplete — undocumented schema changes (new properties, removed relationships, new enum values) land in production before they're announced. This MCP closes that gap by diffing the actual $metadata CSDL daily, and backfills a year of history from both a public community tracker and the official changelog.
Data sources
Two further tables enrich every change with real-world permission/role context: permissions (1,036 scopes scraped from Merill's Graph Permissions Explorer) and roles (135 Entra built-in roles and their microsoft.directory/ actions, from the Microsoft Learn permissions reference), cross-referenced into rolepermission_map.
Quick start (npx)
Requires Node.js 22+ (uses the built-in node:sqlite). Add to your MCP client — e.g. Claude Desktop's claudedesktopconfig.json:
{
"mcpServers": {
"graph-atlas": {
"command": "npx",
"args": ["-y", "graph-atlas-mcp"]
}
}
}That's the whole setup: on first launch the server auto-downloads the latest published database (change history, permissions, roles, embeddings) from this repo's GitHub Releases into ~/.graph-atlas-mcp/, and keeps it current against the daily release cadence.
Developing from source
git clone https://github.com/darrenjrobinson/graph-atlas-mcp.git
cd graph-atlas-mcp
npm install
npm run buildPopulate the database (first run)
npm run seed # one-off: import changes.entra.ms's ~1,600 historical records
npm run backfill # re-runnable: scrape the official changelog for the 8 IAM families
npm run collect # fetch v1.0 + beta $metadata, establish today's baseline snapshot
npm run collect-permissions # re-runnable, ~9 min: scrape ~1,036 Graph permission pages
npm run collect-roles # re-runnable, ~1 min: scrape 135 Entra built-in roles + actions
npm run build-role-map # re-runnable: cross-reference roles <-> permissions (see limitations)This produces graph-atlas.db in the project root. npm run seed uses a gitignored, one-off local script (scripts/seed-from-entra-ms.js) — it isn't part of the committed repo.
The DB uses WAL journal mode so these collection scripts can run concurrently with an MCP client that already has the file open (e.g. Claude Desktop) without lock contention.
Optional: semantic search
searchchanges runs in hybrid (keyword + semantic) mode automatically if OPENAIAPI_KEY is set, and degrades to keyword-only otherwise:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Graph Atlas: common questions
- Is Graph Atlas MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the Graph Atlas safety report
- How do I install Graph Atlas?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Graph Atlas need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Graph Atlas maintained?
- The last commit was 3 days ago (2026-11-03). The latest release is v0.4.0.
- What can I use instead of Graph Atlas?
- Servers from other publishers that do the same job: Microsoft 365 MCP Server.
- How does Graph Atlas compare with other MCP servers?
- safety score 92/100 (higher than 93% of 48,243 servers); github stars 1 (more than 65% of 28,706 servers); downloads a week 160 (more than 71% of 12,306 servers with a package). Full comparison.
Alternatives to Graph Atlas
Same job from other publishers: the closest match first, then the best rated.
- Microsoft 365 MCP ServerInteract with Microsoft 365 and Office services through the Microsoft Graph API.not reviewedEstablishedB