DCC-MCP Public Catalog

The DCC-MCP catalog is a community-maintained registry of adapters and skill packs for the DCC-MCP ecosystem (issue #774).

Catalog File Format

dcc-mcp-catalog.yml in the repository root:

yaml

version: "1"
entries:
  - name: dcc-mcp-maya-skills
    description: "Official Maya skill pack for DCC-MCP"
    dcc: [maya]
    url: "https://github.com/example/dcc-mcp-maya-skills"
    issues_url: "https://github.com/example/dcc-mcp-maya-skills/issues"
    tags: [skills, maya, official]

  - name: dcc-mcp-blender-skills
    description: "Community Blender skill pack"
    dcc: [blender]
    url: "https://github.com/example/dcc-mcp-blender-skills"
    issues_url: "https://github.com/example/dcc-mcp-blender-skills/issues"
    tags: [skills, blender, community]

  - name: dcc-mcp-houdini-adapter
    description: "Houdini DCC adapter for DCC-MCP"
    dcc: [houdini]
    url: "https://github.com/example/dcc-mcp-houdini"
    issues_url: "https://github.com/example/dcc-mcp-houdini/issues"
    tags: [adapter, houdini, official]

Entry Fields

Field	Required	Type	Description
`name`	✅	string	Unique identifier (kebab-case recommended)
`description`	✅	string	One-sentence human-readable description
`dcc`	✅	list[string]	Supported DCC types (e.g. `[maya, blender]`)
`url`	✅	string	Repository or documentation URL
`issues_url`	❌	string	Canonical public GitHub issues URL; required for automatic Finding v1 routing
`tags`	❌	list[string]	Searchable tags (e.g. `skills`, `adapter`, `official`, `community`)

CLI Usage

Adapter installation and dcc-mcp-cli dcc-types use the verified installation catalog, which refreshes independently of CLI releases. The server catalog commands below remain discovery interfaces and do not perform this installation-specific refresh.

bash

# Search by keyword (matches name, description, DCC type, or tag)
dcc-mcp-server catalog search --query maya

# Search with no query → list all entries
dcc-mcp-server catalog search

# Describe a specific entry by exact name
dcc-mcp-server catalog describe --name dcc-mcp-maya-skills

Output is JSON-formatted for easy parsing.

Adobe debug plugin links

Adobe UXP and CEP adapters may declare an install.adobe block. The catalog stores only product metadata and adapter-relative paths; the operator supplies the source bridge and Adobe debug root at install time. For Internal profiles, keep this block in an approved catalog overlay rather than publishing local workstation paths:

yaml

install:
  type: pip
  pip_package: dcc-mcp-premiere
  adobe:
    product: premierepro
    extensionType: uxp
    plugin_id: com.adobepy.bridge.premiere
    manifest_path: manifest.json

Select that overlay with DCC_MCP_CATALOG_PATH or --catalog:

powershell

$env:DCC_MCP_CATALOG_PATH = 'F:\studio\catalog\dcc-mcp-internal.yml'
dcc-mcp-cli install --dcc-type premiere `
  --plugin-source F:\studio\artifacts\premiere-uxp-bridge `
  --adobe-debug-root F:\studio\adobe-debug `
  --execute

The same values can be provided through DCC_MCP_PLUGIN_SOURCE and DCC_MCP_ADOBE_DEBUG_ROOT, which is useful for Internal deployment profiles. The CLI creates an idempotent directory link, refuses to replace an existing non-link or link to a different source, verifies the declared manifest, and rolls the link back if a later install step fails. A successful local install still requires the Adobe host to be restarted or reloaded and then verified through dcc-mcp-cli list and the adapter's Skill discovery.

Adobe debug links are intended for development and Internal deployment profiles. Public or production distribution should use the adapter's packaged host-extension workflow.

MCP Resource Usage

The gateway publishes the catalog as MCP resources (#813 phase 2). Read them via resources/read:

python

# Full index, optional ?query=... keyword filter
result = client.resources_read("gateway://catalog?query=blender")
# Returns: { "total": N, "query": "blender", "entries": [{"name": "...", "description": "...", "dcc": [...], "url": "...", "tags": [...]}] }

# Single entry by exact name
result = client.resources_read("gateway://catalog/dcc-mcp-blender-skills")
# Returns: single entry, or `-32002` error if not found

Opt-in Documentation Connectors

Catalog entries can also point at read-only documentation MCP servers. These entries are discovery hints only; they do not auto-enable remote connectors on gateway startup.

Autodesk Product Help is modeled as a separate documentation backend, not as a Maya, Houdini, Photoshop, or pipeline adapter:

json

{
  "mcpServers": {
    "autodesk-product-help": {
      "url": "https://developer.api.autodesk.com/knowledge/public/v1/mcp"
    }
  }
}

Use tags: [docs, autodesk, read-only, infrastructure] for this connector. Keep documentation lookups separate from pipeline / shotgrid searches so production-tracking tools do not compete with product-help results.

Studio note: treat public documentation MCP servers as optional internet dependencies. Autodesk Product Help is suitable for best-effort reference lookup, but studios that require offline operation, pinned documentation, or formal service guarantees should keep it disabled and route agents to approved internal docs instead.

Custom Catalog Path

Override the default dcc-mcp-catalog.yml location:

bash

DCC_MCP_CATALOG_PATH=/path/to/my-catalog.yml dcc-mcp-server ...

Or set programmatically before calling the gateway tools.

Search Behavior

Case-insensitive substring match on name, description, dcc, and tags
Empty query returns all entries
describe requires an exact name match (case-sensitive)

DCC-MCP Public Catalog ​

Catalog File Format ​

Entry Fields ​

CLI Usage ​

Adobe debug plugin links ​

MCP Resource Usage ​

Opt-in Documentation Connectors ​

Custom Catalog Path ​

Search Behavior ​

See also ​