docs(install): per-OS command blocks for Windows / Linux / macOS

The only per-OS difference in the install flow is how environment
variables are set (export vs $env: vs set) and the shell's
line-continuation character. Add ready-to-copy Linux/macOS, PowerShell,
and Command Prompt blocks for the two quick-starts and the docker run,
fronted by a one-time translation table so the later export examples
don't need triplicating. README's docker block gets a one-line pointer
to the per-OS install-guide blocks.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0122yLZLJ8t4W43sdN6BmTZc

Author: claude

CHANGELOG.md

@@ -21,6 +21,14 @@ adheres to [Semantic Versioning](https://semver.org/).
 
 ### Changed
 
+- **Install docs: per-OS commands + `docker run --name mcpg`.** The
+  installation guide's quick-start and Docker sections now carry ready-to-copy
+  **Linux/macOS, Windows PowerShell, and Windows Command Prompt** blocks (the
+  only per-OS difference is how environment variables are set and the shell's
+  line-continuation character), fronted by a one-time translation table. The
+  `docker run` examples gain `--name mcpg` so the container is addressable by
+  name.
+
 - **De-vendored the SQL-safety kernel (roadmap 18.1).** The formerly-vendored
   `crystaldba/postgres-mcp` `sql/` subpackage (`src/mcpg/_vendor/`) is
   replaced by a first-party `src/mcpg/sql/` package — `allowlist.py` (the

README.md

@@ -102,6 +102,11 @@ docker run --rm --name mcpg -p 8000:8000 \
     ghcr.io/devopam/mcpg:latest
 ```
 
+On **Windows PowerShell** replace the trailing `\` with a backtick `` ` ``
+(or put the command on one line); the [installation
+guide](docs/installation.md#option-2--docker) has ready-to-copy
+Linux/macOS, PowerShell, and Command Prompt blocks.
+
 Or build it yourself from source:
 
 ```bash

docs/installation.md

@@ -52,14 +52,39 @@ mcpg --version
 
 ### Option 2 — Docker
 
+Build the image (identical on every OS):
+
 ```bash
 docker build -t mcpg https://github.com/devopam/MCPg.git
+```
+
+Then run it. The only per-OS difference is the line-continuation
+character — pick the block for your shell:
+
+**Linux / macOS (bash/zsh)**
+
+```bash
 docker run --rm --name mcpg -p 8000:8000 \
     -e MCPG_DATABASE_URL=postgresql://user:pass@host:5432/db \
     -e MCPG_ACCESS_MODE=read-only \
     mcpg
 ```
 
+**Windows (PowerShell)**
+
+```powershell
+docker run --rm --name mcpg -p 8000:8000 `
+    -e MCPG_DATABASE_URL=postgresql://user:pass@host:5432/db `
+    -e MCPG_ACCESS_MODE=read-only `
+    mcpg
+```
+
+**Windows (Command Prompt)**
+
+```bat
+docker run --rm --name mcpg -p 8000:8000 -e MCPG_DATABASE_URL=postgresql://user:pass@host:5432/db -e MCPG_ACCESS_MODE=read-only mcpg
+```
+
 The image is a hardened multi-stage build: the runtime stage drops
 the build toolchain and runs as `uid=10001 / gid=10001` with a
 `nologin` shell. Application files are root-owned and read-only to
@@ -81,20 +106,52 @@ or contribute.
 
 ## Quick start
 
-The minimum to get running locally:
+MCPg is configured entirely through environment variables, and the
+**only per-OS difference in this whole guide is how you set them**. The
+`mcpg` command itself, `pip`, `uv`, and `docker` are identical on every
+platform. Set variables like this:
+
+| Shell | Set a variable |
+|---|---|
+| **Linux / macOS** (bash/zsh) | `export MCPG_DATABASE_URL=postgresql://…` |
+| **Windows — PowerShell** | `$env:MCPG_DATABASE_URL = "postgresql://…"` |
+| **Windows — Command Prompt** | `set MCPG_DATABASE_URL=postgresql://…` |
+
+Every `export …` example below uses the Linux/macOS form; translate it
+to your shell with the table above.
+
+The minimum to get running locally (stdio transport, read-only mode):
+
+**Linux / macOS (bash/zsh)**
 
 ```bash
 export MCPG_DATABASE_URL=postgresql://postgres:postgres@localhost:5432/mydb
 mcpg
 ```
 
+**Windows (PowerShell)**
+
+```powershell
+$env:MCPG_DATABASE_URL = "postgresql://postgres:postgres@localhost:5432/mydb"
+mcpg
+```
+
+**Windows (Command Prompt)**
+
+```bat
+set MCPG_DATABASE_URL=postgresql://postgres:postgres@localhost:5432/mydb
+mcpg
+```
+
 That starts MCPg on the **stdio** transport in **read-only** mode,
 ready to be consumed by an MCP client (Claude Desktop, Cursor,
 Continue, etc.). See the next section for how to wire it into a
 specific client.
 
 For HTTP-based clients:
 
+**Linux / macOS (bash/zsh)**
+
 ```bash
 export MCPG_DATABASE_URL=postgresql://postgres:postgres@localhost:5432/mydb
 export MCPG_TRANSPORT=streamable-http
@@ -103,6 +160,26 @@ export MCPG_HTTP_AUTH_TOKEN=...    # optional but strongly recommended
 mcpg
 ```
 
+**Windows (PowerShell)**
+
+```powershell
+$env:MCPG_DATABASE_URL = "postgresql://postgres:postgres@localhost:5432/mydb"
+$env:MCPG_TRANSPORT = "streamable-http"
+$env:MCPG_HTTP_PORT = "8000"
+$env:MCPG_HTTP_AUTH_TOKEN = "..."    # optional but strongly recommended
+mcpg
+```
+
+**Windows (Command Prompt)**
+
+```bat
+set MCPG_DATABASE_URL=postgresql://postgres:postgres@localhost:5432/mydb
+set MCPG_TRANSPORT=streamable-http
+set MCPG_HTTP_PORT=8000
+set MCPG_HTTP_AUTH_TOKEN=...
+mcpg
+```
+
 ---
 
 ## Wire it into an MCP client