Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Zsh Tool

by ArkTechNWAversion 0.2.1i★ –iRuns on your computer
Registry nameio.github.ArkTechNWA/zsh-tool

Install

Overview

Description from the maker (original English)

Zsh for Claude Code. PTY mode lets Claude type passwords. NEVERHANG + A.L.A.N.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: ALAN_DB_PATH

You need

  • PyPIPython’s uv installed (for the uvx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "zsh-tool": {
      "command": "uvx",
      "args": [
        "zsh-tool-mcp"
      ],
      "env": {
        "ALAN_DB_PATH": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add zsh-tool --env ALAN_DB_PATH=your-value -- uvx zsh-tool-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "zsh-tool": {
      "command": "uvx",
      "args": [
        "zsh-tool-mcp"
      ],
      "env": {
        "ALAN_DB_PATH": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "zsh-tool": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "zsh-tool-mcp"
      ],
      "env": {
        "ALAN_DB_PATH": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • ALAN_DB_PATH env
    Path to A.L.A.N. SQLite database

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account ArkTechNWA, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 32706 servers in this category
  • Published to the registry more recently than 1% of the other 32706 servers in this category
  • Basic checks equal to or better than 100% of the other 32706 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Zsh Tool safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.1) reached the registry 10 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Kanal Varna — drains, leaks & plumbing (Varna, BG)

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

zsh-tool

Zsh execution tool for Claude Code with full Bash parity, yield-based oversight, PTY mode, NEVERHANG circuit breaker, and A.L.A.N. short-term learning.

Status: Beta (v0.7.2)

Author: Claude + Meldrey

License: MIT

Organization: ArkTechNWA


*Built with obsessive attention to reliability.*


Why?

The #1 reason: If you use zsh, Claude Code's Bash tool causes quotation mismatches and shell confusion. Every debug loop costs tokens. zsh-tool eliminates this instantly and permanently.

The token math: One avoided debug spiral = 30+ seconds saved, hundreds of tokens preserved.

zsh-tool is intelligent shell execution:

Problemzsh-tool Solution
Bash/zsh quotation confusionNative zsh — no shell mismatch, no debug loops
Commands hang foreverYield-based execution — always get control back
No visibility into running commandszsh_poll — incremental output collection
Can't interact with promptsPTY mode + zsh_send — full interactive support
Can't type passwordsPTY mode — let Claude Code type its own passwords
Timeouts cascadeNEVERHANG circuit breaker — fail fast, auto-recover
No memory between callsA.L.A.N. 2.0 — retry detection, streak tracking, proactive insights
Polling wastes tokensIntelligent polling — 2s listen window, adaptive suggestions, duration estimates
Blind kills, no learningKill-aware A.L.A.N. — classifies impatience vs genuine hangs
Retrying with wrong flagsmanopt — auto-surfaces command options on repeated failures
No task managementzsh_tasks, zsh_kill — full control

This is the difference between "run commands" and "intelligent shell integration."


Features

Yield-Based Execution

Commands return after yield_after seconds with partial output if still running:

  • No more hanging — you always get control back
  • Incremental output — collect with zsh_poll
  • Interactive input — send with zsh_send
  • Task management — zsh_kill and zsh_tasks
PTY Mode

Full pseudo-terminal emulation for interactive programs:

# Enable with pty: true

zsh(command="pass insert mypass", pty=true)

See prompts, send input with zsh_send

- Proper handling of interactive prompts
  • Programs that require a TTY
  • Color output and terminal escape sequences
  • Full stdin/stdout/stderr merging
NEVERHANG Circuit Breaker

Prevents hanging commands from blocking sessions:

  • Tracks timeout patterns per command hash
  • Opens circuit after 3 timeouts in rolling 1-hour window
  • Auto-recovers after 5 minutes
  • States: CLOSED (normal) → OPEN (blocking) → HALF_OPEN (testing)
A.L.A.N. 2.0 (As Long As Necessary)

Intelligent short-term learning — *"Maybe you're fuckin' up, maybe you're doing it right."*

  • Retry Detection — warns when you're repeating failed commands
  • Streak Tracking — celebrates success streaks, warns on failure streaks
  • Fuzzy Matching — git push origin feature-1 → git push origin *
  • Proactive Insights — contextual feedback before you run commands
  • Session Memory — 15-minute rolling window tracks recent activity
  • Temporal Decay — exponential decay (24h half-life), auto-prunes
  • SSH Intelligence — separates host connectivity from remote command success
  • Pipeline Segment Tracking — when cat foo | grep -badopts | sort fails, A.L.A.N. knows *which* segment failed
Delta Output with Line Numbers (v0.6.3)

zsh_poll returns only new output since the last poll, prefixed with global line numbers. No more dumping 800 lines every poll call.

801: Installing package foo...

802: Compiling module bar... 803: Done.

FieldWhat it tells you
from_line / to_lineLine range in this delta (e.g., 801-803)
new_bytesByte count of new output since last poll
full_output (param)Pass true to get entire buffer with line numbers

First poll returns all output from line 1. Subsequent polls continue where the last left off. Completed tasks return the final delta, then empty on re-poll.

Intelligent Polling

zsh_poll performs a 2-second listen window before returning. If output arrives within 2s, it comes back immediately. If not, poll metadata tells the agent what's happening:

FieldWhat it tells you
polls_since_outputHow many empty polls in a row
elapsed_since_last_output_sIdle time since last output
alan_estimateA.L.A.N.'s duration prediction based on command history
suggestionAdaptive advice: space out polls, check soon, or consider killing

Suggestions are advisory only — the agent always decides. A 2-minute pip install no longer generates 40 empty round-trips.

Kill-Aware A.L.A.N.

When the agent kills a command, A.L.A.N. records it as a KILLED outcome and classifies *why*:

CategoryMeaningExample
EARLY_KILLKilled well before median completion*"Killed at 30s. Median is 120s. Needs more time."*
LATE_KILLRan way past expected duration*"Killed after 180s. Median is 45s. Something is wrong."*
PATTERN_PROBLEMTemplate gets killed >50% of the time*"This pattern may need a different approach entirely."*

Kill classification compares kill_elapsed / median_duration to distinguish impatience from genuine hangs.

manopt — Man Page Options on Failure

When a command fails repeatedly, A.L.A.N. surfaces its available options:

  • 1st failure — normal feedback, no manopt
  • 2nd failure — triggers async manopt lookup in background (2s timeout)
  • 3rd+ failure — presents cached option table in A.L.A.N. insight

Parsed from local man pages. Cached in SQLite. On by default (ALAN_MANOPT_ENABLED=1).

SSH Tracking

A.L.A.N. treats SSH commands specially, recording two separate observations:

ObservationWhat it tracksExample insight
Host connectivityCan we connect to this host?*"Host 'vps' has 67% connection failure rate"*
Remote commandDoes this command work across hosts?*"Remote command 'git pull' reliable across 3 hosts"*

Exit code classification:

  • 0 — Success (connected AND command succeeded)
  • 255 — Connection failed (SSH couldn't connect)
  • 1-254 — Command failed (connected but remote command failed)

This means when ssh host3 'git pull' fails with exit 255, A.L.A.N. knows the *host* was unreachable—not that git pull is broken.


Tools

ToolPurpose
zshExecute command with yield-based oversight
zsh_pollGet new output (delta) from running task with line numbers
zsh_sendSend input to task's stdin
zsh_killKill a running task
zsh_tasksList all active tasks
zsh_healthOverall health status
zsh_alan_statsA.L.A.N. database statistics
zsh_alan_queryQuery pattern insights for a command
zsh_neverhang_statusCircuit breaker state
zsh_neverhang_resetReset circuit to CLOSED

Installation

From Marketplace (Recommended)

Add the ArkTechNWA marketplace to Claude Code:

ArkTechNWA/claude-plugins

Then install: /plugin install arktechnwa/zsh-tool

That's it. The plugin auto-installs dependencies on first run.

Manual Installation
git clone https://github.com/ArkTechNWA/zsh-tool.git ~/.claude/plugins/zsh-tool

Enable in ~/.claude/settings.json:

{

"enabledPlugins": { "zsh-tool": true } }

The bundled scripts/run-mcp.sh builds the Rust binary on first run and launches the MCP server.

Local Development

For local development/testing, the wrapper script automatically detects when CLAUDE_PLUGIN_ROOT isn't expanded and uses the calculated plugin root directory instead. No configuration changes needed.

Alternatively, create a .mcp.local.json with absolute paths:

{

"mcpServers": { "zsh-tool": { "type": "stdio", "command": "/path/to/zsh-tool/scripts/run-mcp.sh", "env": { "NEVERHANG_TIMEOUT_DEFAULT": "120", "NEVERHANG_TIMEOUT_MAX": "600" } } } }

The ALAN_DB_PATH will be automatically set to {plugin_root}/data/alan.db if not explicitly provided.

Requirements: Rust toolchain (cargo) and zsh must be installed.


Architecture

zsh-tool/

├── .claude-plugin/ │ ├── plugin.json │ └── CLAUDE.md ├── .mcp.json ├── zsh-tool-rs/ │ ├── Cargo.toml │ └── src/ │ ├── main.rs # CLI entry point │ ├── lib.rs # Module exports │ ├── executor.rs # Pipe/PTY command execution │ ├── config.rs # User config (~/.config/zsh-tool/) │ ├── circuit.rs # NEVERHANG circuit breaker │ ├── meta.rs # Task metadata (exit code, pipestatus) │ ├── alan/ # A.L.A.N. 2.0 learning engine │ │ ├── mod.rs # Recording + insights │ │ ├── hash.rs # Fuzzy command hashing │ │ ├── insights.rs # Proactive feedback │ │ ├── manopt.rs # Man-page option parsing │ │ ├── ssh.rs # SSH host/command tracking │ │ ├── streak.rs # Success/failure streaks │ │ ├── pipeline.rs # Pipeline segment tracking │ │ ├── prune.rs # Temporal decay + pruning │ │ └── stats.rs # Database statistics │ └── serve/ # MCP JSON-RPC server │ ├── mod.rs # Request dispatch + tool handlers │ ├── format.rs # Rich output formatting │ ├── protocol.rs # JSON-RPC framing │ └── tools.rs # Tool schema definitions ├── scripts/ │ └── run-mcp.sh # Build + launch wrapper ├── data/ │ └── alan.db # A.L.A.N. SQLite database └── README.md


Configuration

Environment variables (set in .mcp.json):

  • ALAN_DB_PATH — A.L.A.N. database location
  • NEVERHANG_TIMEOUT_DEFAULT — Default timeout (120s)
  • NEVERHANG_TIMEOUT_MAX — Maximum timeout (600s)
  • ALAN_MANOPT_ENABLED — Enable man-page option hints on failure (default: 1)
  • ALAN_MANOPT_TIMEOUT — Max seconds to wait for manopt parsing (default: 2.0)
  • ALAN_MANOPT_FAIL_TRIGGER — Fail count to trigger async lookup (default: 2)
  • ALAN_MANOPT_FAIL_PRESENT — Fail count to present cached options (default: 3)
Disabling Bash (Optional)

To use zsh as the only shell, add to ~/.claude/settings.json:

{

"permissions": { "deny": ["Bash"] } }


Changelog

0.7.2

User-Visible Output — *Tell the model to show its work*

  • Fix: MCP tool results are invisible to users in Claude Code (platform limitation). Tool descriptions now instruct the model to relay command output verbatim in its response text.
  • This is a workaround for Claude Code not rendering MCP tool result blocks to users.
0.7.1

Stale Binary Fix — *Actually deliver the new format*

  • Fix: run-mcp.sh now runs cargo clean -p before rebuild when source changes, preventing Cargo's incremental build from serving a stale binary
  • Fix: Rebuild trigger now also watches Cargo.toml (version bumps were invisible to the old find -newer check)
0.7.0

**Rich

Only the beginning is shown; read the rest in the repo

Ask PopNx