@embd/mcp 0.7.1 → 0.7.3
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 +12 -6
- package/dist/{bin-2pd22980.js → bin-23re2y63.js} +9 -9
- package/dist/{bin-crkm8v3n.js → bin-hadzj9pc.js} +1 -1
- package/dist/{bin-facfqmdm.js → bin-mvjk1fq0.js} +2 -2
- package/dist/{bin-ph1y1a8b.js → bin-vnnxgm54.js} +1 -1
- package/dist/{bin-5b95b3jx.js → bin-y6fp1ys8.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/README.md
CHANGED
|
@@ -168,7 +168,9 @@ 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
|
-
|
|
171
|
+
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
|
+
|
|
173
|
+
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.
|
|
172
174
|
|
|
173
175
|
Tools list the authorized workspace's documents, read current source and discussions, create MD/HTML, submit version-checked revisions, comment/reply, and read older history/discussion pages. Read before editing and send both `expectedRevision` and `expectedEditVersion`. On 409, reread and reconcile rather than silently retrying a replacement. A human or another agent can then continue at the same document link. Agent-authored messages/revisions retain the authorizing person's identity and the agent identity. Tokens cannot invite members or manage access.
|
|
174
176
|
|
|
@@ -186,8 +188,10 @@ Use an integer `revision` to pin a saved version. References require current acc
|
|
|
186
188
|
### Guided private-document setup
|
|
187
189
|
|
|
188
190
|
In **Workspace → Agent access**, the owner can now generate a private Codex
|
|
189
|
-
TOML or Claude Desktop JSON configuration.
|
|
190
|
-
|
|
191
|
+
TOML or Claude Desktop JSON configuration. Install the published package, then
|
|
192
|
+
use the default `embd-documents-mcp` command or enter its absolute path.
|
|
193
|
+
Choose **Local source build** only when developing from a repository checkout;
|
|
194
|
+
that option takes the built `packages/mcp/dist/documents-bin.js` path and Node executable.
|
|
191
195
|
The configuration uses the current workspace application's origin, including
|
|
192
196
|
preview origins. Protected Vercel previews may not be reachable by an external
|
|
193
197
|
client; use an accessible deployment for the real client check.
|
|
@@ -208,8 +212,10 @@ revocation. Existing secrets cannot be redisplayed.
|
|
|
208
212
|
|
|
209
213
|
Private document MCP currently uses local stdio. The key-free HTTP server
|
|
210
214
|
above is a different stateless product surface and cannot access private
|
|
211
|
-
workspaces.
|
|
212
|
-
private-document MCP connector.
|
|
215
|
+
workspaces. Installing the published package provides the local stdio server;
|
|
216
|
+
the guided setup does not create a hosted private-document MCP connector.
|
|
217
|
+
Version-specific publication and deployed behavior are verified separately by
|
|
218
|
+
the paired release checks.
|
|
213
219
|
|
|
214
220
|
Client configuration references (checked October 1, 2026):
|
|
215
221
|
[Codex MCP](https://developers.openai.com/codex/mcp),
|
|
@@ -249,7 +255,7 @@ embd workspace kb_status --input '{"workspaceId":"<workspace UUID>"}'
|
|
|
249
255
|
embd workspace kb_forget --input '{"workspaceId":"<workspace UUID>"}'
|
|
250
256
|
```
|
|
251
257
|
|
|
252
|
-
The same
|
|
258
|
+
The same seven `kb_*` operations are available in `embd-documents-mcp`. Call `kb_sync` explicitly there or run the CLI watch process with the same token/origin/cache directory. MCP does not silently start a daemon. `workspace tools` and each command's `--help` expose shared schemas. Search requires all literal terms, with Unicode tokenization; it is lexical, not semantic. Results contain stable document URLs, exact source versions/hashes and freshness. `kb_read` returns bounded source slices; use `nextOffset` to continue. Reads can be stale: fetch the current server document before editing. Relative links resolve only within the synced selection using retained bases and rename aliases; unresolved targets are not automatically downloaded.
|
|
253
259
|
|
|
254
260
|
Changing the selected IDs atomically replaces the local set after complete sync. Interrupted attempts retain the previous complete replica and its original expiry. A server cursor reset triggers a full reconciliation. A 401/403/404 clears the affected replica. `kb_forget` removes local content without deleting server documents. This is pull-only source sync: discussions, offline editing, automatic folder ingestion and embeddings are not included.
|
|
255
261
|
|