smart-terminal-mcp 1.2.0 → 1.2.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.
Files changed (2) hide show
  1. package/README.md +6 -4
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -2,7 +2,7 @@
2
2
 
3
3
  A Windows-native MCP server that gives AI agents (Claude, Cursor, etc.) real interactive terminal access via pseudo-terminals ([node-pty](https://github.com/microsoft/node-pty)).
4
4
 
5
- Unlike simple `exec`-based approaches, this provides full PTY sessions with bidirectional communication, enabling interactive CLI tools, real-time output streaming, and proper terminal emulation.
5
+ Unlike simple `exec`-based approaches, this provides full PTY sessions with bidirectional communication, enabling interactive CLI tools, incremental terminal reads, and proper terminal emulation.
6
6
 
7
7
  ## Features
8
8
 
@@ -20,9 +20,11 @@ Unlike simple `exec`-based approaches, this provides full PTY sessions with bidi
20
20
  - **Output truncation** -- Large outputs are automatically truncated to head + tail
21
21
  - **Session management** -- Named sessions, TTL auto-cleanup, max 10 concurrent sessions
22
22
  - **Anti-blocking** -- Disables pagers (`GIT_PAGER=cat`), progress bars, and sets UTF-8 on Windows
23
- - **Progress notifications** -- Real-time MCP progress updates during long-running commands
23
+ - **Best-effort progress notifications** -- Emits MCP `notifications/progress` for long-running `terminal_exec` / `terminal_wait` calls when the client provides a progress token and surfaces those notifications
24
24
  - **Shell auto-detection** -- Windows: `pwsh.exe` > `powershell.exe` > `cmd.exe`. Linux/macOS: `$SHELL` or `bash`
25
25
 
26
+ Progress notifications are not the same as full stdout streaming: they currently send periodic status updates for `terminal_exec` and `terminal_wait`, typically based on elapsed time and the latest output line. Whether you actually see them depends on your MCP client.
27
+
26
28
  ## Requirements
27
29
 
28
30
  - **Node.js** >= 18
@@ -116,7 +118,7 @@ Start a new interactive terminal session.
116
118
 
117
119
  ### `terminal_exec`
118
120
 
119
- Execute a command with deterministic completion detection.
121
+ Execute a command with deterministic completion detection. If the MCP client sends a `progressToken`, long-running calls may also emit best-effort `notifications/progress` updates.
120
122
 
121
123
  | Param | Type | Default | Description |
122
124
  |-------|------|---------|-------------|
@@ -211,7 +213,7 @@ Send a named special key.
211
213
 
212
214
  ### `terminal_wait`
213
215
 
214
- Wait for a specific pattern in the output stream.
216
+ Wait for a specific pattern in the output stream. If the MCP client sends a `progressToken`, long-running waits may also emit best-effort `notifications/progress` updates.
215
217
 
216
218
  | Param | Type | Default | Description |
217
219
  |-------|------|---------|-------------|
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "smart-terminal-mcp",
3
- "version": "1.2.0",
3
+ "version": "1.2.1",
4
4
  "description": "MCP PTY server providing AI agents with real interactive terminal access",
5
5
  "type": "module",
6
6
  "main": "src/index.js",