Ews Meeting MCP

What ap311036/ews-meeting-mcp MCP server does

The ap311036/ews-meeting-mcp MCP server exposes a structured set of Outlook and calendar operations through Exchange Web Services (EWS). It targets on-premises Exchange deployments rather than Microsoft Graph or a general cloud calendar API.

Agents can search and read inbox messages without marking them as read or changing mailbox state. They can also inspect calendar data, retrieve free/busy information, resolve people, discover rooms, and generate possible meeting times using attendee availability, working-hour rules, excluded windows, and room capacity.

Mail sending is deliberately narrow: ews_send_email_to_self sends a report only to the configured EWS_EMAIL mailbox and requires a stable idempotency key. Meeting writes cover creation, updates, and cancellation, while verification and audit tools provide follow-up checks.

How it works

The ap311036/ews-meeting-mcp MCP server separates planning from changes to Exchange. A scheduling flow can first resolve attendees and rooms, inspect availability, and request slot suggestions. A create, update, or cancel preview then describes the intended operation. The corresponding confirmed tool requires explicit approval and the matching confirmation_id before applying the change.

Setup and operational failures return structured error information, including machine-readable codes and setup guidance. Confirmed actions, duplicate confirmations, in-progress states, previews, and errors can be written to a local JSONL audit log. Meeting state can be checked afterward with ews_verify_meeting.

Setup and configuration

Install the npm package with Node.js 18 or newer and configure an EWS endpoint, mailbox address, username, authentication mode, and timezone as appropriate for the deployment. The README documents NTLM and BASIC authentication; BASIC should only be used when the organization has enabled it and the endpoint uses HTTPS.

Passwords can be supplied through the local ACCOUNT_PASSWORD override, but the project recommends macOS Keychain storage. Keychain access uses a service and account name, with the username used as the default account when no separate account variable is set. The server does not return the EWS password during setup checks.

Optional HTML signatures can be enabled for meeting invitations. The signature path and enablement are controlled through environment variables, and the server provides a setup tool that returns starter HTML.

Tools and capabilities

Supported tool groups include:

• Setup checks, Keychain status, and signature guidance.
• Read-only inbox search and message retrieval.
• Self-only report email with duplicate-send protection.
• Calendar listing, free/busy lookup, and event search.
• Attendee resolution and room discovery through Exchange when available.
• Slot suggestions based on scheduling policy and room constraints.
• Preview and confirmed create, update, and cancel operations.
• Meeting verification and local audit-log retrieval.

The ap311036/ews-meeting-mcp MCP server also includes command-line checks for printing non-secret environment details and probing EWS connectivity.

Limitations and notes

This project requires access to an Exchange EWS endpoint and suitable account credentials; it is not a Microsoft Graph connector. Meeting writes are not direct one-step actions: they depend on a preview, human approval, and a matching confirmation identifier. Update and cancellation require the exact EWS item metadata.

The self-mail capability cannot select an arbitrary recipient. Read-only mailbox tools do not send, move, relabel, or mark messages as read. Local credential and audit-log storage also means deployment teams should review filesystem and Keychain permissions on the host running the MCP process.