Claude is the UI.

Senserva is deep Microsoft security expertise: identity, devices, compliance, remediation, all the way down. Claude is the interface to all of it.

The dashboards, portals, and PowerShell windows do not go away. They just stop being where you do the work. You do the work in Claude. Claude does the work in your tenant. Senserva keeps both of you honest.

Siemserva also contains Claude and uses it extensively inside the product, under the same Senserva Trustworthy AI principles: grounded tenant data, strong prompts, the rules engine, and a human approval step. Whether Claude is your UI or Claude is quietly doing work behind Siemserva's UI, every call is wrapped in the same guardrails.

Senserva Claude MCP Claude MCP + CLI + Agent

Claude Code taught your editor to build software. Senserva for Claude enables Claude to help manage your M365 and Windows.

Senserva is a deep Microsoft 365 and Entra ID security focused IT automation product creator: identity, devices, applications, privileged access, SharePoint, Exchange, Teams, OneDrive, Intune, patching, remediation. Claude is your interface.

Senserva with Claude Desktop, provides access to all the key information, supplies the prompts and guardrails, and puts a human in the loop at just the right time. That is Senserva Trustworthy AI.

Claude on its own can make mistakes. Senserva Trustworthy AI helps prevent this: grounded tenant data via MCP, validated PowerShell from the rules engine, and a human approval step before any change lands.

Get Senserva Claude MCP See Claude in action
Senserva Trustworthy AI

Four things Senserva Claude MCP does, so Claude can help you run your tenant.

Claude is brilliant at general reasoning. It is not, on its own, a Microsoft 365 and Entra ID expert with access to your live environment. Senserva Claude MCP closes that gap.

01 / TEACH

Teach Claude your Microsoft stack.

600+ checks, MCSB, SCuBA, CIS, ZTA, Graph SDK v2. Senserva's prompt library and rules make Claude fluent across Microsoft 365 and Entra ID, Intune, Exchange, SharePoint, Teams, and OneDrive.

02 / ACCESS

Give Claude the Senserva security context graph.

MCP tools expose the full typed graph: scan findings, identity, patch state, compliance mappings, and remediation catalog. Claude queries what it needs, when it needs it, without guessing.

03 / GUARD

Wrap it in guardrails.

Strong prompts shape the request before Claude ever runs, narrowing scope to the action at hand. Every response then runs through Senserva's rules engine: dangerous recommendations are blocked, not flagged; URLs are verified; finding names are cross-checked against real tenant data. 95%+ accuracy target.

04 / REVIEW

Put a human in the loop at the right time.

Claude proposes, you approve. Remediation plans, report drafts, and destructive actions all pause for your review. Iterate until the answer is something you can hand to an auditor, a board, or a customer.

The parallel

What Claude Code did for developers. What Senserva Claude MCP does for IT and Security.

Claude Code did not replace the compiler, the linter, or the tests. It made them conversational. Senserva Claude MCP does the same for tenant operations.

Claude Code

Conversational software engineering.

Claude reads your repo, runs your tests, edits your files, and explains what it did. Your editor and toolchain become the stage, Claude becomes the actor.

  • Understands the codebase via file access
  • Runs tools: build, test, git, shell
  • Proposes diffs, you review and commit
  • One shared chat, not five IDE panels
Senserva Claude MCP

Conversational Microsoft security and IT.

Claude reads your tenant through Senserva MCP, queries your scan graph, drafts remediation, and explains what it found. Your tenant becomes the stage, Claude becomes the SME.

  • Understands your tenant via Siemserva scan data
  • Runs tools: scan, query, remediate, report, compliance
  • Proposes fixes validated by Trustworthy AI rules
  • One shared chat, not fifteen admin portals
Senserva MCP

How Claude reaches into your tenant: the Senserva MCP server.

Model Context Protocol is the plug. Senserva is the socket. Register once, then ask Claude anything about your Microsoft 365 and Entra ID posture.

One MCP server. Every tool Claude needs to run your tenant.

The Senserva MCP server ships with Siemserva. It exposes your scan data, identity graph, patch state, and remediation catalog as native Claude tools. Claude calls them on demand, reads the results, and reasons about your environment in plain English.

MCP works in Claude Desktop, in Cursor, in any MCP-aware client, and programmatically via the Claude API. We are also shipping a dedicated Senserva Claude MCP CLI, and a managed Agent is next.

# One command. Siemserva installs the Senserva MCP server into Claude Desktop. $ siemserva mcp install

Twenty-plus MCP tools ship with Siemserva: scan the tenant, query findings, traverse the identity graph, generate reports, score compliance, propose validated remediation, check patch status, and more. Every tool lands the moment you run the installer.

Two commands, productive in minutes, your own scan data or our rich simulated database, end to end. Walk through the setup on the Quick Start.

Open the Quick Start
Claude in action

Four conversations. No portals. No PowerShell spelunking.

