mcp-newoutlook 0.23.2 → 0.24.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +10 -1
- package/dist/bridge.js +404 -79
- package/dist/bridge.js.map +1 -1
- package/dist/fairqueue.js +83 -0
- package/dist/fairqueue.js.map +1 -0
- package/dist/hub.js +215 -0
- package/dist/hub.js.map +1 -0
- package/dist/index.js +12 -3
- package/dist/index.js.map +1 -1
- package/dist/native.js +174 -0
- package/dist/native.js.map +1 -0
- package/dist/nativehost.js +123 -0
- package/dist/nativehost.js.map +1 -0
- package/dist/setup.js +22 -1
- package/dist/setup.js.map +1 -1
- package/dist/tools.js +9 -5
- package/dist/tools.js.map +1 -1
- package/extension/background.js +309 -107
- package/extension/chunks.js +69 -0
- package/extension/fairqueue.js +79 -0
- package/extension/manifest.json +2 -2
- package/extension/owa.js +8 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -62,6 +62,7 @@ npx mcp-newoutlook setup
|
|
|
62
62
|
|
|
63
63
|
- registers the server with the AI apps it finds: Claude Code, Claude Desktop, Cursor, VS Code (Copilot), Windsurf, Gemini CLI and Codex. It shows what it will change and asks first (`--yes` skips the question), only ever adds or updates its own `newoutlook` entry, and keeps a `.mcp-newoutlook.bak` copy of each file it changes. Other MCP clients: register `npx --prefer-online -y mcp-newoutlook@latest` as a stdio server. ChatGPT and claude.ai on the web can't use local servers;
|
|
64
64
|
- installs the extension in `~/.mcp-newoutlook/extension`;
|
|
65
|
+
- registers the native-messaging host for the Chrome and Edge profiles it finds (see [The native host](#the-native-host));
|
|
65
66
|
- opens the Extensions page of Chrome and/or Edge, and that folder. The one manual step, in the browser you use Outlook in: turn on *Developer mode* and click *Load unpacked* on the folder;
|
|
66
67
|
- waits until the extension connects and Outlook answers, then says *Ready*.
|
|
67
68
|
|
|
@@ -95,7 +96,13 @@ Every AI session starts its own mcp-newoutlook server, and they share the one ex
|
|
|
95
96
|
|
|
96
97
|
- The first server to start owns the bridge port and the extension connection (`role: "hub"` in `get_version`).
|
|
97
98
|
- Servers started later connect to the hub with the same pairing token and send their tool calls through it (`role: "peer"`).
|
|
98
|
-
- When the hub's session ends, a peer takes over the port within a second. The extension reconnects to it within 30 seconds; calls made in that gap fail with "Browser extension is not connected".
|
|
99
|
+
- When the hub's session ends, it first lets the other sessions' running calls (and open confirmation windows) finish, for up to 5 seconds; calls they make meanwhile go to the next hub. Then a peer takes over the port within a second. The extension reconnects to it within 30 seconds; calls made in that gap fail with "Browser extension is not connected".
|
|
100
|
+
|
|
101
|
+
### The native host
|
|
102
|
+
|
|
103
|
+
`setup` also registers a native-messaging host (`com.mcp_newoutlook.hub`) for each Chrome or Edge profile folder it finds: a host manifest and a small launcher that starts this Node with `dist/hub.js`. On macOS and Linux both go in the browser's `NativeMessagingHosts` folder; on Windows they go in `%LOCALAPPDATA%\mcp-newoutlook\`, with a registry key under `HKCU\Software\…\NativeMessagingHosts`. Chrome starts the host only for this extension. The hub then lives as long as the browser, not as long as the first AI session, so closing a session doesn't fail the others' calls. `npm run update` rewrites the host files so they point at the current copy and Node. Details: [docs/native-messaging.md](docs/native-messaging.md).
|
|
104
|
+
|
|
105
|
+
The extension tries the native host first. Where it isn't installed, or a policy blocks native messaging, the extension uses the TCP port as described above, and tries native again the next time it reconnects. `get_version` shows which one is in use: `transport: "native"` or `"websocket"` in the extension's status.
|
|
99
106
|
|
|
100
107
|
Connections from web pages are always refused, and peers need the pairing token. While the extension with the fixed id is connected, other copies of it (e.g. an older one loaded from another folder) are turned away.
|
|
101
108
|
|
|
@@ -115,6 +122,7 @@ Connections from web pages are always refused, and peers need the pairing token.
|
|
|
115
122
|
- The bridge listens only on `127.0.0.1`. Web pages can't connect to it: browsers send their Origin, and only extension origins are accepted. This extension is recognized by its fixed id (from the `key` in its manifest), which other extensions can't take; any other extension, and local programs, need the pairing token in `~/.mcp-newoutlook/config.json`. A local program able to read that file could connect either way, so the token was never a defense against those.
|
|
116
123
|
- Downloaded file names come from emails and are sanitized, so they can't escape the target folder.
|
|
117
124
|
- Emails can contain prompt injection. The send-confirmation window is the safeguard, so read it before clicking Send.
|
|
125
|
+
- A change retried with the same content within 10 minutes (drafts, attachments, events, and answers or invitations you approved) returns the first result instead of acting twice. This is kept only in the extension's memory, as SHA-256 hashes and outcomes (ids, flags), never bodies or file contents, and is cleared when the extension reloads. It never skips a confirmation window: a retry after you declined or closed one asks again.
|
|
118
126
|
- If you also give an AI direct control of your browser or desktop (for example browser automation), it could click the confirmation button itself. Don't combine the two if you rely on the confirmation step.
|
|
119
127
|
|
|
120
128
|
## Limitations
|
|
@@ -122,6 +130,7 @@ Connections from web pages are always refused, and peers need the pairing token.
|
|
|
122
130
|
- It relies on Outlook on the web's internal JSON API (`/owa/service.svc`), which Microsoft doesn't document and can change. All request shapes live in `extension/owa.js`.
|
|
123
131
|
- Without full-text search (see Search syntax), search matches substrings in fields (subject, body, sender, `To`/`Cc` display names).
|
|
124
132
|
- Emails can't be permanently deleted, only moved to Deleted Items.
|
|
133
|
+
- Teams invitations made through `create_event` have the join link and meeting ID but no passcode: Outlook fetches that from a Teams service this extension doesn't have access to; people join from the link, which carries it.
|
|
125
134
|
- Outlook doesn't hand out an attached email's original MIME, so its `.eml` is rebuilt from the original headers, body and attachments. It opens normally in mail clients, but isn't byte-identical to the original (e.g. signatures can't be verified).
|
|
126
135
|
- `download_email` and attached emails in `download_attachments` are limited to 30 MB per email (Outlook's size of the item). A larger one is refused before it is fetched; the error gives its size and a link to open it in Outlook.
|
|
127
136
|
|