Skip to main content
Glama

M365 Graph MCP

by work.mcps
OverviewDiscussionsAdmin

Server Details

Manage Microsoft 365 email, calendar, contacts and inbox rules via the Graph API with OAuth 2.0.

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP
URL

TDQS

B3.4/5.0

Scored across 34 tools

Disambiguation5/5

All M365 tools target distinct entities (contacts, events, messages, folders, rules, settings) with clear verb-noun pairs. The four SAP tools are a separate domain, creating no confusion with the M365 tools.

Naming Consistency4/5

The majority of tools follow a consistent 'm365_verb_noun' pattern. However, four SAP tools (sap_get_*) deviate from this prefix, and the verb 'discover' is used instead of 'list' or 'search', slightly breaking uniformity.

Tool Count2/5

With 34 tools, the server exceeds the 25+ threshold for 'too many'. While the scope is broad (mail, calendar, contacts, rules, settings, plus SAP), the count feels heavy and could be streamlined or split into separate servers.

Completeness4/5

The M365 Graph tools provide comprehensive CRUD coverage for mail, calendar, contacts, rules, and folders, plus specialized operations like free/busy, auto-reply, and mailbox discovery. The SAP tools are read-only and seem out of place, but for the M365 domain the surface is well-covered.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 34 tool updates
    • First observedm365_create_contact
    • First observedm365_create_draft
    • First observedm365_create_event
    • First observedm365_create_mail_folder
    • First observedm365_create_rule
    • First observedm365_delete_contact
    • First observedm365_delete_event
    • First observedm365_delete_mail_folder
    • First observedm365_delete_message
    • First observedm365_delete_rule
    • First observedm365_discover_mailboxes
    • First observedm365_get_contact
    • First observedm365_get_event
    • First observedm365_get_free_busy
    • First observedm365_get_mailbox_settings
    • First observedm365_get_message
    • First observedm365_get_rule
    • First observedm365_list_contacts
    • First observedm365_list_events
    • First observedm365_list_mail_folders
    • First observedm365_list_messages
    • First observedm365_list_rules
    • First observedm365_move_message
    • First observedm365_rename_mail_folder
    • First observedm365_reply_message
    • First observedm365_send_mail
    • First observedm365_set_auto_reply
    • First observedm365_update_contact
    • First observedm365_update_event
    • First observedm365_update_rule
    • First observedsap_get_business_partners
    • First observedsap_get_items
    • First observedsap_get_sales_orders
    • First observedsap_query_entity

Related MCP Connectors

Related MCP Servers

Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources