Skip to main content
Glama
nerdylog-code

m365-mcp-stdio

by nerdylog-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to m365-mcp-stdio

No user-submitted related servers found.

    Related Servers

    • Outlook MCP Server

      Sidd-doshi
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables natural language access to Microsoft 365 data by providing tools for reading and writing emails, calendar events, contacts, tasks, files, Teams meeting recordings and transcripts, and mailbox settings over the Model Context Protocol.
      144 npm
      MIT

    • m365-mcp-server

      SwamiRama
      A
      license
      Not graded
      quality
      C
      maintenance
      A production-ready MCP server that provides secure, delegated access to Microsoft 365 services including Email, SharePoint, OneDrive, and Calendar. It enables AI models to search messages, browse files, manage calendar events, and parse document contents using OAuth 2.1 authentication.
      MIT

    • Foundry Agents MCP Server

      denniszielke
      A
      license
      A
      quality
      D
      maintenance
      Exposes Azure AI Foundry agents, workflows, and AI Search vector-database capabilities as MCP tools, enabling natural language interaction with agents, semantic search, and index management.
      10
      2
      MIT
    Deploy Server
    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

    TDQS

    B3.2/5.0

    Scored across 8 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources