Skip to main content
Glama
desek

outlook-local-mcp

by desek
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

Related Servers

Alternatives to outlook-local-mcp

No user-submitted related servers found.

    Related Servers

    • olk

      rlrghb
      A
      license
      Not graded
      quality
      A
      maintenance
      A CLI and MCP server for Microsoft Outlook and OneDrive via the Microsoft Graph API, enabling AI agents to manage email, calendar, contacts, tasks, and files through the Model Context Protocol.
      19
      MIT

    • Outlook MCP

      lanSall
      A
      license
      A
      quality
      C
      maintenance
      A local stdio MCP server that enables reading, sending, and searching emails, as well as listing calendar events via Microsoft Graph API, using device-code authentication.
      10
      170 npm
      MIT

    • outlook-mcp

      ajs117
      F
      license
      Not graded
      quality
      B
      maintenance
      Local MCP server for personal Outlook.com/Hotmail/Live accounts, enabling email triage, folder management, bulk operations, and newsletter unsubscribe via Microsoft Graph.
      -

    • google-mcp

      giantrotta24
      A
      license
      B
      quality
      C
      maintenance
      Multi-account Google MCP server providing read access to Gmail and Calendar via stdio. Supports secure authentication for personal and work accounts with OAuth and keychain token storage.
      4
      MIT

    • outlook-mcp-server

      dhtim135
      F
      license
      A
      quality
      D
      maintenance
      A lightweight MCP server for personal Microsoft Outlook/Hotmail accounts, enabling email search, reading, attachment management, and folder operations via Microsoft Graph API with OAuth device-code flow.
      6
      1
      -
    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

    A4.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    The four tools (account, calendar, mail, system) each cover a distinct domain with no overlap in their primary responsibilities. The sub-operations within each tool are also clearly separated, making it easy for an agent to select the right tool.

    Naming Consistency5/5

    All tool names are single lowercase nouns (account, calendar, mail, system), following a consistent and predictable pattern. The sub-operations use a verb_noun convention, but the tool-level naming is uniform.

    Tool Count5/5

    With only 4 tools, each serving a major functional area (account, calendar, mail, system), the count is well-scoped and appropriate. The sub-operation design keeps the top-level surface compact while still covering a broad domain.

    Completeness3/5

    The calendar and account tools provide comprehensive lifecycle coverage, but the mail tool in its current configuration only exposes read operations (list, get, search) and lacks essential write capabilities such as sending, replying, or managing drafts. This is a significant gap for a mail-oriented server.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources