@chrischall/office-outlook-mcp 0.3.1 → 0.3.3

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.3.1"
+    "version": "0.3.3"
   },
   "plugins": [
     {
@@ -15,7 +15,7 @@
       "displayName": "Outlook (Microsoft 365)",
       "source": "./",
       "description": "MCP server for Outlook / Microsoft 365 — read mail, folders, calendar, contacts and tasks, and send mail with confirmation",
-      "version": "0.3.1",
+      "version": "0.3.3",
       "author": {
         "name": "Chris Hall"
       },

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "office-outlook-mcp",
   "displayName": "Outlook (Microsoft 365)",
-  "version": "0.3.1",
+  "version": "0.3.3",
   "description": "Outlook / Microsoft 365 for Claude — read mail, folders, calendar, contacts and tasks, and send mail with confirmation, using your signed-in browser session",
   "author": {
     "name": "Chris Hall",

package/README.md

@@ -27,15 +27,32 @@ does not re-capture.
 npm i -g @chrischall/office-outlook-mcp
 ```
 
-Requires the **Transporter** Chrome extension and `@fetchproxy/cli`, on a
-matching major version:
+Requires the **ContextMint Bridge** browser extension, installed from
+[its releases](https://github.com/nullnet-app/contextmint-bridge/releases):
+in Chrome, unzip the chrome build and load it unpacked
+(`chrome://extensions` → Developer mode → Load unpacked). Safari is not
+available yet — it will ship inside the ContextMint app, which has no public
+download — so use Chrome for now.
+
+ContextMint Bridge is the fetchproxy browser extension under its new name, from
+the same maintainer — fetchproxy's own README
+([#extension](https://github.com/chrischall/fetchproxy#extension)) points to it.
+Its source is public at
+[nullnet-app/contextmint-bridge](https://github.com/nullnet-app/contextmint-bridge):
+build it yourself, or check a release zip against the `.sha256` file published
+beside it (`shasum -a 256 -c contextmint-bridge-chrome-<version>.zip.sha256`).
+
+The extension, `fpx` and this server are compatible by **fetchproxy protocol
+number** (currently protocol 4), not by matching package versions. Keep the
+bridge and `fpx` current — a mismatch fails with an error naming both protocol
+numbers. Also install `@fetchproxy/cli`:
 
 ```sh
 npm i -g @fetchproxy/cli
 ```
 
-The first capture prints a 6-digit pair code to approve in the Transporter
-popup; the grant persists.
+The first capture prints a 6-digit pair code to approve in the ContextMint
+Bridge popup; the grant persists.
 
 ### Install in opencode
 
@@ -111,7 +128,9 @@ the one read a preview makes.)
 Mail and event text is written by other people, so `outlook_list_messages`,
 `outlook_get_message`, `outlook_list_events` and `outlook_get_event` 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.
+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).
 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`
 (the default) and approve each preview in chat — or use a client that asks you
@@ -131,7 +150,7 @@ a fresh preview.
 |---|---|---|
 | `MCP_CONFIRM_MODE` | `ask-user` | What a write does on a client that cannot show a confirmation prompt (claude.ai, Claude Desktop). `ask-user`: two steps — the first call does nothing and returns a preview plus a token, and the model must get your approval in chat before calling again with it. `auto`: the same two steps, but the model may use the token after reviewing the preview itself. `refuse`: writes are refused on such clients. A client that can show prompts (Claude Code) always gets the real prompt. An unrecognised value is treated as `refuse`. |
 | `MCP_CONFIRM_TTL_SECONDS` | `600` | How long a token stays valid. |
-| `MCP_CONFIRM_SECRET` | random per process | Signing key; set it only if tokens must survive a server restart. |
+| `MCP_CONFIRM_SECRET` | random per process | Signing key; set it only if tokens must survive a server restart. On mcp-host the host supplies a stable per-child key (`MCP_HOST_CONFIRM_SECRET`) and spent tokens are recorded under `MCP_DATA_DIR`, so an approval survives an idle restart. |
 
 ## Things worth knowing
 

package/dist/auth-fetchproxy.js

@@ -30,7 +30,7 @@ import { PACKAGE_NAME, VERSION } from './version.js';
 /**
  * The fetchproxy concentrator port.
  *
- * ONE port for the whole fleet: the Transporter extension dials this port and
+ * ONE port for the whole fleet: the ContextMint Bridge extension dials this port and
  * servers host/peer-elect on it, so a "unique" per-MCP default would simply
  * never be found. `OUTLOOK_WS_PORT` overrides it for local development and —
  * the reason it exists — for a hosted bridged registration, where mcp-host