ZBrush adapter for the DCC Model Context Protocol (MCP) ecosystem — embedded Python SDK + optional socket bridge
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"dcc-mcp-zbrush","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# dcc-mcp-zbrush <p align="center"> <img src="docs/assets/dcc-mcp-zbrush.svg" alt="DCC-MCP · ZBRUSH" width="600"> </p> <!-- dcc-mcp-coverage-pointer:start --> <!-- Generated from dcc-mcp-catalog.yml by scripts/generate_adapter_pointer.py in dcc-mcp/dcc-mcp-core. Do not edit by hand. --> ## Part of the DCC-MCP host matrix **dcc-mcp-zbrush** — ZBrush adapter for DCC-MCP. It is one of **48 host adapters** in the DCC-MCP catalog. Every adapter speaks the same MCP protocol and builds on the same core runtime contract; each one exposes the tools its own host needs on top of that. - [All host adapters and install metadata](https://dcc-mcp.github.io/ecosystem) - [Host matrix on the core README](https://github.com/dcc-mcp/dcc-mcp-core#readme) - [Showcase](https://dcc-mcp.github.io/showcase) This block is generated from the catalog entry in [`dcc-mcp-catalog.yml`](https://github.com/dcc-mcp/dcc-mcp-core/blob/main/dcc-mcp-catalog.yml). Re-run the generator after changing the catalog. <!-- dcc-mcp-coverage-pointer:end --> ## Agent workflow AI agents should use the shared gateway through `dcc-mcp-cli`; IDE users may continue to use the MCP endpoint. Prefer typed skills and tools over raw scripts. ### Install or update the CLI `dcc-mcp-cli` is the preferred control path for every shell-capable agent. If it is missing, ask the user before installing the latest official release: ```bash # Linux/macOS curl -fsSL https://raw.githubusercontent.com/dcc-mcp/dcc-mcp-core/main/scripts/install-cli.sh | sh # Windows PowerShell powershell -ExecutionPolicy Bypass -c "irm https://raw.githubusercontent.com/dcc-mcp/dcc-mcp-core/main/scripts/install-cli.ps1 | iex" ``` Keep an official build current through the release manifest: ```bash dcc-mcp-cli update check dcc-mcp-cli update apply ``` `update apply` downloads and stages the latest CLI for the next launch. It does not update a running `dcc-mcp-server`; update that server in its own environment. ```bash dcc-mcp-cli dcc-types …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.