marketplace-publish-extension

Marketplace Publish Extension

CLI-First Control Path

For marketplace and live-DCC operations, use the dcc-mcp skill and dcc-mcp-cli whenever shell access is available. Its consent-gated install and update check → update apply contract is the single source of truth; do not invent a package-local CLI bootstrap path.

Publish (register or update) a DCC-MCP Skill, bundle, or Agent Plugin package to a marketplace catalog (marketplace.json).

Prefer the CLI for local and CI publishing:

dcc-mcp-cli marketplace pack ./my-extension --out dist/
dcc-mcp-cli marketplace publish ./my-extension \
  --catalog ./marketplace.json \
  --install-url https://github.com/<owner>/<repo>/releases/download/v0.1.0/my-extension.zip \
  --sha256 sha256:<digest> \
  --min-core-version 0.19.0 \
  --skill-root skill/my-extension

Tools

marketplace_publish_extension__publish

Scan an extension directory, build a CatalogEntry, and upsert it into the target marketplace.json (local file or remote URL-backed file). When the catalog source is a local git repository the tool can optionally commit and push the change.

Prerequisites

• dcc-mcp-core installed
• Write access to the target marketplace catalog path
• Git (if using commit+push mode)

Release Gate — Python 3.7

• Verify py37 wheels exist and py37 CI is green before publishing.
• py37-lite fallback wheels do NOT satisfy the release gate. Native py37 builds are an LTS requirement with no automatic calendar expiry.
• Confirm requires-python = ">=3.7" in pyproject.toml is unchanged.
• Removing native py37 requires an accepted superseding ADR, a major release, and at least 180 days of notice.

Workflow

1. Point the tool at a local Skill directory containing SKILL.md, or an Agent Plugin directory containing root plugin.json and skills/*/SKILL.md.
2. The CLI reads Skill frontmatter or Agent Plugin manifest metadata.
3. Additional CLI-supplied fields (install url, ref, skill roots, tags, maintainer, icon, and showcase) are merged in. Use a repository-relative 16:9 PNG, JPEG, WebP, AVIF, or animated GIF path; the marketplace resolves it at the pinned 40-character Git revision.
4. A CatalogEntry is built and upserted into the target marketplace.json. New catalogs use the v1 skills layout and preserve v1-only fields when an existing entry is updated.
5. If the catalog source is a git repo and --commit is passed, the updated marketplace.json is committed and pushed.