Microsoft 365 MCP Connector for Claude.
A managed Microsoft 365 MCP connector for Claude custom connector deployments. We supply a patched image and matching code, keep it aligned with Softeria ms-365-mcp-server upstream, and make the support boundary clear before production use.
Discuss this connectorWhat the customer receives.
The useful part is not only the MCP server. It is the version pin, image, source, update path, OAuth notes, and evidence that it has been tested through Claude.
Pinned Softeria upstream base with Highland Code patch set
Private container image and matching source fork
Claude custom connector OAuth and tool-list verification
Microsoft Entra setup notes for redirect URIs, scopes, and consent
Runbook covering updates, rollback, logs, and support boundaries
Built around enterprise risk, not demo convenience.
Narrow Graph permissions
We start from the smallest useful Microsoft Graph scope set and expand only when the workflow needs it.
Safer defaults
Read-only mode, explicit tool filtering, redirect allowlists, and audit-friendly settings are treated as defaults, not extras.
Upstream tracking
Softeria releases, dependency patches, Claude behaviour changes, and Microsoft Graph changes are reviewed on a defined cadence.
Remote MCP endpoint
Designed for the HTTPS MCP endpoint used by Claude custom connectors, not local-only desktop configuration.
Customer-controlled tenant
The customer keeps Microsoft identity, secrets, consent, and hosting control. We maintain the connector package and update process.
The promise is maintenance, not magic.
We define the supported Claude flow, the upstream update cadence, the security patch process, and what falls outside the connector package before the client depends on it.
Start the supplier conversation