TenantMCP

Model Context Protocol for Microsoft 365 admins

The safe bridge between AI assistants and your Microsoft tenant.

Approved, audited, five minutes to set up. Connect Claude, Copilot, or any MCP client to your tenant through one URL. Reads work out of the box - every write goes through a human approval queue with a full audit trail.

Join early access Open the portal

EU-hosted on Azure. A Circle of Bytes ApS product, Denmark.

Add MCP server
Server URLhttps://mcp.tenantmcp.com/mcp
AuthSign in with Microsoft
Approval required retire_device on DEV-4471 is waiting for an admin in the portal.

Live in about five minutes

No agents to host, no scripts to maintain. Grant consent once, paste one URL, and keep control of every change.

  1. 1

    Grant consent, stay read-only

    An admin approves TenantMCP in your tenant. The Microsoft consent screen requests read and write Graph permissions, but write tools stay switched off until an admin turns them on in the portal - nothing can change your tenant until you enable writes, and every write still needs approval.

  2. 2

    Paste one URL

    Add https://mcp.tenantmcp.com/mcp as an MCP server in Claude, Claude Code, Copilot Studio, or any MCP client, and sign in with Microsoft. Your assistant can now answer questions about your tenant.

  3. 3

    Approve write actions

    When the AI proposes a change, it never runs inline. It lands in your approval queue for a human to review and approve or reject. Every decision is recorded in the audit trail.

Modules

Actionable, admin-focused toolsets - not raw API breadth. Intune, Entra, and Purview are live; Licenses is in preview.

Intune

Live

Device inventory, compliance, configuration policies, and apps as concise read tools, plus approval-gated writes: sync, retire, wipe, remote lock, passcode reset, and reboot.

Licenses

Coming soon

Assigned versus available licensing, cost visibility, and gated reclaim and downgrade actions.

Entra

Live

Conditional Access coverage and gaps, privileged role holders, app-credential and stale-app hygiene, guest access, and risky users as read tools.

Purview

Live

Unified audit-log search, admin activity, sign-in risk, eDiscovery cases, and DLP alerts, surfaced read-only for your assistant.

Pricing

Launch pricing during early access. Prices are subject to change.

Free

€0

Read-only, for trying it out.

  • Read-only tools across live modules
  • One URL, connect any MCP client
  • Monthly call cap
  • EU-hosted on Azure
Start free
Early access

Pro

~€29/ admin / month

Write actions with approvals and audit export.

  • Everything in Free
  • Approval-gated write actions
  • Human approval queue with full audit trail
  • Audit export (CSV)
  • Priority on new modules
Join early access

Launch pricing shown per admin, per month, and may change as TenantMCP leaves early access.

FAQ

Can the AI change my tenant without me knowing?

No. TenantMCP is read-only by default. Any write action the AI proposes is never executed inline - it is queued as a pending action for a human admin to approve or reject in the portal, and the decision is recorded in the audit trail.

What permissions do you request?

The Microsoft admin-consent screen requests read and write Microsoft Graph permissions for TenantMCP. Granting it gives TenantMCP the capability, but the write tools stay switched off: no write tool is visible or callable to your assistant until an administrator explicitly enables write actions in the portal, and after that every individual write still has to be approved by a human in the approval queue. Three layers stand between an assistant and a change to your tenant: the admin consent, the portal opt-in, and the per-action approval.

Where is my data hosted, and what do you store?

TenantMCP runs on Azure in EU datacenters. We relay Microsoft 365 data on demand rather than warehousing your tenant contents. What we store is the operational record: approval decisions and audit metadata about who did what and when. We are GDPR-aware and keep those records so you have a defensible trail.

Which AI clients work with TenantMCP?

Any client that speaks the Model Context Protocol. That includes Claude and Claude Code, Copilot Studio, and other MCP-capable assistants. You add one server URL and sign in with Microsoft.

Which module is available first?

Intune, Entra, and Purview are live: device, identity, and compliance read tools plus approval-gated writes (device actions, group membership, and licence reclaim). The Licenses FinOps module is in preview.

How do I get started?

Join early access and we will help you onboard. An admin grants consent, you paste the server URL into your MCP client, and you are answering questions about your tenant in minutes. Your tenant stays read-only until an admin enables write actions in the portal, and even then every write is approved by a human.

Bring your AI assistant to your tenant, safely.

Reads by default. Writes behind a human. A full audit trail either way.

Join early access Already connected? Open the portal