smart-terminal-mcp 1.2.6 → 1.2.7

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 +8 -8
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -1,8 +1,8 @@
1
1
  # smart-terminal-mcp
2
2
 
3
- A PTY-based MCP server with strong Windows support that gives AI agents (Claude, Cursor, etc.) interactive terminal access via pseudo-terminals ([node-pty](https://github.com/microsoft/node-pty)).
3
+ A PTY-based MCP server with strong Windows support that gives AI agents (Claude, Cursor, etc.) persistent, interactive shell 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, incremental terminal reads, and PTY-backed terminal behavior.
5
+ Unlike simple `exec`-based approaches, this keeps PTY-backed shell sessions alive across steps, with bidirectional communication for interactive CLI tools, incremental reads, and session state that carries forward.
6
6
 
7
7
  ## Why use this instead of your AI client's built-in terminal?
8
8
 
@@ -13,7 +13,7 @@ This MCP is most useful when you want:
13
13
  - **Portable workflow across clients** -- The same terminal tools and habits work across Claude Code, Cursor, Trae, Antigravity, and other MCP-capable clients.
14
14
  - **Reusable prompts and tooling** -- Workflows built around tools like `terminal_wait`, `terminal_retry`, `terminal_run_paged`, and `terminal_get_history` are easier to reuse across teams and clients, with less lock-in to one client's terminal behavior.
15
15
  - **Persistent terminal state** -- Keep the same shell session alive across steps, including the current folder, environment, and running processes.
16
- - **Better interactive behavior** -- Handle prompts, REPLs, dev servers, Ctrl+C, arrow keys, and other real terminal interactions.
16
+ - **Better interactive behavior** -- Handle prompts, REPLs, dev servers, Ctrl+C, arrow keys, and other interactive terminal behavior.
17
17
  - **More control over large output** -- Truncate, page, diff, retry, wait for patterns, or fetch history instead of dumping everything at once.
18
18
  - **More predictable automation** -- Use deterministic completion markers instead of guessing when a command is done.
19
19
 
@@ -21,18 +21,18 @@ If your AI client already gives you a stable, stateful, interactive terminal wit
21
21
 
22
22
  ## Features
23
23
 
24
- Think of this as a **controlled keyboard + screen for AI**. It can open a real terminal, type commands, read the results, and keep working in the same session.
24
+ Think of this as a **controlled keyboard + terminal for AI**. It opens a persistent PTY-backed shell session, sends commands and keystrokes, reads output, and keeps working in the same session.
25
25
 
26
26
  ### Core terminal features
27
27
 
28
- - **Interactive terminal sessions** -- Keeps a real terminal open so the AI can type, read output, and continue where it left off.
28
+ - **Interactive terminal sessions** -- Keeps a persistent PTY-backed shell session open so the AI can send input, read output, and pick up where it left off.
29
29
  - **Deterministic command completion** -- `terminal_exec` uses unique markers so it can tell when a command has finished.
30
30
  - **Clean output** -- Pre-command markers help keep returned output readable, even when shells echo commands or expand aliases.
31
31
  - **Working directory tracking** -- `terminal_exec` reports the current folder after each command.
32
32
 
33
33
  ### Long output and long-running commands
34
34
 
35
- - **Interactive reads and writes** -- `terminal_write` + `terminal_read` support prompts, REPLs, and other interactive programs.
35
+ - **Interactive reads and writes** -- `terminal_write` + `terminal_read` support prompts, REPLs, and other interactive programs without leaving the current session.
36
36
  - **Pattern waiting** -- `terminal_wait` can pause until specific text appears, such as `server listening on port`.
37
37
  - **Retry helper** -- `terminal_retry` can re-run flaky commands with bounded backoff and optional output matching.
38
38
  - **Best-effort progress notifications** -- Long `terminal_exec` / `terminal_wait` calls can emit `notifications/progress` when the client provides a progress token.
@@ -42,10 +42,10 @@ Think of this as a **controlled keyboard + screen for AI**. It can open a real t
42
42
 
43
43
  ### Safety and usability
44
44
 
45
- - **Safer one-shot commands** -- `terminal_run` executes real binaries with `cmd + args` and `shell=false`.
45
+ - **Safer one-shot commands** -- `terminal_run` executes binaries directly with `cmd + args` and `shell=false` for more predictable automation.
46
46
  - **Structured parsers** -- Some supported read-only commands can return both raw text and parsed output.
47
47
  - **Blocking mitigations** -- Disables pagers (`GIT_PAGER=cat`, `PAGER=cat`), suppresses PowerShell progress output, and sets UTF-8 for `cmd.exe` on Windows.
48
- - **Special key support** -- Can send Ctrl+C, Tab, arrow keys, and similar keys without manually building escape codes.
48
+ - **Special key support** -- Can send Ctrl+C, Tab, arrow keys, and similar keys without manually constructing escape sequences.
49
49
  - **Session management** -- Supports named sessions, idle cleanup, and up to 10 concurrent sessions.
50
50
  - **Shell auto-detection** -- Windows: `pwsh.exe` > `powershell.exe` > `cmd.exe`. Linux/macOS: `$SHELL` > `bash` > `sh`.
51
51
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "smart-terminal-mcp",
3
- "version": "1.2.6",
3
+ "version": "1.2.7",
4
4
  "description": "MCP PTY server providing AI agents with real interactive terminal access",
5
5
  "type": "module",
6
6
  "main": "src/index.js",