Microsoft 365 Calendar
Microsoft 365 Calendar is an MCP server published by mindstone, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-20.
Does Microsoft 365 Calendar support the current MCP specification (2026-07-28)?
Not yet confirmed. Microsoft 365 Calendar is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.
Is Microsoft 365 Calendar a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for Microsoft 365 Calendar (as of 2026-08-20).
How do I connect to Microsoft 365 Calendar?
Microsoft 365 Calendar is available via the package npm:@mindstone/mcp-server-microsoft-calendar, the official MCP Registry under io.github.mindstone/mcp-server-microsoft-calendar, the source repository at https://github.com/mindstone/mcp-servers. Authentication: unknown. Transports: stdio.
Does Microsoft 365 Calendar support MCP revision 2025-11-25?
Yes. Microsoft 365 Calendar supports MCP revision 2025-11-25 (checked 2026-08-20).
Does Microsoft 365 Calendar support MCP revision 2026-07-28?
No. Microsoft 365 Calendar was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).
When were Microsoft 365 Calendar's facts last verified?
2026-08-20. Each fact on this page links to the sources used to verify it.
Microsoft 365 Outlook calendar via Graph: list, get, create, update, respond, free/busy.
Which MCP spec revisions does Microsoft 365 Calendar support?
Microsoft 365 Calendar has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2025-11-25 | Supported | Source | |
| MCP 2026-07-28 | Not supported | Source |
How widely adopted is Microsoft 365 Calendar?
Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.
Repository and package signals for Microsoft 365 Calendar
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Stars
- 10
- Forks
- 4
- Last pushed
- (44 days ago)
- Created
- Open issues
- 22
- Primary language
- TypeScript
- Continuous integration
- Present
- Tests
- None detected
- Security policy
- Present
Package (npm) as of
- Latest version
0.2.0- Last published
- First published
- Releases
- 4
- License (package)
- FSL-1.1-MIT
- Maintainers
- 1
- Direct dependencies
- 3
- Unpacked size
- 144 KB
- Registry signature
- Signed
- Build provenance
- Attested
How was this verified, and what are the sources?
Verified · method: sdk-protocol-constant
· confidence 0.85 (Good).
- Official MCP Registry record for io.github.mindstone/mcp-server-microsoft-calendar at version 0.2.0 - lists package npm:@mindstone/mcp-server-microsoft-calendar and repository https://github.com/mindstone/mcp-servers - accessed
- npm registry metadata for @mindstone/mcp-server-microsoft-calendar at published version 0.2.0, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.30.0 - accessed
- Published artifact of @modelcontextprotocol/sdk@1.30.0, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed