@chrischall/office-outlook-mcp 0.11.0 → 0.12.0

package/.claude-plugin/marketplace.json

@@ -7,7 +7,7 @@
   },
   "metadata": {
     "description": "MCP server for Outlook / Microsoft 365 — mail, calendar, contacts and tasks via natural language",
-    "version": "0.11.0"
+    "version": "0.12.0"
   },
   "plugins": [
     {
@@ -15,7 +15,7 @@
       "displayName": "Outlook (Microsoft 365)",
       "source": "./",
       "description": "MCP server for Outlook / Microsoft 365 — triage unread mail, reply, answer meeting invites and schedule meetings, plus folders, calendar, contacts and tasks, with confirmation before anything is sent",
-      "version": "0.11.0",
+      "version": "0.12.0",
       "author": {
         "name": "Chris Hall"
       },

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "office-outlook-mcp",
   "displayName": "Outlook (Microsoft 365)",
-  "version": "0.11.0",
+  "version": "0.12.0",
   "description": "Outlook / Microsoft 365 for Claude — triage unread mail, reply, answer meeting invites and schedule meetings, plus folders, calendar, contacts and tasks, with confirmation before anything is sent, using your signed-in browser session",
   "author": {
     "name": "Chris Hall",

package/README.md

@@ -272,7 +272,10 @@ An agent can work through new mail end to end without opening Outlook:
      id, so an answered invite is already filed — skip steps 3 and 4 for it
      (its old id would 404);
    - a message that needs an answer: `outlook_reply` (`reply`, `replyAll` or
-     `forward`), or `draftOnly: true` to leave it in Drafts for you to review;
+     `forward`), or `draftOnly: true` to leave it in Drafts for you to review.
+     `cc` / `bcc` add people in the same call — on `replyAll` the thread's
+     existing Cc is kept, not replaced. To change an existing draft's Cc
+     without retyping it, use `outlook_update_draft` with `addCc` / `removeCc`;
    - a request for a meeting: `outlook_find_meeting_times` for the attendees,
      then pass the chosen slot's `createEventArgs` to `outlook_create_event`;
    - an attachment to read: `outlook_get_attachment`.
@@ -332,7 +335,8 @@ are, their sizes, the record and attachment counts, the date span, and
   your response, show-as, categories, the join link and the full plain-text
   body.
   `format: "markdown"` writes `part-0001.md`, a readable transcript (one
-  section per message or event), instead.
+  section per message or event), instead; its bodies are read as HTML and
+  converted to Markdown, so lists, tables, emphasis and links survive.
   `manifest.json` lists the counts and any errors, and the files: on disk
   every part's files (it is rewritten as each part finishes); in a blob zip
   the files in that zip.
@@ -389,7 +393,19 @@ a fresh preview.
 - Fields are **PascalCase** (`ReceivedDateTime`, `IsRead`). This is the Outlook
   REST API, not Graph — a Graph snippet silently returns nothing.
 - `outlook_get_message` returns a **plain-text** body by default, measured 9.4×
-  smaller than the HTML; pass `html: true` for the original.
+  smaller than the HTML. `format: "markdown"` keeps the structure (lists,
+  tables, emphasis, links with their text) at about the same size — on a live
+  Jira notification, 5.2 KB of Markdown against 5.9 KB of plain text and
+  14.5 KB of HTML — and `format: "html"` returns sanitised HTML. Both drop
+  text the sender hid (`display:none` preheaders and the like). `html: true`
+  still returns the HTML exactly as Outlook stores it, and `view: "raw"` is
+  Outlook's untouched record. `outlook_list_unread_messages`
+  takes `bodyFormat: "markdown"` too.
+- Writing, pass `format: "markdown"` to `outlook_send_message`,
+  `outlook_create_draft`, `outlook_update_draft` or `outlook_reply`: the text
+  is sent as formatted HTML (bold, lists, links, headings, quotes, code), and
+  is cheaper for an agent to write than HTML. Raw HTML in it is escaped. A
+  formatted reply is drafted, filled in and sent in the same one call.
 - `outlook_list_events` uses the calendar *view*, which expands recurring
   series. `/me/events` does not, which is why it is not exposed as-is.
 - Time zones are **Windows** names (`Eastern Standard Time`), not IANA.