@chrischall/office-outlook-mcp 0.7.1 → 0.8.1

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.7.1"
+    "version": "0.8.1"
   },
   "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.7.1",
+      "version": "0.8.1",
       "author": {
         "name": "Chris Hall"
       },

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "office-outlook-mcp",
   "displayName": "Outlook (Microsoft 365)",
-  "version": "0.7.1",
+  "version": "0.8.1",
   "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

@@ -154,6 +154,17 @@ return only where they are; see [Bulk export](#bulk-export).
 **Diagnostics** — `outlook_healthcheck`
 
 Every read tool takes `view: compact | full | raw`, defaulting to **compact**.
+Three reads also take `view: "brief"` — the one-line-per-item rung mcp-host's
+context groups ask in: `outlook_list_events` and `outlook_list_tasks` gain it
+beside their existing values, and `outlook_list_unread_messages` gains an
+optional `view` whose only value is `brief` (omit it for the triage batch).
+Both additions are optional, so existing calls are unchanged. A brief answer
+is the untrusted envelope described below, with the lines as `data` (one string
+per item, `title — <ISO date | no date> — <status>`, at most 120 chars); it
+fetches no message body or invite and carries no `nextLink`/`next_from`, so
+when Outlook has another page the last line is the note `-- more` (a line
+starting `-- ` is a note, not an item) — call again without `view: "brief"`
+to get the link and follow it.
 Mutating tools **write nothing** until you confirm (bar the cases above)
 — see [Confirmations](#confirmations). The preview shows exactly what would be sent
 (action, method, path and body). (`outlook_create_event` first reads the
@@ -168,7 +179,8 @@ wrap every result (all views) in an untrusted-content
 envelope — `untrusted_content: true` plus a `note` telling the model to treat
 the text as data, never instructions (a `view: raw` record that carries its
 own `untrusted_content`/`note` key is nested under `data`, so it cannot
-overwrite the envelope). `outlook_reply` returns a sent reply's subject — the
+overwrite the envelope). `outlook_list_tasks`'s brief view is wrapped the same
+way. `outlook_reply` returns a sent reply's subject — the
 original sender's text — inside the same envelope.
 On a client that cannot show a confirmation prompt, the confirmToken is still
 something the model passes back itself, so keep `MCP_CONFIRM_MODE=ask-user`