@bendyline/gezel-mcp 1.2.7 → 1.2.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 CHANGED
@@ -9,16 +9,50 @@ operations, project artifacts, the shared document library, script and
9
9
  Playwright execution, task management, team and project management, image
10
10
  rendering, and history search.
11
11
 
12
- Gezel runs this server for every gezel's chat. You can also run it from any
13
- other MCP client, so that client works with your gezels' memories, projects,
14
- and tasks.
12
+ Gezel runs this server for every gezel's chat. It also gives other AI apps
13
+ (Claude Code, Codex, Cursor, Claude Desktop, VS Code) a small set of Gezel's
14
+ tools; see [For other AI apps](#for-other-ai-apps).
15
15
 
16
16
  ```bash
17
17
  npm install @bendyline/gezel-mcp
18
18
  ```
19
19
 
20
- It speaks stdio, so any MCP client can run it. With Gezel running on the same
21
- computer:
20
+ ## For other AI apps
21
+
22
+ `gezel-mcp --harness <client>` (`claude-code`, `claude-desktop`, `codex`,
23
+ `cursor` or `vscode`) gives an app that already has its own file, shell and
24
+ web tools what only Gezel has: search over the folder it works in (including
25
+ the text of its Office documents), the person's shared library, memories and
26
+ knowledge catalogs, Office documents read as markdown, image description and
27
+ generation, and memory. Nine tools in all, with absolute paths throughout.
28
+
29
+ Set it up from Gezel (Settings → Integrations, or `gezel mcp install <app>`),
30
+ which writes the app's entry for you. By hand, run the server under Node 24 or
31
+ later from the folder you work in:
32
+
33
+ ```json
34
+ {
35
+ "mcpServers": {
36
+ "gezel": {
37
+ "command": "npx",
38
+ "args": ["-y", "@bendyline/gezel-mcp", "--harness", "claude-code"]
39
+ }
40
+ }
41
+ }
42
+ ```
43
+
44
+ The server binds the Gezel project for the folder the app reports (MCP roots),
45
+ or `--folder <path>`, or its working directory; `--project <id>` names one
46
+ outright. It reads the owner credential from `~/.gezel/runtime/` once and
47
+ trades it for a token confined to that project and to the choices the person
48
+ made in Gezel, so the app's model never acts with the person's full access. If
49
+ Gezel is not running, every tool says so instead of the server exiting.
50
+
51
+ ## The full surface, with your own access
52
+
53
+ Without `--harness` the server offers every tool a gezel has, acting with your
54
+ own access, as the `gezel` command does. It speaks stdio, so any MCP client can
55
+ run it. With Gezel running on the same computer:
22
56
 
23
57
  ```json
24
58
  {
package/dist/bin.d.ts ADDED
@@ -0,0 +1,2 @@
1
+
2
+ export { }
package/dist/bin.js ADDED
@@ -0,0 +1,5 @@
1
+ #!/usr/bin/env node
2
+
3
+ // src/bin.ts
4
+ var entry = process.argv.includes("--harness") ? "./harness.js" : "./server.js";
5
+ await import(new URL(entry, import.meta.url).href);
@@ -0,0 +1,2 @@
1
+
2
+ export { }