mcp-debugger 0.1.0__tar.gz

mcp_debugger-0.1.0/.gitignore

@@ -0,0 +1,18 @@
+pycache/
+*.pyc
+.venv/
+*.db
+*.sqlite
+dist/
+build/
+*.egg-info/
+.pytest_cache/
+.ruff_cache/
+.mypy_cache/
+.coverage
+.coverage.*
+htmlcov/
+__pycache__/
+*.log
+*.tmp
+*.pid

mcp_debugger-0.1.0/CHANGELOG.md

@@ -0,0 +1,106 @@
+# Changelog
+
+All notable changes to `mcp-debugger` are documented here.
+
+Format follows [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
+Versioning follows [Semantic Versioning](https://semver.org/).
+
+---
+
+## [0.1.0] — 2026-06-29
+
+Initial release. Full-featured MCP session debugger with proxy recording, inspection, validation, replay, export, and analytics.
+
+### Added
+
+#### Core Proxy
+- `proxy` command: transparent asyncio stdio proxy that records all MCP JSON-RPC messages to SQLite
+- Session naming via `--name` / `-n`
+- Verbose logging via `--verbose` / `-v`
+- Graceful shutdown on `Ctrl+C` / EOF with guaranteed database cleanup (`try...finally`)
+- 10 MB `StreamReader` limit to handle large MCP payloads without crashing
+
+#### Session Management
+- `list` command: browse historical sessions with status, message count, and timestamps
+- Filter by status (`running`, `completed`, `error`) and limit via `--limit`
+- JSON output mode (`--json`) for scripting and automation
+
+#### Inspection
+- `inspect` command: syntax-highlighted, formatted message browser using Rich
+- Filter by method name (`--method`), direction (`--direction`), substring (`--search`)
+- Pagination via `--limit` and `--offset`
+- Output to file via `--output`
+
+#### Protocol Validation
+- `validate` command: rule-based MCP protocol compliance checker
+- Live server validation (`--server`) and recorded session validation (`SESSION_ID`)
+- Rules: handshake order, method name validity, tool schema format (JSON Schema Draft-07), error code validity
+- JSON output for CI/CD integration (`--json`)
+- Exit code `0` (pass) / `1` (critical failure)
+
+#### Analytics
+- `stats` command: comprehensive session dashboard — message counts, latency (p50/p95/p99), tool usage, error rates
+- `compare` command: delta report between two sessions — latency regression, error rate changes, new/missing tools
+- `errors` command: classified error list with category filter (`protocol`, `tool_execution`, `timeout`, `connection`, `unknown`)
+- `tools` command: discovered tool list with call counts; full schema view via `--detail`
+
+#### Replay & Regression Testing
+- `replay` command: re-sends recorded client messages to a target server, compares responses with inline diffs
+- Filter by method (`--filter-method`), limit messages (`--max-messages`), custom timeout (`--timeout`)
+- JSON report output (`--json`) and file output (`--output`)
+- Save replay results to database (`--save`)
+- Exit codes: `0` (all match) / `1` (mismatches) / `2` (server crash)
+
+#### Export
+- `export` command with three formats:
+  - **JSON** — structured machine-readable dump
+  - **Markdown** — human-readable report with optional raw message blocks (`--include-raw`)
+  - **OTLP** — OpenTelemetry traces sent to a Jaeger/Grafana/DataDog collector
+- Per-format options: `--output`, `--pretty`, `--endpoint`, `--insecure`, `--service-name`, `--limit`
+- OTLP requires optional install: `pip install "mcp-debugger[export]"`
+
+#### Configuration
+- `config` command with subcommands: `init`, `get`, `set`, `unset`, `list`, `reset`
+- TOML config file at `~/.mcp-debugger/config.toml` (Linux/macOS) or `%APPDATA%\mcp-debugger\config.toml` (Windows)
+- Dot-notation keys: `replay.timeout`, `aliases.fs`, `export.default_format`, etc.
+- Server aliases for short-hand replay and proxy usage
+- Graceful fallback to defaults on missing or corrupt config file
+- CLI flag always overrides config file value
+
+#### Environment Diagnostics
+- `doctor` command: checks Python version, SQLite version, database directory, file permissions, schema version, Node.js, npx, git, PATH, config validity
+- Exit code `0` (all good) / `1` (critical failure)
+
+#### Storage
+- SQLite database with 6 tables: `sessions`, `messages`, `tools`, `errors`, `replays`, `replay_messages`
+- Async access via `aiosqlite` — non-blocking, event-loop friendly
+- Schema version tracking via `PRAGMA user_version = 1`
+- WAL mode for safe concurrent access
+
+#### Test Suite
+- 247 tests across unit, integration, property-based, and stress categories
+- **96.54% line coverage**
+- Tests run on Python 3.11 and 3.12, Ubuntu and Windows via GitHub Actions
+- Property-based tests using `hypothesis` for schema round-trips and diff symmetry
+- Stress tests: 10k-message sessions, large payload (50 MB), concurrent proxies
+
+#### Documentation
+- `README.md` with badges, feature overview, quickstart, and links
+- `docs/commands.md` — full command reference with all options and examples
+- `docs/architecture.md` — component overview, data flow, design decisions
+- `docs/tutorials.md` — 5 step-by-step workflow guides
+- `docs/faq.md` — 15+ Q&As covering installation, usage, and troubleshooting
+- `docs/config.md` — full configuration key reference
+- `docs/contributing.md` — development setup, test structure, CI details
+- `CONTRIBUTING.md` — contributor quick-start
+
+---
+
+## Roadmap
+
+These features are planned for future releases:
+
+- **v0.2.0** — PyPI publish, `pip install mcp-debugger` from the public index
+- **v0.3.0** — Web UI for browsing sessions in a browser (optional, via `mcp-debugger serve`)
+- **v0.4.0** — Diff ignore paths configuration for non-deterministic replay fields
+- **v0.5.0** — MCP schema version tracking and automatic upgrade migrations

mcp_debugger-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,75 @@
+# Contributing Guidelines
+
+Thank you for your interest in contributing to **MCP Debugger**! This document outlines the development workflow, code style standards, and tooling instructions.
+
+---
+
+## 1. Development Environment Setup
+
+This project uses `uv` for package management and Python 3.11+.
+
+### Step 1: Clone the Repository
+```bash
+git clone https://github.com/sushant-mutnale/mcp-debugger.git
+cd mcp-debugger
+```
+
+### Step 2: Set Up Virtual Environment & Dependencies
+Initialize and activate your environment, then install in editable mode with development dependencies:
+```bash
+# Using uv (recommended)
+uv venv
+source .venv/bin/activate  # Or .venv\Scripts\activate on Windows
+uv pip install -e .[dev]
+```
+
+### Step 3: Run Verification Commands
+Verify that the CLI package is installed correctly and tests run green:
+```bash
+mcp-debugger version
+pytest
+```
+
+---
+
+## 2. Code Quality & Standards
+
+We enforce strict linting, formatting, and static analysis checks to maintain code safety:
+
+- **Style & Formatter**: We use `ruff` for code linting and formatting. Run these before pushing changes:
+  ```bash
+  ruff check src/ tests/
+  ruff format src/ tests/
+  ```
+- **Type Safety**: Code must pass strict `mypy` audits:
+  ```bash
+  mypy src/ tests/
+  ```
+- **Logging**:
+  - Always log internal debug/info data to `sys.stderr` or file-handlers.
+  - Do not use print statements or log to `sys.stdout` in the proxy logic, as this corrupts standard I/O communication between client and server.
+- **Error Handling**:
+  - Avoid bare `except:` statements.
+  - Fail loudly on critical startup bugs (like failing to launch the subprocess) and retry transient errors (like sqlite lock errors).
+
+---
+
+## 3. Git & Pull Request Workflow
+
+1. Create a descriptive feature branch from `main`:
+   ```bash
+   git checkout -b feature/your-feature-name
+   ```
+2. Make your edits and include comprehensive unit/integration tests under `tests/`.
+3. Verify that all linting, formatting, type checking, and tests pass successfully:
+   ```bash
+   ruff check src/ tests/
+   ruff format src/ tests/ --check
+   mypy src/ tests/
+   pytest
+   ```
+4. Commit your changes with clear, imperative-style commit messages:
+   ```bash
+   git commit -m "feat: add schema validator for initialize method"
+   ```
+5. Push to your branch and open a Pull Request.

mcp_debugger-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Sushant Mutnale
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

mcp_debugger-0.1.0/PKG-INFO

@@ -0,0 +1,207 @@
+Metadata-Version: 2.4
+Name: mcp-debugger
+Version: 0.1.0
+Summary: Transparent proxy to debug, record, validate, and replay MCP (Model Context Protocol) sessions
+Project-URL: Homepage, https://github.com/sushant-mutnale/mcp-debugger
+Project-URL: Repository, https://github.com/sushant-mutnale/mcp-debugger
+Project-URL: Documentation, https://github.com/sushant-mutnale/mcp-debugger#readme
+Project-URL: Issues, https://github.com/sushant-mutnale/mcp-debugger/issues
+Author-email: Sushant Mutnale <sushant.mutnale@gmail.com>
+Maintainer-email: Sushant Mutnale <sushant.mutnale@gmail.com>
+License: MIT
+License-File: LICENSE
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: MacOS :: MacOS X
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Debuggers
+Classifier: Topic :: Software Development :: Testing
+Classifier: Topic :: System :: Monitoring
+Requires-Python: >=3.11
+Requires-Dist: aiosqlite>=0.19.0
+Requires-Dist: jsonschema>=4.0.0
+Requires-Dist: pydantic>=2.5.0
+Requires-Dist: rich>=13.7.0
+Requires-Dist: tomli>=2.0.1; python_version < '3.11'
+Requires-Dist: typer>=0.9.0
+Provides-Extra: dev
+Requires-Dist: hypothesis>=6.0.0; extra == 'dev'
+Requires-Dist: mypy>=1.7.0; extra == 'dev'
+Requires-Dist: pre-commit>=3.0.0; extra == 'dev'
+Requires-Dist: pytest-asyncio>=0.21.0; extra == 'dev'
+Requires-Dist: pytest-benchmark>=4.0.0; extra == 'dev'
+Requires-Dist: pytest-cov>=4.0.0; extra == 'dev'
+Requires-Dist: pytest-mock>=3.12.0; extra == 'dev'
+Requires-Dist: pytest>=8.0.0; extra == 'dev'
+Requires-Dist: ruff>=0.1.0; extra == 'dev'
+Provides-Extra: otlp
+Requires-Dist: opentelemetry-api>=1.20.0; extra == 'otlp'
+Requires-Dist: opentelemetry-exporter-otlp>=1.20.0; extra == 'otlp'
+Requires-Dist: opentelemetry-sdk>=1.20.0; extra == 'otlp'
+Description-Content-Type: text/markdown
+
+# mcp-debugger
+
+> Transparent proxy to **debug, record, validate, and replay** MCP (Model Context Protocol) sessions.
+
+[![PyPI version](https://img.shields.io/pypi/v/mcp-debugger.svg)](https://pypi.org/project/mcp-debugger/)
+[![CI](https://github.com/sushant-mutnale/mcp-debugger/actions/workflows/ci.yml/badge.svg)](https://github.com/sushant-mutnale/mcp-debugger/actions/workflows/ci.yml)
+[![Python versions](https://img.shields.io/pypi/pyversions/mcp-debugger.svg)](https://pypi.org/project/mcp-debugger/)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+[![Coverage](https://img.shields.io/badge/coverage-96%25-brightgreen)](https://github.com/sushant-mutnale/mcp-debugger/actions)
+
+---
+
+## ✨ Features
+
+| Feature | What it does |
+|---|---|
+| 🔍 **Record** | Capture every JSON-RPC message between an MCP client and server |
+| 📋 **Inspect** | Browse messages with syntax-highlighted, formatted terminal output |
+| ✅ **Validate** | Check MCP protocol compliance — handshake order, method names, schemas |
+| 🔄 **Replay** | Regression-test server changes by replaying recorded sessions |
+| 📊 **Stats** | Visualise tool usage, latency trends, and error rates |
+| 🔀 **Compare** | Delta reports between two sessions (latency, errors, tool calls) |
+| 📤 **Export** | JSON, Markdown, or OpenTelemetry (OTLP) traces |
+| ⚙️ **Config** | Persistent user preferences — aliases, timeouts, defaults |
+| 🩺 **Doctor** | Environment diagnostics — Python version, SQLite, Node.js, paths |
+| 🚀 **Local-first** | No cloud, no signup — all data stays on your machine |
+
+---
+
+## 📦 Installation
+
+```bash
+pip install mcp-debugger
+```
+
+With optional OpenTelemetry (OTLP) export support:
+
+```bash
+pip install "mcp-debugger[otlp]"
+```
+
+**Requirements:** Python 3.11+, Node.js (for `npx`-based MCP servers)
+
+---
+
+## 🚀 Quickstart
+
+### 1. Record a session
+
+```bash
+mcp-debugger proxy \
+  --server "npx -y @modelcontextprotocol/server-filesystem /tmp" \
+  --name "my-first-session"
+```
+
+Interact with your MCP client (e.g. Claude Desktop). Press `Ctrl+C` to stop.
+
+### 2. List recorded sessions
+
+```bash
+mcp-debugger list
+```
+
+### 3. Inspect a session
+
+```bash
+mcp-debugger inspect 1
+```
+
+### 4. Validate protocol compliance
+
+```bash
+mcp-debugger validate --server "npx -y @modelcontextprotocol/server-filesystem /tmp"
+```
+
+### 5. Replay against a new server version
+
+```bash
+mcp-debugger replay 1 --server "npx -y @modelcontextprotocol/server-filesystem /tmp"
+```
+
+### 6. Export to Markdown
+
+```bash
+mcp-debugger export 1 --format markdown --output session-report.md
+```
+
+---
+
+## 🔧 Use with Claude Desktop
+
+Edit your Claude Desktop config (`~/Library/Application Support/Claude/claude_desktop_config.json` on macOS, `%APPDATA%\Claude\claude_desktop_config.json` on Windows):
+
+```json
+{
+  "mcpServers": {
+    "my-filesystem": {
+      "command": "mcp-debugger",
+      "args": [
+        "proxy",
+        "--server",
+        "npx -y @modelcontextprotocol/server-filesystem /path/to/dir",
+        "--name",
+        "claude-session"
+      ]
+    }
+  }
+}
+```
+
+Every message between Claude and your server is now recorded transparently.
+
+---
+
+## 📖 Documentation
+
+| Document | Description |
+|---|---|
+| [Command Reference](docs/commands.md) | Every CLI command with all options and examples |
+| [Architecture](docs/architecture.md) | How it works — components, data flow, sequence diagrams |
+| [Tutorials](docs/tutorials.md) | Step-by-step workflows for common use cases |
+| [Configuration](docs/config.md) | All config keys, defaults, and examples |
+| [FAQ](docs/faq.md) | Common questions and troubleshooting |
+| [Contributing](docs/contributing.md) | Development setup, test structure, PR process |
+| [Changelog](CHANGELOG.md) | Version history |
+
+---
+
+## 🧪 Development Setup
+
+```bash
+git clone https://github.com/sushant-mutnale/mcp-debugger.git
+cd mcp-debugger
+python -m venv .venv
+source .venv/bin/activate      # Linux/macOS
+# or: .venv\Scripts\activate   # Windows
+pip install -e ".[dev]"
+
+# Run all tests
+pytest
+
+# With coverage
+pytest --cov=mcp_debugger --cov-report=term-missing
+
+# Lint and type-check
+ruff check .
+mypy src/mcp_debugger --ignore-missing-imports
+```
+
+---
+
+## 🤝 Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for setup instructions, coding style, and pull request process.
+
+---
+
+## 📄 License
+
+MIT © [Sushant Mutnale](https://github.com/sushant-mutnale)

mcp_debugger-0.1.0/README.md

@@ -0,0 +1,160 @@
+# mcp-debugger
+
+> Transparent proxy to **debug, record, validate, and replay** MCP (Model Context Protocol) sessions.
+
+[![PyPI version](https://img.shields.io/pypi/v/mcp-debugger.svg)](https://pypi.org/project/mcp-debugger/)
+[![CI](https://github.com/sushant-mutnale/mcp-debugger/actions/workflows/ci.yml/badge.svg)](https://github.com/sushant-mutnale/mcp-debugger/actions/workflows/ci.yml)
+[![Python versions](https://img.shields.io/pypi/pyversions/mcp-debugger.svg)](https://pypi.org/project/mcp-debugger/)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+[![Coverage](https://img.shields.io/badge/coverage-96%25-brightgreen)](https://github.com/sushant-mutnale/mcp-debugger/actions)
+
+---
+
+## ✨ Features
+
+| Feature | What it does |
+|---|---|
+| 🔍 **Record** | Capture every JSON-RPC message between an MCP client and server |
+| 📋 **Inspect** | Browse messages with syntax-highlighted, formatted terminal output |
+| ✅ **Validate** | Check MCP protocol compliance — handshake order, method names, schemas |
+| 🔄 **Replay** | Regression-test server changes by replaying recorded sessions |
+| 📊 **Stats** | Visualise tool usage, latency trends, and error rates |
+| 🔀 **Compare** | Delta reports between two sessions (latency, errors, tool calls) |
+| 📤 **Export** | JSON, Markdown, or OpenTelemetry (OTLP) traces |
+| ⚙️ **Config** | Persistent user preferences — aliases, timeouts, defaults |
+| 🩺 **Doctor** | Environment diagnostics — Python version, SQLite, Node.js, paths |
+| 🚀 **Local-first** | No cloud, no signup — all data stays on your machine |
+
+---
+
+## 📦 Installation
+
+```bash
+pip install mcp-debugger
+```
+
+With optional OpenTelemetry (OTLP) export support:
+
+```bash
+pip install "mcp-debugger[otlp]"
+```
+
+**Requirements:** Python 3.11+, Node.js (for `npx`-based MCP servers)
+
+---
+
+## 🚀 Quickstart
+
+### 1. Record a session
+
+```bash
+mcp-debugger proxy \
+  --server "npx -y @modelcontextprotocol/server-filesystem /tmp" \
+  --name "my-first-session"
+```
+
+Interact with your MCP client (e.g. Claude Desktop). Press `Ctrl+C` to stop.
+
+### 2. List recorded sessions
+
+```bash
+mcp-debugger list
+```
+
+### 3. Inspect a session
+
+```bash
+mcp-debugger inspect 1
+```
+
+### 4. Validate protocol compliance
+
+```bash
+mcp-debugger validate --server "npx -y @modelcontextprotocol/server-filesystem /tmp"
+```
+
+### 5. Replay against a new server version
+
+```bash
+mcp-debugger replay 1 --server "npx -y @modelcontextprotocol/server-filesystem /tmp"
+```
+
+### 6. Export to Markdown
+
+```bash
+mcp-debugger export 1 --format markdown --output session-report.md
+```
+
+---
+
+## 🔧 Use with Claude Desktop
+
+Edit your Claude Desktop config (`~/Library/Application Support/Claude/claude_desktop_config.json` on macOS, `%APPDATA%\Claude\claude_desktop_config.json` on Windows):
+
+```json
+{
+  "mcpServers": {
+    "my-filesystem": {
+      "command": "mcp-debugger",
+      "args": [
+        "proxy",
+        "--server",
+        "npx -y @modelcontextprotocol/server-filesystem /path/to/dir",
+        "--name",
+        "claude-session"
+      ]
+    }
+  }
+}
+```
+
+Every message between Claude and your server is now recorded transparently.
+
+---
+
+## 📖 Documentation
+
+| Document | Description |
+|---|---|
+| [Command Reference](docs/commands.md) | Every CLI command with all options and examples |
+| [Architecture](docs/architecture.md) | How it works — components, data flow, sequence diagrams |
+| [Tutorials](docs/tutorials.md) | Step-by-step workflows for common use cases |
+| [Configuration](docs/config.md) | All config keys, defaults, and examples |
+| [FAQ](docs/faq.md) | Common questions and troubleshooting |
+| [Contributing](docs/contributing.md) | Development setup, test structure, PR process |
+| [Changelog](CHANGELOG.md) | Version history |
+
+---
+
+## 🧪 Development Setup
+
+```bash
+git clone https://github.com/sushant-mutnale/mcp-debugger.git
+cd mcp-debugger
+python -m venv .venv
+source .venv/bin/activate      # Linux/macOS
+# or: .venv\Scripts\activate   # Windows
+pip install -e ".[dev]"
+
+# Run all tests
+pytest
+
+# With coverage
+pytest --cov=mcp_debugger --cov-report=term-missing
+
+# Lint and type-check
+ruff check .
+mypy src/mcp_debugger --ignore-missing-imports
+```
+
+---
+
+## 🤝 Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for setup instructions, coding style, and pull request process.
+
+---
+
+## 📄 License
+
+MIT © [Sushant Mutnale](https://github.com/sushant-mutnale)

mcp_debugger-0.1.0/docs/00-project-charter.md

@@ -0,0 +1,22 @@
+# Project Charter
+
+## Problem Statement
+Currently, Model Context Protocol (MCP) developers debug stdio-based JSON-RPC communication using basic `print()` statements and manual log reading. There is a lack of specialized tooling to record, replay, or validate MCP session traffic, leading to slow debugging cycles and difficult regression testing.
+
+## Solution
+`mcp-debugger` is a Python-native CLI tool that acts as a transparent man-in-the-middle proxy. It captures all JSON-RPC traffic between MCP clients and servers, stores session data locally in an SQLite database, and offers rich CLI command utilities (`inspect`, `validate`, `replay`) to troubleshoot and audit integrations.
+
+## Target Users
+- **MCP Server Developers**: Need to check if their server responds correctly to client queries and complies with the MCP specification.
+- **Agent Framework Maintainers**: Integrate framework libraries (e.g. LangChain, Cursor, OpenAI Agents SDK) with various MCP servers and need visibility into JSON-RPC traffic.
+- **DevOps/QA Engineers**: Testing and validating MCP server compliance in CI/CD pipelines.
+
+## Success Criteria (Measurable)
+- Achieve **500+ GitHub stars** within 3 months of public release.
+- Adoption by **5+ public MCP servers** in their CI/CD compliance workflows.
+- **Zero configuration** needed for basic usage (i.e. simple `pip install` and run commands immediately).
+
+## Non-Goals (Phase 1)
+- **No Cloud Dashboard**: All operations are 100% local-first to ensure developer data privacy.
+- **No Multi-user Support**: Designed as a single-user local command-line utility.
+- **No Native Windows Support**: The initial target OS is Linux/macOS (Phase 1 stdio handling may rely on POSIX-compatible async I/O behaviors, although the CLI commands themselves can run on Windows with appropriate workarounds).