m365-mcp-stdio
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MSGRAPH_MAILBOX | No | Test user email or mailbox address used to scope reads for optional live integration. | |
| MSGRAPH_CLIENT_ID | No | Azure client ID for optional live Microsoft 365 integration. | |
| MSGRAPH_TENANT_ID | No | Azure tenant ID for optional live Microsoft 365 integration. | |
| MSGRAPH_CLIENT_SECRET | No | Client secret for optional live Microsoft 365 integration. Do not commit or expose. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| calendar_agendaA | Read a bounded synthetic calendar agenda for the configured identity. |
| mail_list_inboxB | Read synthetic inbox metadata for the configured identity. |
| mail_prepare_draftA | Prepare a local draft preview; this tool never writes or sends mail. |
| teams_channel_historyC | Read bounded history for an operator-registered synthetic channel alias. |
| teams_channel_digestC | Classify only explicit decision, task, plan, status, blocker, and question markers. |
| sharepoint_list_folderB | List synthetic SharePoint metadata for an allowlisted logical folder. |
| sharepoint_read_documentA | Read one bounded synthetic UTF-8 document by logical alias. |
| powerplatform_list_flowsA | List synthetic flow metadata from a pinned development scope. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct Microsoft 365 domain (calendar, mail, teams, sharepoint, powerplatform), so there is little overlap. The only mild ambiguity is between teams_channel_history and teams_channel_digest, but their descriptions clearly separate raw history from classified markers.
Tool names consistently follow a domain_noun_verb pattern (e.g., calendar_agenda, mail_list_inbox, sharepoint_read_document). Minor inconsistency exists between mail_prepare_draft (verb_noun) and teams_channel_digest (noun_noun), but the overall pattern is predictable.
Eight tools is well-scoped for a Microsoft 365 integration covering five product areas. Each tool earns its place by exposing a distinct read-only or draft operation without unnecessary bloat.
The surface covers read and draft operations across several M365 domains, but it is intentionally synthetic and read-only. Obvious gaps like sending mail, updating calendar events, or writing to SharePoint are absent, though the descriptions suggest this is a bounded preview scope rather than a full CRUD API.