Pick a scenario. This is what running your tenant through Claude actually looks like.

You
Are we vulnerable to the kind of attack that hit Stryker Corporation?
Claude
query_findings · traverse_graph · compliance_gap
Yes, you have exposure. The Stryker breach used a compromised admin account to mass-wipe devices via Intune. In your environment: Multi-Admin Approval is not enabled for device wipe actions, 2 admin accounts use SMS-based MFA (SIM-swap vulnerable), and both hold permanent Global Administrator assignments without PIM. A single compromised credential could wipe your managed device fleet. I also see no Conditional Access policy requiring compliant devices for admin portal access, so these accounts can authenticate from unmanaged machines.

Three things to fix immediately: enable MAA for destructive Intune actions, convert both admin accounts to FIDO2 MFA, and require PIM activation for Global Admin. Want me to generate the PowerShell?
You
Yes. PowerShell for the MAA change first.
Claude
propose_remediation
Validated against Senserva's rules engine and the current Graph SDK. This enables Multi-Admin Approval for Intune device wipe and delete, with a 2-approver requirement and a 4-hour approval window. Review the diff, I will not apply it without your go-ahead.
You
Who can reach Global Admin through group nesting? And are any of those paths through stale accounts?
Claude
traverse_graph
I traversed the identity graph and found 4 paths to Global Administrator through nested group memberships. Two are direct assignments, expected. The other two reach Global Admin through nesting:

One user account via IT-Admins → Tier-1-Ops → Directory Roles (2 hops).
One service principal via DevOps-Automation → Privileged-Ops → Directory Roles.

The service principal has been inactive for 127 days with an expired credential, but the group membership is still active. If someone re-provisions that credential, they inherit Global Admin. This is the kind of hidden escalation Microsoft's admin portals do not surface because no single dashboard shows the full nesting chain plus credential status.
You
Good catch. Remove the SP from the group and open a ticket to review the user path.
Claude
Removing the SP from DevOps-Automation now. Ticket drafted for the IT-Admins path, routed to the identity team owner. I will pause for your approval before either action goes live.
You
We have a CISA audit coming up. What SCuBA controls are we failing and which ones can we fix this week?
Claude
compliance_gap
You are failing 7 SCuBA controls across AAD and Exchange. The fastest to close:

MS.AAD.1.1v1 (legacy auth blocking): one Conditional Access policy, under an hour.
MS.AAD.3.1v1 (phishing-resistant MFA for privileged roles): 2-hour project to deploy FIDO2 keys to your 4 admin accounts.
MS.EXO.1.1v2 (external forwarding): one-line Exchange transport rule.

Those three close your highest-risk gaps before the auditor arrives. The remaining 4 involve Intune device compliance and SharePoint sharing that need broader coordination. Want me to generate the compliance report, or start with the PowerShell for the first three?
You
Generate the report. Include what we are doing well. The auditor likes positive observations.
Claude
generate_report
Adding positive observations: Security Defaults replaced with targeted CA policies (MS.AAD.2.1v1 pass), DKIM and DMARC configured for all domains (MS.EXO.4.1v1 pass), PIM enabled for 3 of 5 privileged roles. Building now.

Report saved: Reports/Senserva_Compliance_2026-04-21.html
You
Five users still have legacy authentication enabled. Turn it off for all of them.
Claude
propose_remediation · rules-engine · human-approval
Before I change anything: two of those five accounts are service accounts used by your on-premises hybrid sync. Cutting legacy auth on them will break directory sync until you rotate to modern auth, which can take 15 to 45 minutes.

Recommended path: disable legacy auth on the three user accounts now (zero risk), schedule the two service accounts for a maintenance window after their modern-auth credentials are provisioned. I can draft the change-management ticket for the service accounts. Approve?
You
Do it. And show me the diff before it applies.
Claude
diff
3 Conditional Access policy changes drafted. No service account changes applied. Review the diff, approve, and I will push. Senserva Trustworthy AI validated: no blocked patterns, URLs verified against Microsoft Learn, finding IDs match live scan data.

Stop clicking through portals. Start having conversations.

Senserva Claude MCP. Claude for IT and Security Management. Backed by the Senserva MCP, CLI, and soon a managed agent.

Senserva is a Microsoft MISA Member · Patented Technology · Senserva is Endorsed by the Microsoft Entra, Sentinel, and Intune Teams

These credentials belong to Senserva. They do not imply that Microsoft endorses Anthropic or Claude.

From the blog

Reading from the Senserva team.

Latest post

Read the Senserva blog

Microsoft 365 and Entra ID security commentary, research notes, and behind-the-scenes posts from the Senserva team.
Recent

Architecture and check deep-dives

How Siemserva is built, how the graph is modeled, and how Senserva Trustworthy AI turns raw findings into validated answers.
From the team

Research, releases, and customer stories

New posts from the Senserva team. Subscribe on blog.senserva.com or follow along for the latest.
See all posts