archilyzer

commit 1f285f61c0182a962eeaf92f4ea6f72dc327d306
parent ab5d4fae7d8cc8c4796443b32cbc1885e5aa529f
Author: I Mean I'm Just Saying <imeanimjustsaying@kiwifarms.st>
Date:   Wed, 30 Sep 2026 18:38:31 -0400

docs: mcp/README registers archilyzer in both examples; README §1 registers from the repo root with "$PWD"

mcp/README's Add to Claude Code and mcp.json examples named the server rekietalyzer; the paragraph
on renaming stays and says why every example uses archilyzer. README §1's /ABS/PATH form becomes
the "$PWD" form §4 and the Windows notes already use.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

Diffstat:
M
README.md
 | 
4
++--
M
mcp/README.md
 | 
11
++++++-----

2 files changed, 8 insertions(+), 7 deletions(-)
diff --git a/README.md b/README.md
@@ -63,14 +63,14 @@ TRANSCRIPT_SITE_URL=https://jeralyzer.pages.dev \
 ```
 
 There is nothing to compile — it runs from source through `tsx`. To register it with
-Claude Code:
+Claude Code, from the repo's root:
 
 ```bash
 claude mcp add archilyzer \
   --env TRANSCRIPT_SITE_URL=https://jeralyzer.pages.dev \
   --env ARCHILYZER_EDITOR_URL=http://localhost:3001 \
   --env WORKER_TOKEN=… \
-  -- pnpm -C /ABS/PATH/TO/this/repo --filter yt-dlp-transcript-mcp exec tsx src/index.ts
+  -- pnpm -C "$PWD" --filter yt-dlp-transcript-mcp exec tsx src/index.ts
 ```
 
 The two editor lines are optional: they let `fetch_clip` ask a local editor for clip
diff --git a/mcp/README.md b/mcp/README.md
@@ -520,7 +520,7 @@ Logs go to stderr; stdout is the MCP JSON-RPC channel.
 ## Add to Claude Code
 
 ```sh
-claude mcp add rekietalyzer \
+claude mcp add archilyzer \
   --env TRANSCRIPT_SITE_URL=https://rekietalyzer.pages.dev \
   --env ARCHILYZER_EDITOR_URL=http://localhost:3001 \
   --env WORKER_TOKEN=… \
@@ -534,9 +534,10 @@ the same; `fetch_clip` then says it has no editor and fetches nothing.
 
 **The `/sweep` and `/ask` commands.** `.claude/commands/{sweep,ask}.md` in this
 repo call `mcp__archilyzer__sweep_plan` / `mcp__archilyzer__ask_plan` — the tool
-name embeds the MCP server name **as you registered it**, so if you used another
-name (`rekietalyzer` above), change the `mcp__<name>__` prefix in those two
-files to match. `foo:bar` namespacing is plugin-only, so what you type stays
+name embeds the MCP server name **as you registered it**, which is why every
+example registers it as `archilyzer`. If you use another name (a site's own,
+say `rekietalyzer`), change the `mcp__<name>__` prefix in those two files to
+match. `foo:bar` namespacing is plugin-only, so what you type stays
 `/sweep`, not `/archilyzer:sweep`.
 
 ## Add to any MCP client (mcp.json)
@@ -544,7 +545,7 @@ files to match. `foo:bar` namespacing is plugin-only, so what you type stays
 ```json
 {
   "mcpServers": {
-    "rekietalyzer": {
+    "archilyzer": {
       "command": "pnpm",
       "args": [
         "-C", "/ABS/PATH/TO/yt-dlp-transcript-browser",