Skip to main content
Glama
wteja

exchange-ai-connector

by wteja
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to exchange-ai-connector

No user-submitted related servers found.

    Related Servers

    • msgraph-mcp

      timfurlong
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to access Microsoft Outlook mail and calendar, plus read-only Microsoft Teams message history, acting as the signed-in user via delegated permissions.
      50
      74 PyPI
      1
      MIT

    • outlook-mcp

      XenoXilus
      A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to manage Microsoft Outlook email and calendar through the Microsoft Graph API, including reading, sending, searching emails, and handling calendar events.
      43
      182 npm
      30
      MIT

    • MCP Outlook Server

      FRESHSK
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to interact with Microsoft Outlook via the Microsoft Graph API for managing emails and calendar events. It allows users to read and send emails, list messages, and create calendar appointments with automatic Teams links.
      1
      ISC

    • mcp-outlook-mail

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to interact with Microsoft 365 Outlook Mail, allowing email operations via natural language.
      11 npm
      MIT

    • mcp-outlook-desktop

      Jpatching
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to securely read, search, draft, and send Outlook emails, manage calendar events, and access mailbox folders through a local MAPI connection to Windows Outlook, with human-in-the-loop safeguards.
      9
      1
      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

    A3.5/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct operation within either the calendar or email domain, with no overlapping purposes. check_availability, create_event, list_events, and read_event are clearly separate; similarly for email tools.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern using snake_case (e.g., check_availability, list_emails). No mixing of conventions or ambiguous verbs.

    Tool Count5/5

    With 8 tools covering both email and calendar operations, the count is well-scoped for the connector's purpose. Each tool serves a clear function without superfluous entries.

    Completeness3/5

    The tool surface covers essential read and create operations but lacks update and delete for calendar events, and email deletion or folder management. These are notable gaps for a full lifecycle.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources