@hybridlabor-api/aos 4.2.0 → 4.4.0

package/mcps/tdmcp/docs/guide/install.md

@@ -1,200 +0,0 @@
----
-description: "Install tdmcp, the TouchDesigner MCP server, in Claude Desktop in about 3 minutes — no terminal, no Node. One-click .mcpb extension, then flip on the bridge."
----
-
-# Claude — Desktop & Code
-
-**The easiest way is Claude Desktop** — no terminal, no Node, no setup files. The
-whole tdmcp server is bundled inside one extension file. Three steps, about 3
-minutes. Using **Claude Code or Cursor**? See [the section below](#other-clients).
-Prefer **Codex**, or a **free local model with no API**? See
-[Codex](/guide/codex) or [Local copilot](/guide/local-copilot).
-
-::: tip Using Claude Code, Cursor, or Codex instead?
-You don't need to do any of this by hand. Paste this one message into your AI and
-it installs everything for you:
-
-```text
-Install and connect tdmcp for me using the official install guide:
-https://pantani.github.io/tdmcp/guide/install
-Do every step yourself; only stop when you need me to do the TouchDesigner bridge step.
-```
-:::
-
-## 1. Download the extension
-
-**[⬇ Download tdmcp.mcpb](https://github.com/Pantani/tdmcp/releases/latest/download/tdmcp.mcpb)**
-
-An `.mcpb` (MCP Bundle) is a single file Claude Desktop installs as an extension.
-The server is inside it — nothing else to download. (`.mcpb` is the current format;
-it was previously called `.dxt`, and any older `.dxt` you may already have still
-installs.)
-
-::: warning If the download link doesn't work
-A release may not be published yet. Ask whoever shared tdmcp with you for the
-`tdmcp.mcpb` file directly, then continue at step 2.
-:::
-
-## 2. Install it in Claude Desktop {#install-from-file}
-
-1. Open Claude Desktop → **Settings → Extensions**.
-2. Choose **Install from file** (or just **drag `tdmcp.mcpb` onto the window**).
-3. If it asks for settings, leave **TouchDesigner host** = `127.0.0.1` and
-   **TouchDesigner port** = `9980`. (The defaults are right when TouchDesigner
-   runs on the same computer.)
-4. **Enable** the "TouchDesigner (tdmcp)" extension.
-
-## 3. Turn on the bridge inside TouchDesigner {#turn-on-the-bridge}
-
-This is what lets Claude actually drive TouchDesigner. The easiest way needs **no
-Textport and no terminal** — just drag a file in. Prefer a one-paste command, or
-open lots of projects? The two alternatives below still work.
-
-### Easiest — drag in the release `.tox` {#drag-in-tox}
-
-1. **[⬇ Download tdmcp_bridge_package.tox](https://github.com/Pantani/tdmcp/releases/latest/download/tdmcp_bridge_package.tox)**
-   from the latest release.
-2. **Open TouchDesigner**, then drag the `.tox` from Finder/Explorer into your
-   `/project1` network.
-3. Click **Install** on the `tdmcp_bridge_package` component.
-
-That's it — no Textport, no Preferences, no clone. The package is self-bootstrapping:
-on the first **Install** it downloads `td/modules` from the matching release zip
-into `~/tdmcp-bridge` and starts the bridge on port 9980. You should see the
-`tdmcp_bridge` component appear in `/project1`. Its **Uninstall** button removes
-only that runtime bridge.
-
-::: warning If the release has no `.tox`
-Older releases may not ship the file yet. Use the one-paste runtime bridge below
-instead, then continue.
-:::
-
-### Quick runtime bridge
-
-1. **Open TouchDesigner.**
-2. Open the **Textport**: menu **Dialogs → Textport and DATs**.
-3. Paste this **one line** and press **Enter**:
-
-   ```python
-   import urllib.request; exec(urllib.request.urlopen("https://github.com/Pantani/tdmcp/raw/v0.12.0/td/bootstrap.py").read().decode())
-   ```
-
-You should see:
-
-```
-[tdmcp] bridge running on port 9980 (/project1/tdmcp_bridge)
-```
-
-It is safe and reversible. To remove it later, paste
-`from mcp import install; install.uninstall()`.
-
-### Draggable Palette package
-
-This installs `tdmcp_bridge_package` into TouchDesigner's Palette so each new
-project is just drag, click **Install**, and start working.
-
-1. In a terminal, run:
-
-   ```bash
-   npx --yes --package=@dpantani/tdmcp tdmcp install-bridge --palette
-   ```
-
-   Working from a clone? Use:
-
-   ```bash
-   node dist/index.js install-bridge --palette
-   ```
-
-2. Copy the Palette package Textport command it prints.
-3. In TouchDesigner, open **Dialogs → Textport and DATs**, paste the command,
-   and press **Enter**.
-4. Open the Palette browser, find **tdmcp → tdmcp_bridge_package**, and drag it
-   into `/project1`.
-5. Click **Install** on the component.
-
-Packages generated without a **Modules Dir** can self-bootstrap: they download
-the zip in **Repo Zip**, extract only `td/modules` into **Bootstrap Dest**
-(default `~/tdmcp-bridge`), and start from that local cache. This is the shape
-used for release-ready `.tox` packages.
-
-Verify from a terminal:
-
-```bash
-curl http://127.0.0.1:9980/api/info
-```
-
-The Palette package stays in your project; its **Uninstall** button removes only
-`/project1/tdmcp_bridge`.
-
-## You're connected
-
-With TouchDesigner open and the bridge on, you're ready to
-[make your first visual](/guide/first-visual).
-
-::: warning One safety note
-The bridge lets Claude run code inside TouchDesigner and listens on port 9980.
-Only use it on a network you trust (like your own computer), not on public Wi-Fi
-without a firewall. Developers can lock it down further — see
-[Security](/reference/architecture#security).
-:::
-
-## Claude Code, Cursor & other MCP clients {#other-clients}
-
-Claude Desktop (above) is the no-terminal route. For **Claude Code** or **Cursor**,
-connect tdmcp from source — you'll need **[Node.js 20+](https://nodejs.org)**.
-(**Codex** has its own walkthrough on the [Codex page](/guide/codex); the same
-source build also powers the [local copilot](/guide/local-copilot).)
-
-::: tip Easiest — let your AI do it
-Paste the one-liner from the top of this page into your client; it clones, builds
-and wires everything itself, stopping only for the TouchDesigner step in
-[step 3](#turn-on-the-bridge).
-:::
-
-Or wire it by hand:
-
-```bash
-git clone https://github.com/Pantani/tdmcp.git
-cd tdmcp
-npm run setup   # installs, builds, and prints the exact line to connect your client
-```
-
-::: tip One command end-to-end — `tdmcp init`
-After the build, **`tdmcp init --yes`** runs the whole onboarding in one shot:
-it stages the TD bridge, deep-merges a client config for Claude / Cursor /
-Codex (auto-detected), seeds a default profile, and (optionally) generates a
-`TDMCP_BRIDGE_TOKEN`. Add `--dry-run` to see the plan first, or `--json` for a
-machine-readable envelope. The per-client manual steps below still work for
-advanced setups. See [CLI · Onboarding](/reference/cli#onboarding).
-:::
-
-`npm run setup` prints a ready-to-paste command with your real paths filled in.
-The manual equivalents (`<project-path>` is the cloned folder — run `pwd` inside it):
-
-- **Claude Code** — `claude mcp add tdmcp -- node <project-path>/dist/index.js`
-- **Codex CLI** — `codex mcp add tdmcp -- node <project-path>/dist/index.js`, or add
-  this to `~/.codex/config.toml`:
-
-  ```toml
-  [mcp_servers.tdmcp]
-  command = "node"
-  args = ["<project-path>/dist/index.js"]
-  ```
-
-- **Cursor** — create `.cursor/mcp.json` in your workspace:
-
-  ```json
-  {
-    "mcpServers": {
-      "tdmcp": { "command": "node", "args": ["<project-path>/dist/index.js"] }
-    }
-  }
-  ```
-
-Restart your client so it loads the server, then turn on the bridge —
-[step 3 above](#turn-on-the-bridge). It's the same one line for every client.
-
-## Trouble?
-
-See [Troubleshooting](/guide/troubleshooting) — it covers "TouchDesigner isn't
-reachable", download errors, and the macOS microphone permission popup.

package/mcps/tdmcp/docs/guide/local-copilot.md

@@ -1,154 +0,0 @@
----
-title: Local copilot (no API)
-description: "Run tdmcp — the TouchDesigner MCP server — with a free local LLM. `tdmcp chat` opens a browser copilot wired to TouchDesigner: no paid API, works offline."
----
-
-# Local copilot (no API)
-
-tdmcp ships a **local copilot** so you can drive TouchDesigner with a **free LLM
-running on your own machine** — no paid API, no account, works offline. The
-command `tdmcp chat` opens a small chat page in your browser, wired to the same
-TouchDesigner bridge the other clients use.
-
-It's the budget-friendly, private path: great for the everyday stuff, and it hands
-off to [Claude](/guide/install) or [Codex](/guide/codex) the moment you want a
-whole system built.
-
-::: tip Which path is this?
-[Claude Desktop](/guide/install) is the no-terminal route. This page is for running
-tdmcp with a **local model** instead of a paid assistant — it needs
-[Node.js 20+](https://nodejs.org), like the Codex and Cursor paths.
-:::
-
-## What it's good for
-
-The local copilot is given a **curated, safe subset** of the tools, so it's quick
-and hard to misuse. It's meant for the easy stuff:
-
-- **Inspecting** your project — what's there, how it's wired.
-- **Reading errors** and explaining what's wrong.
-- **Creating, wiring and tweaking individual operators** — one node at a time.
-
-It deliberately **can't** build whole systems (no Layer-1 generators) and **can't
-run raw Python**. When you want a full audio-reactive or generative network, click
-**Escalate ⇪** in the UI: it copies a ready-to-paste prompt you hand to
-[Claude](/guide/install) or [Codex](/guide/codex). They drive the *same* project,
-so nothing has to move.
-
-## What you need
-
-- **[TouchDesigner](https://derivative.ca/download)** with the bridge on (the same
-  one-line step as every client — [see below](#turn-on-the-bridge)).
-- **[Node.js 20+](https://nodejs.org)** — used to launch the copilot.
-- **[Ollama](https://ollama.com)** — the free local model runner. `tdmcp chat`
-  starts it for you if it isn't already running.
-
-## Start it
-
-The quickest path needs no clone — just Node and Ollama installed:
-
-```bash
-# one-time: install Ollama from https://ollama.com, then optionally pre-pull a model
-ollama pull qwen2.5:3b      # optional — the UI also has a one-click pull
-
-npx --yes --package=@dpantani/tdmcp tdmcp chat # opens http://127.0.0.1:4141 in your browser
-```
-
-If you already cloned and built tdmcp (the [from-source path](/guide/install#other-clients)),
-the command is simply `tdmcp chat` (or `node dist/index.js chat`).
-
-`tdmcp chat` **starts Ollama for you** if the daemon isn't up — detached and left
-running, so closing the chat never takes your model offline. Useful flags:
-
-- **`--read-only`** — force the safe/read-only tool tier for the whole session.
-- **`--creative`** — use the creative tool tier and a warmer sampling preset.
-- **`--prompt <text>`** — run one headless prompt and print the answer without
-  opening the browser.
-- **`--no-ollama`** — don't auto-start it (for a remote endpoint or a daemon you
-  manage yourself).
-- **`--no-open`** — don't open the browser automatically.
-- **`--profile <name>`** / **`--config <path>`** — use a saved venue/profile
-  config for this chat run.
-- **`--help`** — list everything.
-
-::: tip Which local model?
-**`qwen2.5:3b`** is the default — benchmarked at 100% tool-calling on the
-simple-task workload, as reliable as bigger models but faster and lighter. Sub-3B
-models are flaky; bump to `qwen2.5:7b` only if you want more answer-quality
-headroom. More detail in the [CLI reference](/reference/cli#local-copilot-tdmcp-chat).
-:::
-
-## Using the chat
-
-The browser UI is wired to your live TouchDesigner project. It has:
-
-- A **read-only** toggle — let it look but not touch.
-- Live **model switching** and **endpoint settings**, plus a one-click **model
-  pull** if a model isn't downloaded yet.
-- **Persistent history**, so your conversation survives a restart.
-- **Escalate ⇪** — copies a handoff prompt for Claude or Codex when a task is too
-  big for the local model.
-
-## RAG and generation flow
-
-Creative RAG and Project RAG are context sources first, not automatic builders.
-`tdmcp ask --with-creative` can add Creative RAG references to a prompt, and
-`project_rag_search` can surface real TouchDesigner projects, components and
-snippets, but both are read-only unless you explicitly choose a mutating tool.
-
-To turn a Creative RAG card into a TouchDesigner network, enable the guarded apply
-path and dry-run it before mutating the project:
-
-```bash
-export TDMCP_RAG_ENABLED=1
-export TDMCP_RAG_APPLY_CARD=1
-tdmcp-agent apply-creative-card --params '{"card_id":"<card-id>","dry_run":true}'
-```
-
-Review the planned target tool and arguments, then rerun with `"dry_run":false`
-only when you want tdmcp to create operators. Treat Project RAG results as
-technical references and provenance, not executable project instructions.
-
-## Point it at a different model
-
-By default the copilot talks to local Ollama, but it speaks the standard
-OpenAI-compatible API — so you can aim it anywhere with two environment variables:
-
-| Variable | Default | Use it for |
-| --- | --- | --- |
-| `TDMCP_LLM_BASE_URL` | `http://127.0.0.1:11434/v1` | LM Studio, a cloud GPU, or a paid API. |
-| `TDMCP_LLM_MODEL` | `qwen2.5:3b` | Any model id available at that endpoint. |
-| `TDMCP_LLM_TIER` | `standard` | Start the UI in `standard`, `safe`, or `creative` mode. |
-| `TDMCP_LLM_MAX_STEPS` | `8` | Cap model/tool loop iterations for one turn. |
-| `TDMCP_LLM_TEMPERATURE` | `0.4` | Tune sampling temperature for the chat endpoint. |
-
-Full list (including `TDMCP_LLM_API_KEY` and the chat port) is in
-[environment variables](/reference/environment#local-copilot-tdmcp-chat).
-
-## Turn on the bridge {#turn-on-the-bridge}
-
-Like every client, the copilot needs the small bridge running *inside*
-TouchDesigner. The easiest way is to drag the release `.tox` in — no Textport
-([see Install](/guide/install#drag-in-tox)). Prefer one paste? Open the
-**Textport** (**Dialogs → Textport and DATs**), paste this one line, and press Enter:
-
-```python
-import urllib.request; exec(urllib.request.urlopen("https://github.com/Pantani/tdmcp/raw/v0.12.0/td/bootstrap.py").read().decode())
-```
-
-You should see `[tdmcp] bridge running on port 9980`. See
-[Install](/guide/install#turn-on-the-bridge) for details and how to remove it
-later.
-
-## Not connecting?
-
-- Confirm the bridge is on: `curl http://127.0.0.1:9980/api/info` should return
-  JSON.
-- Make sure Ollama is installed and a model is pulled (the UI's model pull does
-  this for you).
-- Full [Troubleshooting](/guide/troubleshooting) covers the common cases.
-
-With TouchDesigner open and the bridge on, ask in plain language — *"what's in this
-project?"*, *"why is this node red?"*, *"add a blur after the noise."* For bigger
-ideas, see the [prompt cookbook](/guide/prompt-cookbook) or escalate to
-[Claude](/guide/install) / [Codex](/guide/codex).

package/mcps/tdmcp/docs/guide/lops-integration.md

@@ -1,133 +0,0 @@
----
-description: "Use tdmcp from inside TouchDesigner via dotsimulate's LOPs MCP Client — point it at the hardened launcher and an in-TD agent can build and inspect your project."
----
-
-# Use from TouchDesigner (LOPs)
-
-dotsimulate's **LOPs "MCP Client"** runs *inside* TouchDesigner and can talk to
-any MCP server. Point it at tdmcp and an agent living in your TD network can
-build, wire, inspect and preview operators in that same project — closing the
-loop **TD (LOPs MCP Client) → tdmcp server → the tdmcp bridge → your network.**
-
-This is **not** an LLM-backend swap: LOPs brings its own model (OpenAI / Claude /
-Ollama); tdmcp is the *tools* it calls, exactly like Claude or Cursor would.
-
-## What you get
-
-The LOPs client gets the **full tdmcp tool surface** — the build/inspect/preview
-tools **plus** the knowledge-base tools (`get_td_classes`,
-`get_td_class_details`, `get_module_help`, `search_operators`, `find_td_nodes`).
-Those KB tools cover part of what dotsimulate's *dotContext* provides, so you
-don't need a separate operator-reference layer alongside tdmcp.
-
-When you connect through the recommended launcher (below), tdmcp starts in its
-**`safe` profile** — the destructive tools are hidden so an autonomous in-TD
-agent can't delete nodes or run unreviewed code by accident.
-
-## Prerequisites
-
-- The tdmcp **bridge is installed and running** inside the *same* TouchDesigner
-  instance — see [install step 3, "turn on the bridge"](/guide/install#turn-on-the-bridge).
-- **Node.js 20+ on your PATH** — LOPs spawns `node`.
-- You have run **`npm run build`** in your tdmcp checkout, so `dist/index.js`
-  exists.
-- dotsimulate's **LOPs** is installed, with the MCP Client component.
-
-## Connect (recommended: the launcher)
-
-dotsimulate's `servers_config.json` documents `transport`, `command`, `args`,
-`cwd` and `description` — but **no `env` field** — so we can't set tdmcp's
-hardening variables through the config directly. tdmcp ships a tiny launcher,
-`scripts/tdmcp-lops.mjs`, that sets them for you and then starts the server.
-Point the LOPs client at it:
-
-```json
-{
-  "mcpServers": {
-    "tdmcp": {
-      "transport": "stdio",
-      "command": "node",
-      "args": ["/abs/path/to/tdmcp/scripts/tdmcp-lops.mjs"],
-      "cwd": "/abs/path/to/tdmcp",
-      "description": "tdmcp — build & inspect this TouchDesigner project (hardened: safe profile)"
-    }
-  }
-}
-```
-
-Replace `/abs/path/to/tdmcp` with the folder where you cloned tdmcp (run `pwd`
-inside it). Use the **full absolute path** for both `command`/`args` and `cwd` —
-LOPs resolves `cwd` differently than CLI clients, so don't rely on relative
-paths. The `tdmcp-lops.mjs` launcher sets the `safe` profile for you.
-
-## Alternative: an `env` block (if your LOPs build supports it)
-
-dotsimulate's published schema does **not** document an `env` field, so the
-launcher above is the safe default. If your LOPs build happens to pass an `env`
-block through, you can instead point `args` straight at `dist/index.js` and set
-the variables yourself:
-
-```json
-{
-  "mcpServers": {
-    "tdmcp": {
-      "transport": "stdio",
-      "command": "node",
-      "args": ["/abs/path/to/tdmcp/dist/index.js"],
-      "cwd": "/abs/path/to/tdmcp",
-      "env": {
-        "TDMCP_RAW_PYTHON": "off",
-        "TDMCP_TOOL_PROFILE": "safe"
-      },
-      "description": "tdmcp — hardened for an in-TD agent"
-    }
-  }
-}
-```
-
-If the `env` block is ignored (you'll see the destructive tools still listed),
-fall back to the launcher.
-
-## Hardening note
-
-For an autonomous in-TD agent — no human reviewing each call — harden the
-surface:
-
-- **`TDMCP_RAW_PYTHON=off`** removes the two raw-Python tools
-  (`execute_python_script`, `exec_node_method`) where the *client* authors the
-  code. It is **not** a code-execution kill-switch: many higher-level tools still
-  send their own *templated* Python to the bridge.
-- **`TDMCP_TOOL_PROFILE=safe`** goes further and also hides destructive tools
-  (node deletion, DAT rewrites, checkpoint/component/package writes, preview-asset
-  writes, panic controls) — a strict superset of `RAW_PYTHON=off`. The launcher sets this for you. See
-  [Environment variables](/reference/environment).
-- Bridge-side arbitrary exec is now closed by default unless
-  **`TDMCP_BRIDGE_TOKEN`** is configured or **`TDMCP_BRIDGE_ALLOW_EXEC=1`** is set
-  in *TouchDesigner's* own environment. Keep it closed for autonomous LOPs use.
-
-## How it works
-
-Both the LOPs client and the tdmcp bridge live in the **same** TouchDesigner
-process. The LOPs client spawns `node dist/index.js` (the tdmcp server) over
-stdio; that server then talks HTTP to the bridge on `127.0.0.1:9980` — the very
-same TD — which manipulates your network. No transport change is needed; stdio is
-tdmcp's default. The spawned server is short-lived, tied to the MCP client's
-lifecycle. See [Architecture](/reference/architecture#transports-events).
-
-## This does NOT replace `tdmcp chat`
-
-The [local LLM copilot](/guide/local-copilot) (`tdmcp chat`) is a *separate*
-surface — tdmcp running its own local model. LOPs is a **client that consumes its
-own model** (OpenAI / Claude / Ollama) and calls tdmcp's tools; it is not a
-swap-in for the copilot's model backend. Use whichever fits your workflow.
-
-## Troubleshooting
-
-- **"node not found"** — LOPs couldn't find Node on its PATH. Install
-  [Node.js 20+](https://nodejs.org) and make sure it's on the PATH the TD process
-  inherits.
-- **"dist/index.js not found"** — the launcher prints this to stderr when the
-  build is missing. Run `npm run build` in your tdmcp folder.
-- **"bridge not reachable"** — the tdmcp bridge isn't running in this TD, or it's
-  on a different host/port. Re-check [install step 3](/guide/install#turn-on-the-bridge)
-  and [Troubleshooting](/guide/troubleshooting).

package/mcps/tdmcp/docs/guide/mcp-resources.md

@@ -1,96 +0,0 @@
----
-description: "The tdmcp:// MCP resources an AI client can read — operators, Python API, recipes, GLSL snippets, cheatsheets, learning paths, prompts, live scene digests and more."
----
-
-# MCP resources
-
-Beyond the tools it can *call*, tdmcp exposes a library of **resources** an AI
-client can *read* — operator docs, shader snippets, recipes, cheatsheets, a
-learning path, even a live snapshot of your running project. Resources are how
-the assistant grounds itself in TouchDesigner facts and in tdmcp's own surface
-before it builds, instead of guessing.
-
-You rarely address these by hand; a capable client lists and reads them for you.
-But knowing the families helps you ask better questions — *"check the operators
-resource"*, *"read the GLSL snippet catalog first"* — and explains where the
-assistant's knowledge comes from.
-
-::: tip This is the artist-facing map
-For the full per-resource reference (every URI template, every parameter), the
-[Architecture](/reference/architecture) and
-[Tools reference](/reference/tools) pages are the source of truth. This page is
-the orientation.
-:::
-
-## Knowledge base (always on)
-
-The committed operator knowledge base, exposed as readable resources:
-
-| Family | URI | What it exposes |
-| --- | --- | --- |
-| Operators | `tdmcp://operators/{name}` | Operator catalog — read a category (TOP, CHOP, SOP, DAT, COMP, MAT, POP) to list, or an operator name for full docs. |
-| Operator connections | `tdmcp://operator-connections/{operator}` | Likely upstream/downstream operators, workflow hits and next-operator suggestions grounded in imported operator docs and patterns. |
-| Operator examples | `tdmcp://operator-examples/{operator}` | Stored Python snippets, expressions, generated usage patterns and tips for a specific operator. |
-| Python API | `tdmcp://python-api/{class_name}` | TouchDesigner Python class reference — members and methods. |
-| TD versions | `tdmcp://td-versions/{version}` | Stable TouchDesigner release metadata, Python-version notes, highlights and compatibility changes. |
-| Experimental builds | `tdmcp://td-experimental/{series_or_category}` | Experimental TouchDesigner build-series data, feature flags, new operators and breaking-change notes. |
-| Compatibility | `tdmcp://compat/operators/{operator}`, `tdmcp://compat/python/{class_or_member}` | Direct operator and Python API compatibility lookups for added/changed/removed version notes. |
-| Patterns | `tdmcp://patterns/{pattern_name}` | Named operator-chain workflow patterns (recommended wiring). |
-| GLSL patterns | `tdmcp://glsl/{pattern_name}` | Named shader techniques with ready-to-use fragment-shader snippets. |
-| GLSL snippets | `tdmcp://glsl-snippets` | A vetted, license-clean catalog of embedded GLSL snippets the agent can assemble without guessing IDs. |
-| Technique packs | `tdmcp://techniques/{category}` | Bottobot technique packs such as audio-visual, GPU compute, machine learning, networking and advanced Python workflows. |
-| TD classes | `tdmcp://td-classes/{family}` | TouchDesigner operator-family class references such as TOP Class, CHOP Class and COMP Class. |
-| Recipes | `tdmcp://recipes/{recipe_name}`, `tdmcp://recipes/search/{query}` | Pre-validated composite network templates, plus keyword search over built-in and vault recipes. |
-| Tutorials | `tdmcp://tutorials/{tutorial_name}` | Long-form TD fundamentals and workflows. |
-
-## Guidance & onboarding (always on)
-
-Compact, KB-grounded guides that help the agent pick the right move:
-
-| Family | URI | What it exposes |
-| --- | --- | --- |
-| Cheatsheets | `tdmcp://cheatsheets` | Compact reminders for common workflows (operator families, the debug loop, GLSL-TOP assembly, audio binding, vault library), with links to richer resources. |
-| Learning path | `tdmcp://learning/touchdesigner` | A curated path pairing the `teach_touchdesigner` prompt with embedded operator and tutorial resources. |
-| Cookbook | `tdmcp://cookbook`, `tdmcp://cookbook/{locale}` | The prompt cookbook as a resource, in English (`en`) or Portuguese (`pt`). |
-
-## Surface discovery (always on)
-
-So clients and the local copilot stay in sync with the real registry instead of
-drifting:
-
-| Family | URI | What it exposes |
-| --- | --- | --- |
-| Commands | `tdmcp://commands` | The CLI verbs, generated from the actual dispatcher (safe / mutating / unsafe). |
-| Prompts | `tdmcp://prompts` | The MCP prompts tdmcp offers, generated from the prompt registry. |
-| Session profile | `tdmcp://session/profile` | Your persistent cross-session profile — see [Session profile & corpus learning](/guide/session-profile). |
-
-## Live project (needs the bridge)
-
-When the [bridge](/guide/install#turn-on-the-bridge) is reachable, two resources
-read your running project. They no-op without a TD client and cache briefly (5 s
-hot, 1 s offline):
-
-| Family | URI | What it exposes |
-| --- | --- | --- |
-| Scene summary | `tdmcp://scene/{view}` | A compact snapshot of the running project — `current` (topology + perf + errors), `operators` (full inventory), or `errors` (clustered list). |
-| Graph digest | `tdmcp://digest/{path}` | A token-cheap (<500 token) structured digest of a subtree: header, family counts, the primary output's upstream chain, and top grouped errors. |
-
-## Opt-in libraries (off by default)
-
-Registered only when their feature flags are on — see
-[Session profile & corpus learning](/guide/session-profile):
-
-| Family | URI | Gate |
-| --- | --- | --- |
-| Creative RAG | `tdmcp://creative/cards/{id}`, `tdmcp://creative/search` | `TDMCP_RAG_ENABLED=1` |
-| Project RAG | `tdmcp://project/cards/{id}`, `tdmcp://project/search`, `tdmcp://project/sources` | `TDMCP_RAG_ENABLED=1` and `TDMCP_PROJECT_RAG_ENABLED=1` |
-
-Both are read-only and carry source URL, license and rights notes on every
-result.
-
-## See also
-
-- [Architecture](/reference/architecture) for how resources are registered and
-  served.
-- [Session profile & corpus learning](/guide/session-profile) for the
-  session-profile and RAG resources in depth.

package/mcps/tdmcp/docs/guide/mediapipe-adapters.md

@@ -1,90 +0,0 @@
----
-description: "Wire MediaPipe face, hand, body and segmentation tracking into TouchDesigner with tdmcp — adapter tools that load the free torinmb plugin and hand you clean, canonical CHOPs and mattes."
----
-
-# MediaPipe adapters
-
-The body-tracking guide shows how to *use* a tracked body. This page is about the
-layer underneath: the **adapter tools** that load the free
-[torinmb/mediapipe-touchdesigner](https://github.com/torinmb/mediapipe-touchdesigner)
-plugin, switch on the pipeline you want, find the engine's output, and hand you a
-clean, canonical CHOP or matte you can wire into anything.
-
-Reach for an adapter when you want face / hand / body / segmentation data as a
-stable signal — landmarks in TD coordinates, a person matte, screen-space points
-for UI — rather than a finished visual.
-
-## Get the plugin
-
-The plugin is MIT-licensed and runs on macOS and Windows from an ordinary
-webcam. tdmcp's package manager can stage it for you:
-
-```bash
-npx --yes --package=@dpantani/tdmcp tdmcp install mediapipe-touchdesigner
-```
-
-This grabs the MIT release and extracts it under `~/.tdmcp/packages`; the
-adapters resolve the staged path automatically (with legacy and manual fallbacks).
-See [Body & pose tracking](/guide/body-tracking) for the camera-permission and
-first-run details.
-
-::: tip Timeline must be playing
-The plugin's embedded browser only captures while the TD timeline plays. If the
-data reads zero, press Play.
-:::
-
-## The adapters
-
-Each adapter loads the engine (idempotent — it reuses an existing one), toggles
-the pipeline you ask for, and builds a small wrapper COMP whose Script CHOP/TOP
-reads the engine's JSON output and republishes it as a canonical signal. They
-probe the engine's output names across plugin versions, so they keep working as
-the plugin evolves.
-
-| Adapter | Layer | What it wires up | Output |
-| --- | --- | --- | --- |
-| **`setup_body_tracking`** | 1 | Pose pipeline → a canonical pose CHOP; optionally builds a skeleton visual. | 33-landmark pose CHOP (`tx`/`ty`/`tz`/confidence), hip-centred |
-| **`setup_face_tracking`** | 2 | Face-mesh pipeline → a canonical face CHOP. | 468 (or 478 with iris) landmark CHOP, nose-centred |
-| **`setup_hand_tracking`** | 2 | Hand pipeline → a canonical hand CHOP, in world or image space. | `max_hands` × 21-landmark CHOP, with handedness and screen-space channels |
-| **`setup_segmentation`** | 2 | Selfie-segmentation pipeline → a feathered mask TOP, optionally a pre-keyed RGBA. | mask TOP (+ optional `person_rgba` for drop-in compositing) |
-| **`setup_mediapipe_plugin`** | 1 | Loads the engine **once** and toggles Face/Hand/Body/Segmentation together; discovers and exports each pipeline's output path. | the engine's discovered DAT/TOP paths |
-
-> *"Set up hand tracking in world space for up to two hands."*
-> *"Set up segmentation with a 12-px feather and publish a pre-keyed person
-> matte."*
-
-Use `setup_mediapipe_plugin` when you want several pipelines from one engine in a
-single call; use the individual `setup_*` adapters when you want exactly one
-modality and its canonical wrapper.
-
-## From adapter to art
-
-Adapters produce signals; the `create_*` tools consume them. Point a consumer's
-source at the adapter's output CHOP/TOP and the rest of the network behaves
-exactly as it does in synthetic mode:
-
-- **Pose** → `create_pose_tracking`, `create_pose_skeleton`,
-  `create_body_reactive` (see [Body & pose tracking](/guide/body-tracking)).
-- **Hands** → `create_hand_gesture_bus` (publishes stable gesture channels) →
-  `create_hand_hologram`, `create_hand_ableton_mapper`.
-- **Segmentation** → feed the mask or `person_rgba` into any compositing chain.
-
-## Ready-made recipes
-
-Three browsable templates ship in the [recipe gallery](/guide/recipes) — say
-*"list recipes"*:
-
-- **Pose Skeleton (MediaPipe)** — the stick-figure skeleton from a live webcam.
-- **MediaPipe Body Dots** — glowing dots tracking every joint.
-- **MediaPipe Face Overlay** — a dot-cloud over live video from the face
-  landmarks.
-
-Each expects the plugin loaded; point its Select CHOP at the matching adapter's
-output.
-
-## See also
-
-- [Body & pose tracking](/guide/body-tracking) — the consumer-side guide and the
-  camera/first-run walkthrough.
-- [Camera & motion reactive](/guide/prompt-cookbook#camera-motion-reactive) in the
-  prompt cookbook.