MS365 connector missing from Connectors directory in Cowork

Resolved 💬 2 comments Opened Apr 13, 2026 by pjakonis Closed May 30, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

The Microsoft 365 connector does not appear in the Connectors directory when searching for "Microsoft". Only Microsoft Clarity, Microsoft Learn, Word, and PowerPoint show up.

However, MS365 IS defined as a bundled MCP server inside plugin .mcp.json files (both operations and productivity plugins) pointing to https://microsoft365.mcp.claude.com/mcp. It's just invisible to the user — there's no way to discover, install, or manage it from the Connectors UI.

Other connectors like Gmail, Google Calendar, Slack, Notion, and Atlassian all appear in the directory. MS365 is the only bundled connector that's completely hidden.

Related: #47374 (MS365 auth is also broken, compounding the problem)

What Should Happen?

MS365 should appear in the Connectors directory alongside Gmail, Google Calendar, Slack, and other connectors, so users can discover and install it from the UI.

Error Messages/Logs

Steps to Reproduce

  1. Open Claude Desktop with Cowork enabled
  2. Go to Directory → Connectors
  3. Search "Microsoft" or "MS365" or "Outlook"
  4. Only Microsoft Clarity, Microsoft Learn, Word, and PowerPoint appear
  5. MS365 (email, calendar, OneDrive) is not listed
  6. Meanwhile, check the plugin .mcp.json files — MS365 is defined there as https://microsoft365.mcp.claude.com/mcp but invisible in the UI

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

Latest (Claude Desktop with Cowork, April 2026)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