ews-meeting-mcp

EWS Meeting Agent

Use the ews-meeting-mcp MCP tools to read company Outlook mail, send self-only Jira reports, and schedule meetings through an on-prem Exchange/EWS calendar.

Workflow

1. For company Outlook mail, call ews_setup_check, then ews_search_emails with the narrowest known filters. Present the returned metadata, use the exact selected id and optional changekey with ews_read_email, and summarize the returned message. These tools are read-only: they do not mark messages as read, move messages, delete messages, or change labels.
2. At the start of a scheduling session, call ews_setup_check. If it returns ready: false, show its user_message as-is, or show setup_command verbatim in a fenced bash block, and stop. Do not ask the user to paste a password into chat or MCP config; do not ask for attendee emails or continue with EWS tools until the user says they fixed setup. Then call ews_setup_check again before continuing. If the user asks how to set up an Outlook-style meeting signature, call ews_signature_setup_guide and show the returned sample_html, recommended_path, and setup_command; this helper does not require EWS credentials.
3. For the Thursday Jira weekly-report automation, after it assembles the previous and current report, call ews_send_email_to_self with subject, body, body_format, and a stable, non-secret idempotency_key. It has no recipient, to, cc, or bcc argument; it sends only to the configured EWS_EMAIL through EWS CreateItem followed by SendItem. Never substitute Gmail or to: me. Reuse the same idempotency key for retries; treat duplicate_confirmation, confirmation_in_progress, and unknown delivery as stop conditions until Sent Items and the audit log are inspected.
4. Parse the user's request into attendees, candidate rooms, date range, duration, subject, body, and location. For Taiwan/local office scheduling, pass datetime arguments with an explicit local offset such as +08:00. Z is accepted by the tool but means UTC, not local time.
5. If any attendee is not a complete email address, call ews_resolve_attendees first. Do not ask the user to provide full attendee email addresses before trying company directory resolution.
6. Use exactly resolved emails for scheduling. If a name has zero matches or multiple matches, ask the user to clarify or choose from the returned candidates before continuing. Prefer the host's interactive multiple-choice UI or clickable choice controls when available; otherwise show a short numbered list of candidates. For ambiguous matches, show candidate names and emails as choices; do not ask the user to type the full email manually.
7. If the user did not mention rooms, call ews_list_rooms with the attendee count if known, then ask whether a meeting room is needed using the returned options. Prefer the host's interactive multiple-choice UI or clickable choice controls when available; include "no meeting room" and "auto-pick any room with enough capacity" choices. The default source: "auto" tries Exchange room-list discovery and falls back to configured policy rooms; offer the user a choice among the returned room values or "no specific room"; do not rely on a hand-written room list.
8. If the user wants a room but does not choose a specific room, call ews_suggest_slots with require_room: true and no rooms; the tool uses dynamic Exchange rooms when available, then falls back to configured rooms, and filters rooms with known capacity below the attendee count. P means persons.
9. If the user chooses specific rooms, pass the selected room values or emails in rooms when calling ews_suggest_slots.
10. Show suggested slots with their available_rooms. When asking the user to pick a slot or room, prefer the host's interactive multiple-choice UI or clickable choice controls when available; otherwise show a short numbered list. Omit workday_start, workday_end, and avoid to use local policy defaults.
11. When the user picks a slot and room, call ews_create_meeting_preview with the selected room in rooms.
12. For recurring meeting requests, pass a structured recurrence object to preview and confirmed create calls. Weekly Monday/Wednesday uses {"type":"weekly","interval":1,"weekdays":["MO","WE"],"range":{"type":"numbered","count":10}}. Every business day until 2026-07-26 uses {"type":"weekly","interval":1,"weekdays":["MO","TU","WE","TH","FR"],"range":{"type":"end_date","end_date":"2026-07-26"}}. Business days mean Monday through Friday only. If the user gives weekdays but no end date, occurrence count, or explicit no-end choice, ask for one before previewing.
13. Show the exact preview: attendees, rooms, start, end, subject, body, location, signature status, recurrence if present, and confirmation_id.
14. Only after the user explicitly confirms, call ews_create_meeting_confirmed with confirm: true and the exact confirmation_id returned by preview.
15. After a successful confirmed create, call ews_verify_meeting with the returned item id and changekey when available, then report the organizer item status and room response_status. Treat unknown room response as pending/unknown, not as failure.