mcp-newoutlook 0.22.0 → 0.23.1

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
@@ -14,7 +14,7 @@ AI app ────stdio(MCP)──► mcp-newoutlook server ──ws://127.0.0.
14
14
 
15
15
  | Tool | What it does |
16
16
  |---|---|
17
- | `get_version` | Server and extension versions, and the connection/session status. Temporarily (diagnostic for #48), `outlook.sessionRequests` lists the last 50 requests Outlook sent to `/search/`, `/searchservice/` and `/outlookgatewayb2/` since the extension's background worker started (`since`; the list is kept in memory only): time, method, Outlook host, path (no query; ids masked), request type, whether it came from a tab and from a page (`frameType`) or a worker, and whether a non-empty authorization header was sent (never its value) |
17
+ | `get_version` | Server and extension versions, and the connection/session status. Per Outlook site, `fullTextSearch` and `teamsMeetings` show whether its search and Teams sessions are there yet |
18
18
  | `reload_extension` | Reloads the browser extension from disk after an update and waits until it is back, reporting the version before and after |
19
19
  | `list_folders` | Every mail folder, including subfolders, with its path (`Inbox/Projects/Northwind`) and counts (`include_ids: true` adds folder ids) |
20
20
  | `search_emails` | Lists emails, or searches them with Outlook-style syntax (`from:alice`, `subject:report`, `cc:bob`, `hasattachment:yes`, `after:2026-09-01`, `received:today`; see below) in Outlook's full-text index, newest first or by relevance (`order`). By default it covers Inbox, Sent Items and all their subfolders. `folder` takes a standard name (`inbox`, `sentitems`…), a path or id from `list_folders`, a list of these, or `all` for every folder; each folder is searched with its subfolders (`subfolders: false` leaves them out). Results carry their folder path. `preview: true` adds each email's To line and the start of its body. Each result carries its `conversationId` |
@@ -23,9 +23,9 @@ AI app ────stdio(MCP)──► mcp-newoutlook server ──ws://127.0.0.
23
23
  | `list_events` | Calendar appointments and meetings in a date range (default: the next 7 days), optionally only those whose subject, location, organizer or attendees match `query` (`searchNote` says when attendees couldn't be read), recurring meetings expanded, with location, organizer, your response and free/busy. Times in UTC and local time. |
24
24
  | `find_meeting_times` | Suggests times when you and the attendees (addresses or names) are all free, from their free/busy and your calendar, inside working hours (default 09:00–17:00 local, weekdays). Tentative meetings count as busy unless `allow_tentative` |
25
25
  | `read_event` | One event with its attendees and their responses, and the description |
26
- | `find_contacts` | Looks people up by name, email or domain in your personal contacts, the organization directory and the people you exchange email with (external partners). Contacts and directory give job title, department, company, office and phone numbers where stored; people from mail come with how many emails were found, the latest one, the folders they're filed in and the signature of their latest email (usually title, company, phone and address). `source` picks `contacts`, `directory`, `mail` or `all` (mail only when contacts and the directory find nobody, since it scans every folder). |
26
+ | `find_contacts` | Looks people up by name, email or domain in your personal contacts, the organization directory and the people you exchange email with (external partners). Contacts and directory give job title, department, company, office and phone numbers where stored; people from mail come with how many emails were found, the latest one, the folders they're filed in and the signature of their latest email (usually title, company, phone and address). `source` picks `contacts`, `directory`, `mail` or `all` (mail only when contacts and the directory find nobody, since it scans every folder). If Outlook is throttling, the mail part can be incomplete; the answer then says `partial: true`. |
27
27
  | `respond_to_event` | Accept, tentatively accept or decline a meeting, optionally with a note to the organizer. **You must confirm.** |
28
- | `create_event` | Your own appointment (created at once, nothing is sent), or a meeting with attendees by address or name, whose invitation **you must confirm**. Meetings get a Microsoft Teams link by default (`teams_meeting`), made the way Outlook makes it; this needs Outlook to have created a Teams meeting once since the browser or extension started |
28
+ | `create_event` | Your own appointment (created at once, nothing is sent), or a meeting with attendees by address or name, whose invitation **you must confirm**. Meetings get a Microsoft Teams link by default (`teams_meeting`), made the way Outlook makes it. Outlook sets up its Teams session when its tab loads; if there is none, reload the Outlook tab (or give `teams_meeting: false`) |
29
29
  | `create_draft` | Writes an email into Drafts. Never sends. |
30
30
  | `create_reply_draft` | Reply or reply all to an email, as a draft with the original quoted. Never sends. |
31
31
  | `create_forward_draft` | Forward an email with its attachments, as a draft. Never sends. |
@@ -42,7 +42,7 @@ Email and folder ids can be Outlook's own or Microsoft Graph's (with `-` and `_`
42
42
 
43
43
  ### Recipients by name
44
44
 
45
- `to`, `cc` and `bcc` (in `create_draft`, `create_reply_draft`, `create_forward_draft`, `update_draft` and `compose_and_send`) take email addresses or names, e.g. `["Daniel Kowalski", "bob@example.com"]`. Each name is looked up in your contacts, the directory and your mail at once (a few seconds), and must mean exactly one person: an exact full-name match wins among several ("Kowalski, Daniel (ENG)" matches "Daniel Kowalski"). Otherwise nothing is created and the matching people are listed. The result's `resolvedRecipients` shows what each name became.
45
+ `to`, `cc` and `bcc` (in `create_draft`, `create_reply_draft`, `create_forward_draft`, `update_draft` and `compose_and_send`) take email addresses or names, e.g. `["Daniel Kowalski", "bob@example.com"]`. Each name is looked up in your contacts and the directory first (a few seconds); your mail is searched too only when they don't give exactly one exact full-name match, so an outside sender with the same name as a colleague isn't considered. A name must mean exactly one person: an exact full-name match wins among several ("Kowalski, Daniel (ENG)" matches "Daniel Kowalski"). Otherwise nothing is created and the matching people are listed. The result's `resolvedRecipients` shows what each name became.
46
46
 
47
47
  ### Sending always needs your click
48
48
 
@@ -79,7 +79,7 @@ Coming from a version before 0.15 (a git clone, extension loaded from the repo's
79
79
 
80
80
  ## Search syntax
81
81
 
82
- Searches go to Outlook's full-text index, the one its own search box uses: whole words in the subject, body, people and attachment contents (`search: "fulltext"` in the result). The index needs the search session Outlook sets up when it loads or when you use its search box, so after the browser or the extension starts, **reload the Outlook tab or search once in Outlook** to turn it on. Until then, and in folders you made yourself, fields are matched as described under Limitations (`search: "substring"`, `searchNote` says why). The index can only be limited to a standard folder without its subfolders, and it gives only the first 25 matches of a search. So a search over subfolders asks the index for matches in every folder and keeps those in the chosen folders; when that first page doesn't hold enough of them, fields are matched instead. When the index answers without seeing every match, `total` is `null` (`includesLastItem` still tells whether there are more). When nothing is found, `emptyNote` says what wasn't searched: other folders, folders that couldn't be searched, or attachment contents with field matching.
82
+ Searches go to Outlook's full-text index, the one its own search box uses: whole words in the subject, body, people and attachment contents (`search: "fulltext"` in the result). The index needs the search session Outlook sets up when it loads or when you use its search box, so after the browser or the extension starts, **reload the Outlook tab or search once in Outlook** to turn it on. Until then, and in folders you made yourself, fields are matched as described under Limitations (`search: "substring"`, `searchNote` says why). The index can only be limited to a standard folder without its subfolders, and it gives only the first 25 matches of a search. So a search over subfolders asks the index for matches in every folder and keeps those in the chosen folders; when that first page doesn't hold enough of them, fields are matched instead. In standard folders, a `limit` above 25 still gives only those 25 matches, with a `searchNote` saying more exist; to see the rest, narrow the query (e.g. with dates) or page on with `offset`, which matches fields from offset 25 on (and earlier when the first page can't fill the page asked for). When the index answers without seeing every match, `total` is `null` (`includesLastItem` still tells whether there are more). When nothing is found, `emptyNote` says what wasn't searched: other folders, folders that couldn't be searched, or attachment contents with field matching.
83
83
 
84
84
 
85
85
  - Free words match the subject, body or sender. `"Quoted phrases"` match as a whole.
@@ -132,9 +132,11 @@ cd mcp-newoutlook
132
132
  npm install && npm run build
133
133
  node dist/index.js setup # registers this copy (node dist/index.js) instead of npx
134
134
  npm run update # on main with no local changes: pulls, builds, reloads the extension
135
- npm test # builds, then runs unit + end-to-end tests (fake extension)
135
+ npm test # builds, typechecks the tests, scans fixtures, then runs every test layer
136
136
  npm run smoke # read-only live check against your real mailbox (needs Chrome with the extension and Outlook open)
137
137
  ```
138
+
139
+ Tests are written first, one layer per folder (see [docs/testing.md](docs/testing.md)): `test/unit` (pure functions; `npm run test:unit`), `test/integration` (the extension's handlers on a fake `chrome`, and the bridge on real sockets; `npm run test:integration`), `test/system` (the built server over stdio, including a snapshot of every tool's description and schema; `npm run test:system`). A bug fix starts with a failing test named after its issue.
138
140
  Versions are bumped automatically. On every push to `main` (except Markdown-only changes), the **Version bump** GitHub Action runs the tests, then bumps `package.json`, `package-lock.json` and `extension/manifest.json`, commits `chore(release): vX.Y.Z` and tags it. The bump level comes from the pushed commit messages:
139
141
 
140
142
  | Commit message | Bump |