EWS Meeting MCP
This is an MCP server that lets agents safely read Outlook/Exchange mail and calendar data, send self-only reports, and schedule or modify meetings on on-prem Exchange EWS with human-in-the-loop confirmation.
Check EWS setup, credentials, keychain status, and connectivity without exposing passwords.
Search and read inbox emails read-only without changing mailbox state.
Send a weekly report email only to the configured self address, with idempotency protection.
List calendar events, find events by filters, and get free/busy availability for attendees.
Resolve attendee identities against the Exchange directory.
List and filter meeting rooms, including capacity-aware fallback rooms.
Suggest overlapping free meeting slots using workday, avoid windows, and optional room requirements.
Preview, then confirm creation of meetings with attendees, rooms, location, body, optional recurrence, and show-as status.
Preview, then confirm updates to existing meetings using exact EWS item metadata.
Preview, then confirm cancellation of meetings by moving them to trash.
Verify meeting state on the server and read a local JSONL audit log of lifecycle actions.
Retrieve setup guides and configure an optional HTML signature for meeting invites.
EWS Meeting MCP
The MCP server for safely reading Outlook inbox messages, sending self-only reports, and scheduling meetings on on-prem Exchange EWS.
EWS Meeting MCP gives coding assistants and desktop agents a safe, structured way to read Outlook inbox messages and availability, send a report only to the configured mailbox, discover rooms, suggest meeting slots, and create, update, or cancel meetings only after an explicit human confirmation step.
It is built for companies where calendar access is sensitive infrastructure: regulated teams, internal networks, strict security review, legacy Exchange deployments, and organizations that cannot simply hand a cloud agent broad Microsoft 365 permissions. Credentials stay local, meeting writes are previewed before they touch Exchange, self-only report sends require idempotency protection, and every write can be traced through a local audit trail.
npx ews-meeting-mcpWhy This Exists
Many teams still run calendar infrastructure through on-prem Exchange/EWS. General-purpose agents can reason about scheduling, but they should not receive raw passwords, guess attendee addresses, or send calendar invitations without a reviewable checkpoint.
This is not a generic Outlook wrapper or a Microsoft Graph-first calendar connector. It is designed for the stricter enterprise case: local EWS access, room resources, explicit human approval, duplicate-send protection, and audit-friendly meeting lifecycle tools.
This project wraps Exchange calendar operations in a small MCP surface with:
Room-aware scheduling: finds overlapping attendee availability and filters meeting rooms by Exchange discovery or local policy.
Human-in-the-loop writes: create, update, and cancel operations require a preview plus a matching
confirmation_id.Outlook Show As: create or update personal appointments with
show_as: "out_of_office"(EWSOOF). Empty attendees and rooms never send invitations; this does not configure email automatic replies.Local-first credential handling: reads
.env, shell environment, or macOS Keychain without passing passwords through the model.Structured recovery: setup failures return machine-readable error codes and user-facing setup commands.
Auditability: lifecycle previews, confirmed actions, duplicate confirmations, in-progress states, and structured errors are written to a local JSONL audit log.
Agent-ready instructions: the MCP server exposes tool descriptions and initialization guidance, and the repo includes a companion skill for agents that support skills.
Related MCP server: MCP Outlook Scheduler
What Agents Can Do
Capability | Tooling | Safety posture |
Check setup and credentials |
| Never returns the EWS password |
Set up meeting signatures |
| Returns copyable HTML sample and local env guidance |
Read Outlook inbox |
| Read-only; does not mark messages as read or change mailbox state |
Send a weekly report to self |
| Only sends to |
Read calendar availability |
| Read-only |
Resolve people and rooms |
| Uses Exchange directory when available |
Suggest slots |
| Applies local workday, avoid windows, and room capacity |
Create meetings |
| Supports optional weekly recurrence; requires preview, explicit approval, and matching confirmation id |
Update meetings |
| Requires exact EWS item metadata and matching confirmation id |
Cancel meetings |
| Requires exact EWS item metadata and matching confirmation id |
Verify and audit |
| Confirms server-side state without exposing credentials |
Documentation
Usage Guide: local setup, Keychain, scheduling policy, smoke checks, CLI examples, MCP config, and npm wrapper details.
Agent Guide: tool contracts, setup checks, attendee resolution, room selection, preview-confirm flows, audit log, and verification rules.
Publishing: npm package and GitHub Actions release checklist.
Quick Start
1. Configure EWS
Create a .env file in the working directory or provide equivalent environment variables:
EWS_ENDPOINT=https://mail.company.com/EWS/Exchange.asmx
EWS_EMAIL=your_user@company.com
EWS_USERNAME='DOMAIN\your_user'
EWS_AUTH_TYPE=NTLM
EWS_TIMEZONE=Asia/TaipeiUse EWS_AUTH_TYPE=BASIC only if IT confirms Basic auth is enabled and the endpoint is protected by HTTPS.
2. Store the Password
For local development, the generic ACCOUNT_PASSWORD override works, but do not put it in MCP config:
ACCOUNT_PASSWORD='your-password'On macOS, Keychain is safer than storing the password in .env or MCP client config:
read -rsp "Account password: " ACCOUNT_PASSWORD
echo
security add-generic-password -U -s ews-meeting-mcp-account-password -a 'DOMAIN\your_user' -w "$ACCOUNT_PASSWORD"
unset ACCOUNT_PASSWORDUse the same Keychain service/account pair from any local tool that needs this account password:
ACCOUNT_PASSWORD_KEYCHAIN_SERVICE=ews-meeting-mcp-account-password
ACCOUNT_PASSWORD_KEYCHAIN_ACCOUNT='DOMAIN\your_user'If ACCOUNT_PASSWORD_KEYCHAIN_ACCOUNT is omitted, EWS_USERNAME is used. ACCOUNT_PASSWORD is only a generic local override; Keychain is preferred.
3. Add the MCP Server
For an npm-installed MCP client:
{
"mcpServers": {
"ews-meeting-mcp": {
"command": "npx",
"args": ["-y", "ews-meeting-mcp@0.1.25"],
"env": {
"EWS_ENDPOINT": "https://mail.company.com/EWS/Exchange.asmx",
"EWS_EMAIL": "your_user@company.com",
"EWS_USERNAME": "DOMAIN\\your_user",
"ACCOUNT_PASSWORD_KEYCHAIN_SERVICE": "ews-meeting-mcp-account-password",
"ACCOUNT_PASSWORD_KEYCHAIN_ACCOUNT": "DOMAIN\\your_user",
"EWS_AUTH_TYPE": "NTLM",
"EWS_TIMEZONE": "Asia/Taipei"
}
}
}
}For a local checkout:
{
"mcpServers": {
"ews-meeting-mcp": {
"command": "/path/to/ews-meeting-mcp/.venv/bin/python",
"args": ["-m", "ews_meeting_mcp.mcp_server"],
"cwd": "/path/to/ews-meeting-mcp",
"env": {
"PYTHONPATH": "src"
}
}
}
}Optional: Add an Outlook-Style Signature
Meeting invites append a configured HTML signature by default. Ask the MCP tool for a copyable starter template:
ews_signature_setup_guideSave the returned sample_html as ews-meeting-signature.html in the MCP working directory, then edit the name, email, title, logo URL, and disclaimer. You can also point to a different file:
EWS_MEETING_SIGNATURE_HTML_PATH=/path/to/ews-meeting-signature.html
EWS_MEETING_SIGNATURE_ENABLED=trueUse an HTTPS logo URL recipients can access, or replace the <img> source with a base64 data URI. Set EWS_MEETING_SIGNATURE_ENABLED=false to temporarily stop appending the signature.
4. Verify Setup
npx ews-meeting-mcp --cli env
npx ews-meeting-mcp --cli probeThe first command prints the configured endpoint and account without printing the password. The second command validates that the account can connect to EWS.
Agent Workflow
For incoming Outlook mail, search the configured inbox first and then read the selected message:
user asks about company email
-> ews_setup_check
-> ews_search_emails with the narrowest known filters
-> user selects or identifies one message
-> ews_read_email with the exact id and optional changekeyThese mailbox tools are read-only. They do not mark messages as read, send mail, move messages, or change labels.
For the Thursday Jira weekly-report automation, compose the report from the Jira results and then call the dedicated self-only mail tool through this EWS MCP:
weekly report is ready
-> ews_setup_check
-> ews_send_email_to_self with subject, body, and a stable idempotency_key
-> stop after sent=true; do not use Gmail, to: me, or another mail providerews_send_email_to_self takes no recipient, to, cc, or bcc argument. It obtains the only recipient from EWS_EMAIL, sends through Exchange EWS, and appends the configured HTML signature by default. It does not write the email body or recipient address to the audit log. Reuse the same idempotency key for an automation retry; a completed or in-progress key will not call Exchange again.
Scheduling should follow this shape:
user request
-> ews_setup_check
-> ews_signature_setup_guide, if the user needs help creating the optional HTML signature
-> ews_resolve_attendees, if names or aliases are provided
-> ews_list_rooms, if a room may be needed
-> ews_suggest_slots
-> user chooses a slot and room
-> ews_create_meeting_preview
-> show exact invite details, recurrence if present, and confirmation_id
-> user explicitly confirms
-> ews_create_meeting_confirmed with confirm=true and the same confirmation_id
-> ews_verify_meeting, when item id and changekey are availableRecurring meetings are created by passing a structured recurrence object to both preview and confirmed create calls. For example, "every Monday and Wednesday" uses weekly recurrence:
{
"type": "weekly",
"interval": 1,
"weekdays": ["MO", "WE"],
"range": {
"type": "numbered",
"count": 10
}
}"Every business day until 7/26" means Monday through Friday, without holiday or makeup-day handling:
{
"type": "weekly",
"interval": 1,
"weekdays": ["MO", "TU", "WE", "TH", "FR"],
"range": {
"type": "end_date",
"end_date": "2026-07-26"
}
}If the user asks only for weekdays such as "every Monday and Wednesday" without an end date, occurrence count, or explicit no-end choice, ask for one before previewing.
Existing meeting changes should use exact calendar metadata:
user asks to update or cancel a meeting
-> ews_find_calendar_events with the narrowest known time window
-> user chooses one exact event, if more than one candidate exists
-> ews_update_meeting_preview or ews_cancel_meeting_preview
-> show current/proposed details, warnings, and confirmation_id
-> user explicitly confirms
-> matching confirmed tool with confirm=true and the same confirmation_idAgents should never infer an event from subject text when multiple candidates are possible.
Safety Model
EWS Meeting MCP is designed around a simple rule: reads may be automated, and every write must have a narrow safety gate. Inbox reads are limited to explicit read-only search and read tools; meeting writes require preview plus explicit confirmation, while the self-only report send requires configured-self enforcement plus idempotency protection.
Authentication failures are fail-fast: the EWS client uses
FailFast, and after one invalid-credential or locked-account response the MCP blocks all later EWS calls in that process. Fix the shared Keychain item and restart the MCP before trying again.Confirmed create, update, and cancel tools refuse to run unless
confirm=trueis passed.Confirmed tools require the exact
confirmation_idreturned by the matching preview.Confirmed update and cancel tools also require the exact EWS
idandchangekeyfromews_find_calendar_eventsor a prior verified result.Duplicate confirmed requests return
error_code: "duplicate_confirmation"with prior result metadata instead of calling EWS again.In-progress confirmations return
error_code: "confirmation_in_progress"and should not be blindly retried.Preview tools never save, move, delete, or send Exchange notifications.
ews_send_email_to_selfis the only mail-write capability. It is self-only, requiresEWS_EMAILto be configured, and sends a saved draft with EWSCreateItemfollowed bySendItem; it does not accept an arbitrary recipient.Self-only sends require a stable, non-secret
idempotency_key. A duplicate or in-progress key is refused before another EWS send. If delivery is uncertain, inspect Sent Items before retrying.Self-only send audit entries contain only action/status and non-sensitive delivery/idempotency metadata; they do not contain the configured email address, subject, body, password, or token.
The local confirmation ledger and audit log store operation metadata, not EWS passwords.
If ews_setup_check returns ready: false, an agent should show the returned user_message or setup_command verbatim and stop. It should not ask for attendee emails or continue scheduling as a workaround.
Scheduling Policy
By default, scheduling tools look for ews-meeting-policy.json in the current working directory. Set EWS_MEETING_POLICY_FILE to point at a different file.
If no policy file exists, built-in defaults are used:
workday:
10:00to18:00avoid:
12:00-14:00fallback rooms:
2-11,2-13,2-14,3-1,3-2,3-4
Live room selection uses Exchange room-list discovery when available, then falls back to configured rooms.
Example policy:
{
"workday_start": "10:00",
"workday_end": "18:00",
"avoid": ["12:00-14:00"],
"rooms": [
{
"alias": "3-1",
"name": "3-1 Meeting Room(12P)",
"email": "3-1MeetingRoom@company.com",
"capacity": 12
}
]
}Policy rooms are merged with the default fallback rooms by alias. A matching alias overrides the default room, and new aliases are appended.
CLI Usage
The npm wrapper starts the MCP server by default:
npx ews-meeting-mcpPass --cli to run the Python CLI through the same package:
npx ews-meeting-mcp --cli env
npx ews-meeting-mcp --cli calendar --days 7Suggest a 30-minute meeting slot:
npx ews-meeting-mcp --cli suggest \
--attendee alice@company.com \
--attendee bob@company.com \
--start 2026-06-15T09:00:00+08:00 \
--end 2026-06-19T18:00:00+08:00 \
--duration-minutes 30 \
--limit 5Preview a meeting invitation without sending anything:
npx ews-meeting-mcp --cli create-meeting \
--attendee alice@company.com \
--attendee bob@company.com \
--start 2026-06-15T11:00:00+08:00 \
--end 2026-06-15T11:30:00+08:00 \
--subject "Project sync" \
--body "Discuss next steps" \
--location "Webex"Actually create the meeting and send invitations:
npx ews-meeting-mcp --cli create-meeting \
--attendee alice@company.com \
--attendee bob@company.com \
--start 2026-06-15T11:00:00+08:00 \
--end 2026-06-15T11:30:00+08:00 \
--subject "Project sync" \
--body "Discuss next steps" \
--location "Webex" \
--confirmThe --confirm flag is intentionally required. Without it, the command prints a dry-run preview and does not call EWS to create the event.
Calendar Show As / 不在辦公室
The create and update preview/confirmed MCP tools accept optional show_as:
| EWS |
|
|
|
|
|
|
|
|
Omitting it during creation keeps the existing Busy default; omitting it during updates preserves the stored status. Personal appointments use attendees: [] and rooms: [], and are saved with SendToNone. Existing meetings with attendees or resources retain their invitation behavior. Weekly recurring creation also accepts show_as; recurrence editing capabilities are unchanged.
Call ews_create_meeting_preview with, for example:
{
"subject": "不在辦公室",
"attendees": [],
"rooms": [],
"start": "2026-09-21T09:00:00+08:00",
"end": "2026-09-21T18:00:00+08:00",
"show_as": "out_of_office",
"include_signature": false
}Show the user the start/end, timezone offsets, show_as, and invitation behavior. After explicit confirmation, call ews_create_meeting_confirmed with the same arguments plus confirm: true and the returned confirmation_id. Changing the status after preview invalidates that confirmation. Query/verification tools return the stored show_as and raw legacy_free_busy_status; use ews_verify_meeting to read the server after saving.
See Calendar status usage, MCP update steps, and live verification for update examples and a manual verification checklist. This feature affects the calendar status only, not mail automatic replies.
Local Development
For detailed setup, smoke tests, CLI examples, and MCP client configuration, see the Usage Guide.
The short development loop is:
python3 -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
cp .env.example .env
npm testRun the MCP server from a checkout:
env PYTHONPATH=src python -m ews_meeting_mcp.mcp_serverCompanion Skill
The repo includes a companion skill for agents that support skills:
skills/ews-meeting-mcp/SKILL.mdSee the Agent Guide for the same workflow in plain Markdown.
Troubleshooting
Operational troubleshooting lives in the Usage Guide. For agent behavior, setup-check handling, and lifecycle safety, see the Agent Guide.
Release
See Publishing.
License
MIT
Available Tools
17 toolsews_cancel_meeting_confirmedA
Cancel an existing non-recurring organizer meeting by moving it to trash. Requires confirm=true and the confirmation_id returned by ews_cancel_meeting_preview.
Inputs: id (required), changekey (required), confirmation_id (required), confirm (required), +1 more.
ews_cancel_meeting_previewA
Preview cancellation of an existing meeting using exact id and changekey. Does not delete, move, or send cancellations.
Inputs: id (required), changekey (required), send_meeting_cancellations.
ews_create_meeting_confirmedA
Create a meeting and send invitations. Only call after the user explicitly confirms the exact attendees, time, subject, body, and location. Requires confirm=true and the confirmation_id returned by ews_create_meeting_preview.
Inputs: subject (required), attendees (required), start (required), end (required), +6 more.
ews_create_meeting_previewB
Preview a meeting invite without creating the event or sending invitations.
Inputs: subject (required), attendees (required), start (required), end (required), +4 more.
ews_find_calendar_eventsA
Read-only search for calendar events in a time window. Returns exact EWS id and changekey metadata for safe preview-confirm update or cancel flows.
Inputs: start (required), end (required), subject_contains, location_contains, +3 more.
ews_get_audit_logA
Read recent local lifecycle audit entries for meeting preview, confirmed, duplicate, in-progress, and error actions. Does not read EWS credentials or call Exchange.
Inputs: limit, action, status.
ews_get_free_busyA
Read free/busy blocks for one or more attendee email addresses.
Inputs: attendees (required), start (required), end (required).
ews_keychain_statusA
Check whether EWS password credentials are available from environment variables or macOS Keychain without revealing the password. If missing, returns required_action and setup_command that must be shown verbatim to the user.
Inputs: no named parameters.
ews_list_calendarC
List upcoming events from the configured user's default calendar.
Inputs: days.
ews_list_roomsB
List Exchange meeting rooms from dynamic room lists, or configured static fallback rooms, as structured options for user selection.
Inputs: attendee_count, query, room_list, source, +1 more.
ews_probeA
Check that the configured EWS account can connect. Does not read calendar items.
Inputs: no named parameters.
ews_resolve_attendeesA
Resolve attendee names, aliases, or email addresses against the company Exchange directory before scheduling. If multiple matches are returned, ask the user which email to use.
Inputs: attendees (required), limit.
ews_setup_checkA
Return whether EWS setup is ready, including env and password/Keychain checks. When ready is false, show user_message or setup_command and stop before scheduling.
Inputs: no named parameters.
ews_suggest_slotsA
Suggest nearest overlapping free meeting slots for multiple attendees and optional candidate meeting rooms. Omits workday_start, workday_end, and avoid to use local policy defaults.
Inputs: attendees (required), start (required), end (required), rooms, +6 more.
ews_update_meeting_confirmedA
Update an existing meeting. Requires confirm=true and the confirmation_id returned by ews_update_meeting_preview. Supports only subject, start, end, location, and body.
Inputs: id (required), changekey (required), confirmation_id (required), confirm (required), +7 more.
ews_update_meeting_previewA
Preview changes to an existing meeting using exact id and changekey. Does not save or send meeting updates.
Inputs: id (required), changekey (required), subject, start, +5 more.
ews_verify_meetingA
Verify a calendar item by EWS id and optional changekey. Returns normalized organizer item status, attendees, rooms/resources, and response_status values when Exchange exposes them.
Inputs: id (required), changekey.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 17 tools
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.
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.
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.
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.
Related MCP Connectors
Merged free/busy, find mutual time, propose bookings with human approval. Never event contents.
Book meetings on each user's own calendar from inside your app. Also email and Slack posts; undo.
Read and change Google Calendar and Outlook events, find free time and add meeting links.
Check availability, book meetings and find group times — without sharing your calendar.
Related MCP Servers
- AlicenseAqualityDmaintenanceAllows scheduling meetings in Microsoft Outlook using Microsoft Graph API, with features for creating calendar events and adding attendees by finding their email addresses.816ISC
- AlicenseNot gradedqualityDmaintenanceEnables 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.1MIT
- FlicenseAqualityDmaintenanceEnables 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-
- AlicenseNot gradedqualityCmaintenanceEnables OAuth2-authenticated clients to search and read on-premises Exchange mail, download attachments, manage drafts and confirmed sending, update read flags, move messages, look up directory entries, and access personal calendar events through EWS, with LiteLLM integration.MIT