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.

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 read-only consent

    An admin approves TenantMCP in your tenant with read-only Microsoft Graph permissions to start. Write permissions are a separate, later consent - nothing can change your tenant until you ask for it.

  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 is live now. More modules are on the way.

Intune

Live

Device inventory, compliance, configuration policies, and apps as concise read tools, plus approval-gated writes like device sync and retire.

Licenses

Coming soon

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

Entra

Coming soon

Users, groups, and Conditional Access reads with carefully gated group membership writes.

Purview

Coming soon

Compliance and audit signal, surfaced for your assistant in read-first form.

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

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?

Your first admin consent grants read-only Microsoft Graph permissions. Write permissions are a separate, incremental consent that you grant only when you decide to enable gated write actions. You are always one step ahead of what the tool can do.

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 is live, with device, compliance, policy, and app read tools plus approval-gated writes. Licenses, Entra, and Purview modules are on the roadmap.

How do I get started?

Join early access and we will help you onboard. An admin grants read-only consent, you paste the server URL into your MCP client, and you are answering questions about your tenant in minutes. Enabling writes is an extra consent step whenever you are ready.

Bring your AI assistant to your tenant, safely.

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