connectors-directory-spec
Provides submission guidelines for MCPB-based Claude Desktop Extensions. Clarifies path decisions and local-only compliance.
Install
mkdir -p .claude/skills/connectors-directory-spec && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13412" && unzip -o skill.zip -d .claude/skills/connectors-directory-spec && rm skill.zipInstalls to .claude/skills/connectors-directory-spec
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Authoritative reference for submitting tdmcp to the Anthropic Connectors Directory as a Claude 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.Key capabilities
- →Determine the correct submission path for tdmcp to the Anthropic Connectors Directory
- →Identify rejection-causing gates for submissions
- →Provide canonical answers for Desktop extension form fields
- →Outline the local-only compliance story for tdmcp
- →Distinguish tdmcp submission from other registries and community lists
How it works
The skill provides a reference for submitting tdmcp as a Claude Desktop Extension (MCPB), detailing the correct submission path, approval gates, form fields, and compliance narrative.
Inputs & outputs
When to use connectors-directory-spec
- →Submit extension to Anthropic
- →Check compliance requirements
- →Decide between remote vs desktop path
About this skill
Anthropic Connectors Directory — tdmcp submission spec
The "Claude marketplace" is the Anthropic Connectors Directory, surfaced in Claude 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)
| Path | For | tdmcp? |
|---|---|---|
| Remote MCP server (internet-hosted, OAuth 2.0) → MCP Directory form | SaaS-style connectors Claude 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.
Approval gates (these cause rejection)
| 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 |
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 (Claude/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 setsTDMCP_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.
| 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 (Claude 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 |
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.comandawesome-*lists are community discovery, not the official directory.
Sources
- Submitting to the Connectors Directory — claude.com/docs/connectors/building/submission
- Connectors Directory FAQ — support.claude.com (article 11596036)
- Desktop Extensions — anthropic.com/engineering/desktop-extensions
When not to use it
- →When submitting a remote MCP server (SaaS-style connector)
- →When seeking community discovery for tdmcp
- →When the submission is not for a Claude Desktop Extension (MCPB)
Limitations
- →Focuses specifically on tdmcp as a Desktop Extension (MCPB).
- →Does not cover submission for Remote MCP servers.
- →Requires manual action for TODO items like privacy policy and bundle migration.
How it compares
This skill provides specific, authoritative guidance for tdmcp's submission to the Anthropic Connectors Directory, unlike general submission guidelines or community resources.
Compared to similar skills
connectors-directory-spec side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| connectors-directory-spec (this skill) | 0 | 2mo | No flags | Intermediate |
| release-rust-srec | 0 | 2mo | Review | Advanced |
| version-bump | 0 | 1mo | No flags | Beginner |
| release | 0 | 5mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by Pantani
View all by Pantani →You might also like
release-rust-srec
hua0512
Prepare a new rust-srec application release end to end — pick the next semver version, bump the workspace version, promote the staged unreleased.md notes into versioned en+zh release-notes pages, reset unreleased, refresh the release-notes index/sidebar/GitHub-body, and emit the rust-srec-vX.Y.Z tag
version-bump
sequra
Bump the seQura WooCommerce plugin version across the two coupled locations (sequra/sequra.php header and sequra/readme.txt stable tag + changelog), keeping them in sync and writing the changelog entry. Use when releasing a new plugin version.
release
akiojin
Execute the release workflow when the user asks `release` or `/release`: sync develop, update version/changelog, create `chore(release)` commit, collect closing issues, create develop->main release PR, and verify release/publish artifacts.
git-deploy
ClaudioCeppi83
Skill experta para limpiar código, documentar, crear y sincronizar repositorios usando el MCP de GitHub con estándares de producción.
docs
matteocervelli
Build and publish project documentation — Starlight (Astro) for apps, markdown for libraries/services, with IT+EN i18n and VPS deploy. Use when writing user guides, scaffolding a docs site, or publishing docs. Trigger on "write docs", "documentation site", "user guide", "publish docs".
doc-cli-usage
BA-CalderonMorales
Use the Rust-based documentation CLI for common tasks.