Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.
日本語の概要は準備中です。原文の説明を表示しています。
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 gates, and the local-only compliance story. Read this before writing any submission deliverable.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
The "Codex marketplace" is the Anthropic Connectors Directory, surfaced in Codex Desktop at Settings → Extensions → Browse extensions ("Anthropic-reviewed tools"). There are two submission paths with separate forms — picking the wrong one wastes a ~2-week review cycle.
| Path | For | tdmcp? |
|---|---|---|
| Remote MCP server (internet-hosted, OAuth 2.0) → MCP Directory form | SaaS-style connectors Codex reaches over the network | NO |
| Desktop Extension (local MCP server bundled as MCPB) → Desktop extension form | Local servers that run on the user's machine | YES |
Why local: tdmcp is a Node/stdio server that talks to a Python bridge running
inside TouchDesigner at 127.0.0.1:9980. It cannot be hosted remotely — it must
run next to TD on the artist's machine. So OAuth/hosting requirements do not
apply; ignore them. Submit via the Desktop extension form (linked from the
official submission docs page).
.dxtwas renamed to.mcpb(MCP Bundle). Existing.dxtstill installs, but new submissions should ship.mcpb. See themcpb-bundleskill.
| Gate | Requirement | tdmcp status |
|---|---|---|
| Privacy policy | Present + complete. Missing = immediate rejection. | TODO — docs-author writes it (local-only ⇒ short) |
| Tool annotations | Every tool has safety hints (readOnlyHint/destructiveHint). Missing = ~30% of all rejections. | PASS — all tools annotated (verified in src/tools/**) |
| Production-ready | Not beta. Stable, versioned, installable. | PASS — v0.3.0 on npm + MCP registry |
| Public docs URL | Setup + usage docs. | PASS — https://pantani.github.io/tdmcp/ |
| Data-handling statement | What data is handled and where it goes. | TODO — trivial (see below) |
| Branding | Logo / icon. | PASS — docs/public/logo-400.png (400×400) + favicon |
| Installable bundle | A valid .mcpb. | TODO — bundle-engineer migrates .dxt→.mcpb |
tdmcp's compliance answers are simple because of what it is — state it plainly:
127.0.0.1:9980 (configurable host/port). No other network egress.9980; for untrusted networks the user sets TDMCP_BRIDGE_TOKEN /
TDMCP_BRIDGE_ALLOW_EXEC=0 (already documented in the architecture docs).This is the basis for both the privacy policy page and the form's data/compliance fields.
For each field: the canonical answer or who drafts it. Known repo facts are filled.
| Field | Answer / source |
|---|---|
| Name | tdmcp |
| Display name | TouchDesigner (tdmcp) (from dxt/manifest.json) |
| Tagline (one-liner) | docs-author — reuse docs/index.md hero |
| Description | docs-author — reuse what-is-tdmcp + README; mention 100+ tools, knowledge base, create→verify→preview |
| Use cases | docs-author — VJ/live audiovisual, generative art, audio-reactive, projection mapping (see prompt-cookbook) |
| Category | Creative / media tools |
| Transport | stdio (Codex Desktop spawns the local server) |
| Auth | None (local) |
| Tools list + annotations | architect derives from src/tools/**; each tool's title/readOnlyHint/destructiveHint |
| Data handling / compliance | the local-only story above |
| Privacy policy URL | the new page docs-author publishes (e.g. https://pantani.github.io/tdmcp/privacy) |
| Public docs URL | https://pantani.github.io/tdmcp/ |
| Repo | https://github.com/Pantani/tdmcp |
| npm | @dpantani/tdmcp |
| MCP registry id | io.github.Pantani/tdmcp |
| License | MIT (verify LICENSE) |
| Logo / branding | docs/public/logo-400.png, favicon |
| Bundle | tdmcp.mcpb (from the migrated build) |
| Support channel | NEEDS HUMAN INPUT — GitHub Issues URL is the likely answer; confirm |
| Test account credentials | NEEDS HUMAN INPUT — likely N/A (no auth); note "local tool, no account" |
| Production-ready confirmation | Yes — v0.3.0 |
io.github.Pantani/tdmcp, active) is the open registry —
already done, feeds PulseMCP etc. It is not the Anthropic directory.desktopextensions.com and awesome-* lists are community discovery, not the
official directory.まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).
日本語の概要は準備中です。原文の説明を表示しています。
Reference for how BDB structures autonomous software engineering work — the seven-node dispatcher graph (Architect, TechLead, UI/UX, Engineering, Media/EventTech, Reviewer, Shipping) that /startcycle-graph actually runs. Use when you need the high-level lifecycle framing without inventing your own process.
日本語の概要は準備中です。原文の説明を表示しています。
Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling.
日本語の概要は準備中です。原文の説明を表示しています。
Harness patterns for coding agents — memory, permissions, context engineering, delegation, skills, hooks, bootstrap.
日本語の概要は準備中です。原文の説明を表示しています。
agenttrail: live map of a multi-agent build in the browser: which plan component is being worked on, by which agent or harness, what is done and what is stuck. Use when a multi-agent pipeline starts (/startcycle, /startcycle-graph, /teamwork-preview) or after a plan-canvas approve, when the user asks to see what the agents are doing ("live map", "build board", "who is running now"), or by yourself whenever a multi-agent run is under way — no user prompt needed.
日本語の概要は準備中です。原文の説明を表示しています。