memshell-party-cli 0.2.0 → 0.2.2

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "memshell-party-cli",
3
- "version": "0.2.0",
3
+ "version": "0.2.2",
4
4
  "description": "Command-line client and MCP server for MemShellParty (party.mem.mk) — generate Java memory shells and probes from the terminal.",
5
5
  "keywords": [
6
6
  "memshell",
@@ -19,6 +19,7 @@
19
19
  "dist",
20
20
  "skills",
21
21
  "README.md",
22
+ "README.zh-CN.md",
22
23
  "LICENSE"
23
24
  ],
24
25
  "engines": {
package/skills/SKILL.md CHANGED
@@ -18,7 +18,7 @@ Two equivalent interfaces — pick whichever is available:
18
18
  - **CLI**: `memparty <command> [flags]` (install: `npm install -g memshell-party-cli`, or `npx memshell-party-cli`).
19
19
  - **MCP tools** (if the `memshell-party` MCP server is connected): `list_servers`, `list_config`,
20
20
  `list_packers`, `list_command_configs`, `generate_memshell`, `generate_probe`, `parse_classname`,
21
- `server_version`.
21
+ `server_version`, `connect_test`.
22
22
 
23
23
  The CLI is the source of truth for examples below; MCP tool args mirror the CLI flags
24
24
  (`-s/--server` → `server`, `-t/--tool` → `shellTool`, `-y/--type` → `shellType`, `-p/--packer` → `packer`).
@@ -159,6 +159,9 @@ memparty connect -u <shell-url> -t godzilla --pass pass --key key \
159
159
  --header-name User-Agent --header-value <headerValue-from-gen-json>
160
160
  ```
161
161
 
162
+ Over MCP the same check is the `connect_test` tool (`url`, `tool`, `pass`/`key`,
163
+ `headerName`/`headerValue`, `suo5Mode`).
164
+
162
165
  ## Gotchas
163
166
 
164
167
  - **Jakarta vs javax.** Tomcat 10+ / Spring Boot 3 → `Jakarta*` shell types. Tomcat 9- / Spring Boot 2