Skip to main content
Glama
ap311036

EWS Meeting MCP

by ap311036
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to EWS Meeting MCP

No user-submitted related servers found.

    Related Servers

    • outlook-local-mcp

      amirulmenjeni
      F
      license
      A
      quality
      B
      maintenance
      Enables local automation of classic Outlook for Windows via COM, allowing email search, folder listing, calendar leave block creation, and contact/recipient management without needing cloud APIs or admin approval.
      8
      -

    • MCP Outlook Scheduler

      ChitSingh
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to intelligently schedule meetings by checking Microsoft Outlook calendars, finding available time slots across multiple participants, and automatically booking meetings with Teams integration. Uses Microsoft Graph API with smart fallback logic for optimal scheduling.
      1
      -

    • OWA Exchange MCP Server

      nhype
      A
      license
      A
      quality
      D
      maintenance
      MCP server for any Microsoft Exchange / OWA deployment. Gives LLM agents access to email, calendar, directory search, folders, availability, and meeting analytics via 30 tools.
      30
      25 PyPI
      8
      MIT

    • outlook-classic-mcp-hardened

      wa1939
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to securely interact with the classic Outlook desktop client on Windows via COM, covering mail, calendar, contacts, tasks, categories, and rules. It enforces draft-first outbound email, send gating, and recipient domain allowlisting for restricted environments without Graph, OAuth, or Azure app registration.
      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.8/5.0

    Scored across 17 tools

    Disambiguation5/5

    All tools have clearly distinct purposes, with preview/confirmed pairs clearly differentiated and supporting tools (find, list, resolve, suggest) addressing separate needs. No overlap or ambiguity.

    Naming Consistency5/5

    All tools follow a consistent 'ews_verb_noun' pattern, with clear conventions for preview vs confirmed flows (e.g., ews_create_meeting_preview, ews_create_meeting_confirmed). No naming irregularities.

    Tool Count5/5

    17 tools is well-scoped for a meeting management server, covering setup, inspection, scheduling, creation, update, cancellation, and verification. Each tool serves a distinct and necessary function.

    Completeness5/5

    The tool surface covers the full lifecycle of meeting management from setup and attendee resolution to create/update/cancel with preview/confirmed flows, plus supporting tools like free/busy, room listing, and audit log. No obvious gaps for an organizer-focused server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources