@embd/mcp 0.7.6 → 0.7.8
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 +16 -0
- package/dist/bin-0ftgp1t8.js +70 -0
- package/dist/{bin-5nmmdwrv.js → bin-361phfqr.js} +1 -1
- package/dist/{bin-y6yfg1je.js → bin-66kzqre3.js} +1 -1
- package/dist/{bin-v8v8gkhr.js → bin-9vtm5gnz.js} +1 -1
- package/dist/{bin-q74qdkyd.js → bin-bw6a4d6a.js} +1 -1
- package/dist/bin.js +1 -1
- package/dist/documents-bin.js +1 -1
- package/dist/http-bin.js +1 -1
- package/dist/index.js +1 -1
- package/package.json +2 -2
- package/dist/bin-hmjc7445.js +0 -70
package/README.md
CHANGED
|
@@ -168,6 +168,16 @@ The separate `embd-documents-mcp` entry point works with private workspace Markd
|
|
|
168
168
|
|
|
169
169
|
A workspace owner opens **Workspace → Agent access**, chooses a name and read/comment/edit scope, and copies the credential once. Access is workspace-scoped, expires after 30 days and can be revoked there. Configure it as `EMBD_DOCUMENT_TOKEN`; optionally set `EMBD_DOCUMENT_ORIGIN` (default `https://app.embd.sh`). Never place the token in document source or a shared configuration file.
|
|
170
170
|
|
|
171
|
+
A guest invited to one document can also open **Agent access** from that document.
|
|
172
|
+
That credential is capped to the named document and the guest's current role;
|
|
173
|
+
listing, search, history, comments, images and selected-document sync respect the
|
|
174
|
+
same boundary. The agent cannot create documents, import sets, change folders,
|
|
175
|
+
upload workspace images, invite people or alter access. Revoking the guest or
|
|
176
|
+
lowering their role immediately limits future server requests by their agent.
|
|
177
|
+
An existing downloaded copy cannot be recalled; local replicas retain their
|
|
178
|
+
bounded offline lease. Invitation acceptance and audience management stay in
|
|
179
|
+
the human **Share** flow.
|
|
180
|
+
|
|
171
181
|
Install the published package with `npm install --global @embd/mcp` using Node.js 22.13 or later, then configure your MCP client to launch `embd-documents-mcp` with that environment and no arguments. The workspace setup panel supplies a version-pinned install command matching its release. If your desktop client cannot find the command, use its absolute path (`command -v embd-documents-mcp` on macOS/Linux).
|
|
172
182
|
|
|
173
183
|
A source build remains available for contributors: run `bun install` and `bun run --filter @embd/mcp build` from the repository, then launch `node /absolute/path/to/embd/packages/mcp/dist/documents-bin.js`. A source checkout is not required for the published client.
|
|
@@ -289,3 +299,9 @@ its retained link base within `files/`, preserving exact relative image links;
|
|
|
289
299
|
its current workspace path remains in the manifest. The JSON form has each file's
|
|
290
300
|
encoding/content; the ZIP contains real source/image files instead of base64.
|
|
291
301
|
MCP returns the same JSON package and does not write to the machine's filesystem.
|
|
302
|
+
|
|
303
|
+
Document request continuity: `agent_requests` lists scoped request progress and
|
|
304
|
+
proposal links; `read_agent_request` reads one request. These tools do not dispatch
|
|
305
|
+
paid work or expose execution leases. Humans use the document’s **Ask an agent**
|
|
306
|
+
flow with `embd agent serve` from the paired CLI. Review and discussion continue
|
|
307
|
+
through the existing proposal/thread tools, with the same access and version checks.
|