file-share-mcp 1.0.17 → 1.0.18
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 +3 -3
- package/dist/version.js +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -126,9 +126,9 @@ Nothing to configure.
|
|
|
126
126
|
the server runs on the gateway machine, and neither path means anything there. MCP has no
|
|
127
127
|
file-transfer primitive — only the bytes a message carries actually travel — so the relay,
|
|
128
128
|
which runs next to the agent in `--mcp` mode, fills the gap in both directions. Configure it
|
|
129
|
-
with `GATEWAY_INLINE_ROOTS` (reading, for `copy_file`)
|
|
130
|
-
(writing, for `download_file`)
|
|
131
|
-
|
|
129
|
+
with `GATEWAY_INLINE_ROOTS` (reading, for `copy_file`) and `GATEWAY_INLINE_WRITE_ROOTS`
|
|
130
|
+
(writing, for `download_file`). Those two directory lists are the whole configuration: every
|
|
131
|
+
file type is allowed by default.
|
|
132
132
|
|
|
133
133
|
Neither direction has a fallback. With the relay in the chain but the matching root
|
|
134
134
|
unconfigured, the call fails and names the variable to set; nothing is read, written, or
|
package/dist/version.js
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
export const VERSION = '1.0.
|
|
1
|
+
export const VERSION = '1.0.18';
|