@zswarm/mcp 0.2.1 → 0.3.1
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 -1
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -39,7 +39,9 @@ zswarm({ op: "send", to: "terminal_2", body: "ping" })
|
|
|
39
39
|
Some MCP hosts spawn servers outside your shell and inherit neither PATH nor
|
|
40
40
|
the Zellij environment. Give the interpreter an absolute path and set
|
|
41
41
|
`ZSWARM_SESSION`. Forward `ZELLIJ_PANE_ID` (or set `ZSWARM_FROM`) so send
|
|
42
|
-
labels `[zswarm from=…]` with the sending pane instead of `swarm`.
|
|
42
|
+
labels `[zswarm from=…]` with the sending pane instead of `swarm`. zswarm also
|
|
43
|
+
appends `src=<session>/<pane>`, `host=<host>`, and `via=serve` when the message
|
|
44
|
+
arrived over serve; set `ZSWARM_HOST` to name the machine (`-` hides it).
|
|
43
45
|
`ZSWARM_SSH` or `ZSWARM_SERVE` routes the same tool at a remote crew.
|
|
44
46
|
`ZSWARM_SERVE` may be `host:port` or `ssh://user@host?servePort=9419` (MCP reuses
|
|
45
47
|
a healthy owned tunnel until stdin EOF, then cancels in-flight work and reaps
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@zswarm/mcp",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.3.1",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"description": "zSwarm MCP server — Zellij pane coordination",
|
|
6
6
|
"bin": {
|
|
@@ -8,7 +8,7 @@
|
|
|
8
8
|
},
|
|
9
9
|
"dependencies": {
|
|
10
10
|
"@modelcontextprotocol/sdk": "1.30.0",
|
|
11
|
-
"@zswarm/core": "0.
|
|
11
|
+
"@zswarm/core": "0.4.1"
|
|
12
12
|
},
|
|
13
13
|
"devDependencies": {
|
|
14
14
|
"@types/node": "22.14.1",
|