@bendyline/gezel-mcp 1.2.4 → 1.2.6

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
@@ -1,13 +1,18 @@
1
1
  # @bendyline/gezel-mcp
2
2
 
3
3
  The [Model Context Protocol](https://modelcontextprotocol.io) server that gives
4
- [gezel](https://github.com/bendyline/gezel) agents their hands.
4
+ gezels, the AI companions in [Gezel](https://github.com/bendyline/gezel), their
5
+ hands.
5
6
 
6
7
  Every tool a gezel can call lives here: memory search and save, workspace file
7
8
  operations, project artifacts, the shared document library, script and
8
9
  Playwright execution, task management, team and project management, image
9
10
  rendering, and history search.
10
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.
15
+
11
16
  ```bash
12
17
  npm install @bendyline/gezel-mcp
13
18
  ```
@@ -49,6 +54,10 @@ it, then reconnect the server from your MCP client.
49
54
  Run this way, the server acts with your own access, as the `gezel` command
50
55
  does; `GEZEL_PROJECT_ID` picks a default, not a boundary.
51
56
 
57
+ `gezel agent list` (from `@bendyline/gezel-cli`) lists your gezels and their
58
+ ids. The `agent` in that command and in `GEZEL_AGENT_ID` is a historical name:
59
+ both refer to your gezels.
60
+
52
61
  When Gezel starts the server itself, for a gezel's chat, it passes the
53
62
  connection directly: `GEZEL_BASE_URL`, `GEZEL_TOKEN` (a token it mints for that
54
63
  one session, confined to its project unless the gezel coordinates across
@@ -70,8 +79,8 @@ Run the server and call `tools/list` for the authoritative, current inventory.
70
79
  | Subpath | Contents |
71
80
  |---|---|
72
81
  | `@bendyline/gezel-mcp` | Server construction helpers |
73
- | `@bendyline/gezel-mcp/lint-contracts` | Tool-contract linting used by the eval harness |
74
- | `@bendyline/gezel-mcp/dist/server.js` | The stdio entry point. Resolved by string from `packages/service/src/chat/manager.ts` — removing this export makes chat sessions silently run with no tools |
82
+ | `@bendyline/gezel-mcp/lint-contracts` | The exact input and output schemas the built-in tools publish, for checking tool contracts |
83
+ | `@bendyline/gezel-mcp/dist/server.js` | The stdio server itself, also installed as the `gezel-mcp` command. The Gezel service launches this file for every chat, so it stays a supported path |
75
84
 
76
85
  ## Stability
77
86
 
package/dist/index.d.ts CHANGED
@@ -92,9 +92,17 @@ declare const SCRIPT_NETWORK_ALLOWED_ENV = "GEZEL_SCRIPT_NETWORK_ALLOWED";
92
92
  * applies RestrictAddressFamilies and rejects an AF_INET socket.
93
93
  */
94
94
  declare function canUseLinuxSystemdDenyNet(): boolean;
95
+ /**
96
+ * Set to `windows-mxc` on the MCP child when the service's own executable
97
+ * probe found a working Windows process container. The service decides once,
98
+ * asynchronously; this child only reads the answer, so registering tools never
99
+ * starts a container on anyone's event loop.
100
+ */
101
+ declare const SCRIPT_DENY_NET_BOUNDARY_ENV = "GEZEL_SCRIPT_DENY_NET_BOUNDARY";
95
102
  /**
96
103
  * The deny-net tools this host cannot offer. Without an enforceable network
97
- * boundary (Windows; Linux without the probed systemd manager) they are
104
+ * boundary (Windows without a probed MXC container; Linux without the probed
105
+ * systemd manager) they are
98
106
  * withheld — unless `networkAllowed`: when the policy already lets gezellen
99
107
  * reach the network, the boundary has nothing left to protect, and the
100
108
  * service runs these scripts without it. Where a boundary exists it is always
@@ -102,7 +110,8 @@ declare function canUseLinuxSystemdDenyNet(): boolean;
102
110
  */
103
111
  declare function unavailableToolsForPlatform(platform: NodeJS.Platform, options?: {
104
112
  linuxSystemdAvailable?: boolean;
113
+ windowsMxcAvailable?: boolean;
105
114
  networkAllowed?: boolean;
106
115
  }): readonly string[];
107
116
 
108
- export { type FileContent, SCRIPT_NETWORK_ALLOWED_ENV, type ValidateCheck, type ValidateResult, canUseLinuxSystemdDenyNet, formatValidateResult, unavailableToolsForPlatform, validateFile };
117
+ export { type FileContent, SCRIPT_DENY_NET_BOUNDARY_ENV, SCRIPT_NETWORK_ALLOWED_ENV, type ValidateCheck, type ValidateResult, canUseLinuxSystemdDenyNet, formatValidateResult, unavailableToolsForPlatform, validateFile };
package/dist/index.js CHANGED
@@ -644,11 +644,15 @@ function canUseLinuxSystemdDenyNet() {
644
644
  linuxSystemdProbe = result.status === 0;
645
645
  return linuxSystemdProbe;
646
646
  }
647
+ var SCRIPT_DENY_NET_BOUNDARY_ENV = "GEZEL_SCRIPT_DENY_NET_BOUNDARY";
647
648
  function unavailableToolsForPlatform(platform, options = {}) {
648
649
  if (platform === "darwin") return [];
649
650
  if (platform === "linux" && (options.linuxSystemdAvailable ?? canUseLinuxSystemdDenyNet())) {
650
651
  return [];
651
652
  }
653
+ if (platform === "win32" && (options.windowsMxcAvailable ?? process.env[SCRIPT_DENY_NET_BOUNDARY_ENV] === "windows-mxc")) {
654
+ return [];
655
+ }
652
656
  if (options.networkAllowed) return [];
653
657
  return DENY_NET_TOOLS;
654
658
  }
@@ -666,6 +670,7 @@ export {
666
670
  LEGACY_TOOL_NAMES,
667
671
  RENAMED_TOOLS,
668
672
  RESERVED_TOOL_NAMES,
673
+ SCRIPT_DENY_NET_BOUNDARY_ENV,
669
674
  SCRIPT_NETWORK_ALLOWED_ENV,
670
675
  TOOL_NAME_TOMBSTONES,
671
676
  TOOL_REGISTRY,