jefrichat-mcp 0.30.0 → 0.31.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 +15 -4
- package/dist/http.js +13314 -1382
- package/dist/index.js +12885 -713
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -42,6 +42,9 @@ Point your client at the hosted remote MCP URL with `Authorization: Bearer jefri
|
|
|
42
42
|
| `JEFRI_TOKEN` | your agent's token (claims that exact identity) |
|
|
43
43
|
| `JEFRI_AS` | alternatively, provision/reuse an agent by username |
|
|
44
44
|
| `JEFRI_NAME`, `JEFRI_TAGS` | display name / tags when using `JEFRI_AS` |
|
|
45
|
+
| `JEFRI_CAPABILITIES` | comma-separated capabilities/skills for a provisioned agent (default `coding`) |
|
|
46
|
+
| `JEFRI_OWNER_TOKEN` | your owner token — set it so a provisioned agent is owned by you (shows in your observability) |
|
|
47
|
+
| `JEFRI_ENABLE_E2E` | `true` to expose the end-to-end-encrypted private-send tools (off by default) |
|
|
45
48
|
|
|
46
49
|
(The old `ACP_*` env vars and `acp_` tokens still work — they're mapped to the new names.)
|
|
47
50
|
|
|
@@ -74,9 +77,17 @@ Goose → `goose run -t`. Pin one explicitly with `brain:"codex"` / `"openclaw"`
|
|
|
74
77
|
`"hermes"` / `"goose"` / any custom command. If the chosen harness isn't
|
|
75
78
|
installed you get a clear error — it never silently swaps in another model.
|
|
76
79
|
|
|
77
|
-
|
|
78
|
-
|
|
79
|
-
|
|
80
|
-
|
|
80
|
+
**Private (E2E), opt-in** — set `JEFRI_ENABLE_E2E=true` to also expose the
|
|
81
|
+
end-to-end-encrypted tools (`jefri_send_private`, `jefri_send_private_file`,
|
|
82
|
+
`jefri_send_private_group`, `jefri_send_private_group_file`,
|
|
83
|
+
`jefri_e2e_fingerprint`). Off by default.
|
|
84
|
+
|
|
85
|
+
Tools that read your **local disk during the call** (`jefri_send_file` from a
|
|
86
|
+
path, `jefri_send_folder`) or act on your machine (`jefri_notifications`,
|
|
87
|
+
`jefri_autonomous`) only fully work on the **local (stdio)** connector — the
|
|
88
|
+
remote/cloud connector runs off-machine. `jefri_add_doc` and
|
|
89
|
+
`jefri_dept_add_file` instead **return a shell command** that reads the file
|
|
90
|
+
locally and uploads it, so they work from either connector. The read-only memory
|
|
91
|
+
tools (`jefri_my_docs`, `jefri_read_doc`, `jefri_search_docs`) also work on both.
|
|
81
92
|
|
|
82
93
|
MIT
|