mcp-teams 0.3.72 → 0.3.73

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 CHANGED
@@ -158,7 +158,7 @@ A server that is already running keeps its code when the copy on disk changes (`
158
158
  - The server and the extension prove to each other that they know the pairing token in `~/.mcp-teams/config.json`, without sending it. Setup copies it into the installed extension folder as `pairing.json`; both files can be read only by your user. So a program that takes the port while no AI app runs gets nothing from the extension, and a program posing as the extension gets no calls.
159
159
  - Teams' tokens are only ever sent to the service they were captured from.
160
160
  - Messages can contain prompt injection. The send-confirmation window is the safeguard, so read it before clicking Send. With `autoSendTo` set, messages to yourself alone skip it (see Configuration).
161
- - The extension may observe requests to Microsoft hosts (`*.microsoft.com`, `*.office.com`, `*.sharepoint.com` and similar), but it only records requests made by the Teams tab, only names, and only while `api_traffic` recording is on. Apart from that it keeps only the time and host of the Teams tab's last call and last signed-in call (see *When Teams has no session*). It runs requests only in Teams tabs, and in SharePoint tabs to read transcripts.
161
+ - The extension may observe requests to Microsoft hosts (`*.microsoft.com`, `*.office.com`, `*.sharepoint.com` and similar), but it only records requests made by the Teams tab, only names, and only while `api_traffic` recording is on. That includes WebSocket handshakes (`wss://`) and beacons, never what a socket carries. The extension also has `wss://` host permissions for these hosts, so it can see those handshakes; reloading the extension after an update picks them up. Apart from that it keeps only the time and host of the Teams tab's last call and last signed-in call (see *When Teams has no session*). It runs requests only in Teams tabs, and in SharePoint tabs to read transcripts.
162
162
  - If you also give an AI direct control of your browser or desktop, it could click the confirmation button itself. Don't combine the two if you rely on the confirmation step.
163
163
 
164
164
  ## Limitations
package/dist/build.json CHANGED
@@ -1,4 +1,4 @@
1
1
  {
2
- "version": "0.3.72",
3
- "buildId": "1274f3433802"
2
+ "version": "0.3.73",
3
+ "buildId": "3daff63d2b0a"
4
4
  }
@@ -236,12 +236,28 @@ export function savePendingTraffic() {
236
236
  store.set({ [TRAFFIC_KEY]: traffic }).catch(() => {}); // kept in memory: the next change saves again
237
237
  }
238
238
 
239
- const trafficFilter = { urls: teams.TRAFFIC_URLS, types: ["xmlhttprequest", "other", "media"] };
239
+ /**
240
+ * Recorded for api_traffic but not a last call (#200): websocket (a WebSocket handshake, e.g.
241
+ * trouter) and ping (navigator.sendBeacon). A trouter WebSocket opens once and stays open, and a
242
+ * beacon is fire-and-forget, often sent as the page goes away, so neither on its own says the tab
243
+ * is active; the last calls keep counting only the types they counted before.
244
+ */
245
+ const TRAFFIC_ONLY_TYPES = ["websocket", "ping"];
246
+
247
+ /**
248
+ * The traffic log hears these types too, so api_traffic shows a feature that talks over them, and
249
+ * the wss:// URLs Chrome reports handshakes under (#200). Only the handshake or beacon is seen, never
250
+ * what a socket carries; a handshake's onCompleted, if Chrome reports one, gives its status (101).
251
+ * A socket opened before recording started (trouter opens at page load) is never seen: anything
252
+ * sent over it later leaves no request here.
253
+ */
254
+ const trafficFilter = { urls: [...teams.TRAFFIC_URLS, ...teams.TRAFFIC_WS_URLS], types: ["xmlhttprequest", "other", "media", ...TRAFFIC_ONLY_TYPES] };
240
255
 
241
256
  function recordRequest(details) {
242
257
  if (!teams.isTeamsOrigin(details.initiator)) return;
243
258
  const entry = teams.summarizeRequest(details);
244
259
  updateTraffic((list) => teams.recordTraffic(list, entry), { ifRecording: true });
260
+ if (TRAFFIC_ONLY_TYPES.includes(details.type)) return;
245
261
  return noteCall(details);
246
262
  }
247
263
 
@@ -2,7 +2,7 @@
2
2
  "manifest_version": 3,
3
3
  "key": "MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvoz9Wexl4ZqY9YtEyBZsu/Qi5Ft5EjNUNB8b30wgt3AR8TjXI5UumcPQFBIm7ZfvBsjgrh6tBJlygsgFbZ5cB1EiI+WSz/2Wcqwz4eowKMXXPvGuDGrO+2O2zbSpTG19/MwTljI+g0TLfn8Vkoqd8z9MskKk+vCZjjV0Jk8QjVEdHypgM7H8zTuUM06SO12IIZMdeE3IURzf35zbjlfPPkJiDWoo3wB9nxAvLd57xrQhPUB/lGtCJk9mS3SY+/VwOlG5kJ9WS/RCHXcs5Qs7huIlKIatmFz7YiducvTR3DKBbjqbMTyqHzXkmkUmJRqzsYtgtKcz0C0cjFOt6uNdhwIDAQAB",
4
4
  "name": "mcp-teams bridge",
5
- "version": "0.3.72",
5
+ "version": "0.3.73",
6
6
  "description": "Lets AI assistants (via the mcp-teams MCP server) read and search Microsoft Teams chats, channels and meeting transcripts and, with your explicit confirmation, post messages.",
7
7
  "minimum_chrome_version": "116",
8
8
  "icons": {
@@ -34,7 +34,14 @@
34
34
  "https://*.office.net/*",
35
35
  "https://*.sharepoint.com/*",
36
36
  "https://*.svc.ms/*",
37
- "https://*.skype.com/*"
37
+ "https://*.skype.com/*",
38
+ "wss://*.cloud.microsoft/*",
39
+ "wss://*.microsoft.com/*",
40
+ "wss://*.office.com/*",
41
+ "wss://*.office.net/*",
42
+ "wss://*.sharepoint.com/*",
43
+ "wss://*.svc.ms/*",
44
+ "wss://*.skype.com/*"
38
45
  ],
39
46
  "action": {
40
47
  "default_title": "mcp-teams",
@@ -847,6 +847,9 @@ export const TRAFFIC_URLS = [
847
847
  "https://*.skype.com/*",
848
848
  ];
849
849
 
850
+ /** The same hosts for WebSocket handshakes, which Chrome reports under their wss:// URL (#200). */
851
+ export const TRAFFIC_WS_URLS = TRAFFIC_URLS.map((u) => u.replace(/^https:/, "wss:"));
852
+
850
853
  const TEAMS_ORIGIN = /^https:\/\/(teams\.cloud\.microsoft|teams\.microsoft\.com)$/i;
851
854
 
852
855
  /** Whether a request comes from the Teams web app (its page or its workers). */
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "mcp-teams",
3
- "version": "0.3.72",
3
+ "version": "0.3.73",
4
4
  "description": "MCP server that lets AI assistants work with Microsoft Teams (web) through a Chrome/Edge extension bridge",
5
5
  "keywords": ["mcp", "model-context-protocol", "teams", "microsoft-teams", "microsoft-365", "chat", "claude", "chrome-extension"],
6
6
  "repository": {