Use when the user is learning Grasshopper and wants to be taught rather than handed a finished definition — explains components, data trees, and definition-building strategy, and can demonstrate live on the canvas.
Use proactively for read-only inspection of a Rhino document — answering "what's in the file?", "where is X?", or "what does this look like?" without modifying geometry.
Use proactively for tasks that require creating, editing, or inspecting geometry inside Rhino3D. Hands-on modeling assistant that drives Rhino through the rhino MCP server.
Use for organizing a Rhino document — layer structure, object naming, grouping, layer materials, and tidying up sloppy files. Does not create or edit geometry.
Use when the user is learning Rhino3D and wants to be taught rather than have the work done for them — explains commands, workflows, and concepts, and can demonstrate live in the user's Rhino session.
Start a single Rhino MCP session. Accepts a version argument (e.g. 8, WIP) and an optional explicit port. Walks forward from 10500 to pick a free port if none was given. On macOS this opens a new document in the running Rhino; on Windows it launches a new Rhino process. Use when the user asks to start a Rhino MCP…
Spin up N Rhino MCP sessions in parallel and fan out one agent per Rhino. Use when the user wants multiple Rhinos running simultaneously with each agent driving its own — e.g. "spawn 3 agents and have each launch Rhino", "run 5 Rhino tasks in parallel". For a single Rhino, use /launch-rhino instead.
Python MCP server (30 compound tools, 328 granular tools in --full mode) for controlling DaVinci Resolve via its Scripting API. See AGENTS.md for full project overview and the README for the 109-action kernel coverage map.
This document gives AI assistants the context needed to use the DaVinci Resolve MCP server effectively. It covers the tool landscape, page prerequisites, common workflow patterns, error recovery, and known gotchas.
Authoritative reference for submitting tdmcp to the Anthropic Connectors Directory as a Codex Desktop Extension (MCPB). Use whenever drafting, checking, or fixing the submission — it defines the two submission paths, why tdmcp is a Desktop Extension (never a remote connector), every form field, the rejection-causing…
How to migrate the tdmcp Codex Desktop bundle from legacy .dxt to .mcpb (MCP Bundle) and keep it building — covers the manifest schema (verify against the installed packer, never hardcode), the build-dxt.mjs packer/zip-fallback flow, the npm scripts, and the full .dxt→.mcpb reference sweep across docs and scripts. Use…
Verification methodology and gate checklist for the tdmcp Connectors Directory submission — run the docs build, build and inspect the .mcpb bundle, sweep for stale .dxt references, and cross-check the form-answer draft against the real requirements. Use to validate the submission package before a human submits, by…
Implement ONE tdmcp tool from a spec — the canonical file pattern (Zod schema + …Impl + register… ToolRegistrar), a bridge Python payload via buildPayloadScript, and an offline msw unit test — touching only new files, never shared registries. Use when coding/implementing/writing a tdmcp tool, generator, effect…
Design a tdmcp feature into an implementable spec before any code is written — choose the layer, define the Zod input schema, lay out the TD network topology, plan the bridge/Python approach, sketch a UI wireframe when relevant, and list probe-first risks + the test plan. Use whenever a tdmcp feature idea needs a…
Wire builders' isolated tdmcp tool files into the shared registries, CLI, and docs as a single writer, conflict-safe, and confirm a green typecheck + build. Use when integrating/wiring/registering new tdmcp tools, adding their CLI commands, resolving build breaks after parallel feature work, or merging several…
Quality-assure integrated tdmcp features: run the four PR gates + recipe/bridge tests, cross-boundary coherence checks (tool schema↔CLI↔docs↔registry, operator↔createable, bridge↔client), and live TouchDesigner validation (preview + post-cook error check) when the bridge is reachable. Use when…
Release tdmcp: write the Keep-a-Changelog entry, bump the SemVer version across every manifest, then (autonomously, per project policy) commit, tag, and push — gated on a td-qa PASS, with hard git safety rails. Use when releasing/shipping/cutting a tdmcp version, writing the CHANGELOG, bumping the version, or tagging…