Skip to main content
Glama
access-ctrl

@lnwebworks/outlook-mcp-server

by access-ctrl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to @lnwebworks/outlook-mcp-server

No user-submitted related servers found.

    Related Servers

    • Outlook MCP Server

      SfdcAnnu
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables reading, sending, and managing Microsoft 365/Outlook emails through MCP tools with OAuth 2.1 authentication.
      144 npm
      MIT

    • Outlook Graph MCP

      LPDigitale
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables to manage your Outlook mailbox via Microsoft Graph (write access) with delegated permissions, providing MCP tools to create, modify, and send emails, folders, categories, rules, and automatic replies.
      -

    • outlook-mcp

      Plong-Wasin
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for sending and managing Microsoft Outlook email via the Microsoft Graph API, including drafts, replies, contacts, and directory search.
      144 npm
      MIT

    • outlook-mcp

      hickeroar
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Microsoft Outlook that enables searching, sending, and managing mail and calendar via the OWA REST API using browser-session authentication, with no Azure AD app registration required.
      144 npm
      MIT

    • outlook-mcp

      littlebearapps
      A
      license
      A
      quality
      B
      maintenance
      MCP server for Microsoft Outlook via Graph API. 20 consolidated tools for email, calendar, contacts, folders, rules, categories, and settings with safety controls (dry-run preview, rate limiting, recipient allowlists) and MCP annotations on every tool.
      8
      22
      922 npm
      36
      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.3/5.0

    Scored across 22 tools

    Disambiguation3/5

    There is a cluster of email retrieval tools—get_recent_emails, get_recent_emails_all_folders, get_unread_emails, and get_todays_briefing—that overlap in function and could lead an agent to pick the wrong one by name alone. Most other tools are clearly separated by resource/action, and the descriptions resolve the ambiguity if read carefully.

    Naming Consistency5/5

    All tools use snake_case verb_noun names (get_, create_, update_, cancel_, send_, reply_to_, move_, mark_) with no camelCase or inconsistent style. Even phrase-based names like get_todays_briefing still follow the get_<thing> convention, so the pattern is predictable.

    Tool Count3/5

    22 tools is on the heavy side for a mail/calendar server, and the four overlapping email-fetch variants add redundancy rather than distinct capabilities. A tighter set closer to 15-16 tools would be easier to navigate, though the count is not extreme.

    Completeness4/5

    Email covers fetch, search, triage, drafts, replies, send, move, mark-read, and attachments; calendar covers create/read/update/cancel with conflict checks. The main gaps are no email deletion or forwarding and no direct send for an existing draft, but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources