hypermail-mcp 0.7.5 → 0.7.6
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 +14 -9
- package/dist/cli.js +14130 -285
- package/dist/cli.js.map +1 -1
- package/package.json +3 -2
package/README.md
CHANGED
|
@@ -3,6 +3,11 @@
|
|
|
3
3
|
A **Model Context Protocol** server that lets an agent operate any of the user's
|
|
4
4
|
inboxes through a single, unified tool surface.
|
|
5
5
|
|
|
6
|
+
> **v0.7.6** — Strict provider env var enforcement. Legacy env vars
|
|
7
|
+
> (`MS_CLIENT_ID`, `MS_TENANT_ID`, `GOOGLE_CLIENT_ID`,
|
|
8
|
+
> `GOOGLE_CLIENT_SECRET`) are unconditionally ignored; only the dedicated
|
|
9
|
+
> `HYPERMAIL_PROVIDERS_*` names are resolved.
|
|
10
|
+
>
|
|
6
11
|
> **v0.7.5** — Attachments via file path on `send_email`/`draft_email`
|
|
7
12
|
> (`attachments` param). `edit_draft` gains `new_attachments` and
|
|
8
13
|
> `remove_attachments` — `add_attachment_to_draft` is removed (23 tools now).
|
|
@@ -21,8 +26,7 @@ inboxes through a single, unified tool surface.
|
|
|
21
26
|
> (above the spacer delimiter) is replaced.
|
|
22
27
|
>
|
|
23
28
|
> **v0.7.1** — Every config field is now settable via a dedicated
|
|
24
|
-
> `HYPERMAIL_*` env var. Legacy env vars
|
|
25
|
-
> `GOOGLE_CLIENT_ID`, `GOOGLE_CLIENT_SECRET`) still work as fallbacks. See
|
|
29
|
+
> `HYPERMAIL_*` env var. Legacy provider env vars are no longer accepted. See
|
|
26
30
|
> [Environment Variables](#environment-variables) for the full reference.
|
|
27
31
|
>
|
|
28
32
|
> **v0.7.0** — Email watch mode: background poll loop detects new inbox
|
|
@@ -120,8 +124,8 @@ docker run -d \
|
|
|
120
124
|
--name hypermail-mcp \
|
|
121
125
|
-p 3000:3000 \
|
|
122
126
|
-e HYPERMAIL_MCP_KEY=<32-byte-key> \
|
|
123
|
-
-e
|
|
124
|
-
-e
|
|
127
|
+
-e HYPERMAIL_PROVIDERS_OUTLOOK_CLIENT_ID=<your-client-id> \
|
|
128
|
+
-e HYPERMAIL_PROVIDERS_OUTLOOK_TENANT_ID=<your-tenant-id> \
|
|
125
129
|
-v hypermail-data:/data \
|
|
126
130
|
hypermail-mcp
|
|
127
131
|
```
|
|
@@ -151,8 +155,8 @@ The server listens on `http://127.0.0.1:3000/mcp`. Pi connects via the
|
|
|
151
155
|
| --- | --- | --- |
|
|
152
156
|
| `HYPERMAIL_MCP_DATA_DIR` | Where to keep the encrypted accounts blob | `~/.hypermail-mcp` |
|
|
153
157
|
| `HYPERMAIL_MCP_KEY` | 32-byte AES-256-GCM key (hex, base64, or any passphrase — derived via SHA-256). Required for hosted deployments. Auto-generated for stdio. | auto-generated, stored via OS keychain (`keytar`) or a local `master.key` file |
|
|
154
|
-
| `
|
|
155
|
-
| `
|
|
158
|
+
| `HYPERMAIL_PROVIDERS_OUTLOOK_CLIENT_ID` | Azure Entra public client (application) id used for device-code login | placeholder — **set your own for production** |
|
|
159
|
+
| `HYPERMAIL_PROVIDERS_OUTLOOK_TENANT_ID` | Tenant for the authority URL | `common` |
|
|
156
160
|
|
|
157
161
|
CLI flags: `--http`, `--port`, `--host`, `--data-dir`, `--read-only`, `--help`.
|
|
158
162
|
|
|
@@ -196,9 +200,10 @@ and read emails.
|
|
|
196
200
|
|
|
197
201
|
Every config field can be set via a dedicated `HYPERMAIL_*` env var, following
|
|
198
202
|
a dotted-path naming convention (`HYPERMAIL_HTTP_PORT`,
|
|
199
|
-
`HYPERMAIL_PROVIDERS_OUTLOOK_CLIENT_ID`, etc.). Legacy env vars
|
|
200
|
-
|
|
201
|
-
|
|
203
|
+
`HYPERMAIL_PROVIDERS_OUTLOOK_CLIENT_ID`, etc.). Legacy provider env vars such
|
|
204
|
+
as `MS_CLIENT_ID`, `MS_TENANT_ID`, `GOOGLE_CLIENT_ID`, and
|
|
205
|
+
`GOOGLE_CLIENT_SECRET` are ignored; use the `HYPERMAIL_PROVIDERS_*` names
|
|
206
|
+
below.
|
|
202
207
|
|
|
203
208
|
| Env var | Config path | Type |
|
|
204
209
|
| --- | --- | --- |
|