本文へ移動
cccskills
無料GitHub で公開

connectors-directory-spec

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.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md5.6 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Anthropic Connectors Directory — tdmcp submission spec

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 decision — tdmcp is a Desktop Extension (MCPB)

PathFortdmcp?
Remote MCP server (internet-hosted, OAuth 2.0) → MCP Directory formSaaS-style connectors Codex reaches over the networkNO
Desktop Extension (local MCP server bundled as MCPB) → Desktop extension formLocal servers that run on the user's machineYES

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).

.dxt was renamed to .mcpb (MCP Bundle). Existing .dxt still installs, but new submissions should ship .mcpb. See the mcpb-bundle skill.

Approval gates (these cause rejection)

GateRequirementtdmcp status
Privacy policyPresent + complete. Missing = immediate rejection.TODO — docs-author writes it (local-only ⇒ short)
Tool annotationsEvery tool has safety hints (readOnlyHint/destructiveHint). Missing = ~30% of all rejections.PASS — all tools annotated (verified in src/tools/**)
Production-readyNot beta. Stable, versioned, installable.PASS — v0.3.0 on npm + MCP registry
Public docs URLSetup + usage docs.PASS — https://pantani.github.io/tdmcp/
Data-handling statementWhat data is handled and where it goes.TODO — trivial (see below)
BrandingLogo / icon.PASS — docs/public/logo-400.png (400×400) + favicon
Installable bundleA valid .mcpb.TODO — bundle-engineer migrates .dxt→.mcpb

The local-only compliance story (reuse everywhere)

tdmcp's compliance answers are simple because of what it is — state it plainly:

  • Runs entirely on the user's machine. No accounts, no sign-in, no cloud.
  • The MCP server only makes HTTP calls to the user's own TouchDesigner bridge on 127.0.0.1:9980 (configurable host/port). No other network egress.
  • Collects no user data, no telemetry, no analytics, sends nothing to the author or any third party.
  • The user's AI client (Codex/Cursor/Codex) processes prompts under that client's privacy policy — tdmcp adds no data collection of its own.
  • Security note worth stating: the bridge executes Python inside TD and listens on 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.

Form field map (Desktop extension form)

For each field: the canonical answer or who drafts it. Known repo facts are filled.

FieldAnswer / source
Nametdmcp
Display nameTouchDesigner (tdmcp) (from dxt/manifest.json)
Tagline (one-liner)docs-author — reuse docs/index.md hero
Descriptiondocs-author — reuse what-is-tdmcp + README; mention 100+ tools, knowledge base, create→verify→preview
Use casesdocs-author — VJ/live audiovisual, generative art, audio-reactive, projection mapping (see prompt-cookbook)
CategoryCreative / media tools
Transportstdio (Codex Desktop spawns the local server)
AuthNone (local)
Tools list + annotationsarchitect derives from src/tools/**; each tool's title/readOnlyHint/destructiveHint
Data handling / compliancethe local-only story above
Privacy policy URLthe new page docs-author publishes (e.g. https://pantani.github.io/tdmcp/privacy)
Public docs URLhttps://pantani.github.io/tdmcp/
Repohttps://github.com/Pantani/tdmcp
npm@dpantani/tdmcp
MCP registry idio.github.Pantani/tdmcp
LicenseMIT (verify LICENSE)
Logo / brandingdocs/public/logo-400.png, favicon
Bundletdmcp.mcpb (from the migrated build)
Support channelNEEDS HUMAN INPUT — GitHub Issues URL is the likely answer; confirm
Test account credentialsNEEDS HUMAN INPUT — likely N/A (no auth); note "local tool, no account"
Production-ready confirmationYes — v0.3.0

Distinguish from what's already done

  • MCP Registry (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.

Sources

  • Submitting to the Connectors Directory — Codex.com/docs/connectors/building/submission
  • Connectors Directory FAQ — support.Codex.com (article 11596036)
  • Desktop Extensions — anthropic.com/engineering/desktop-extensions

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.

日本語の概要は準備中です。原文の説明を表示しています。

hybridlabor-api/aos62026年10月12日 更新

Use when a hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).

日本語の概要は準備中です。原文の説明を表示しています。

hybridlabor-api/aos62026年10月12日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

hybridlabor-api/aos62026年10月12日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

hybridlabor-api/aos62026年10月12日 更新

Harness patterns for coding agents — memory, permissions, context engineering, delegation, skills, hooks, bootstrap.

日本語の概要は準備中です。原文の説明を表示しています。

hybridlabor-api/aos62026年10月12日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

hybridlabor-api/aos62026年10月12日 更新

hybridlabor-api のスキルをすべて見る

このスキルの問題を報告する