Skip to main content

dcc-mcp-server-bin — PyPI distribution blueprint

Status: blueprint — packaging files are wired but no PyPI release has shipped yet. Tracked in issue #1002 (deliverable 3 of RFC #998 Addendum A.7).

This directory packages the crates/dcc-mcp-server Rust binary as a platform-specific binary-only PyPI wheel, following the same pattern as ruff, uv, cmake, and pyright. The result is a single pip install dcc-mcp-server that drops the gateway / sidecar / translate CLI onto PATH for Python 3.7+ regardless of which DCC the user runs.

Why a separate PyPI package?

dcc-mcp-core is a PyO3 wheel — its _core.so is loaded into the host Python interpreter (mayapy / blender-python / hython). The sidecar binary, by contrast, is meant to run as its own OS process; bundling it into dcc-mcp-core would couple two artefacts with very different release cadences and ABI matrices. Splitting them is the standard pattern.

Package Distributes Audience
dcc-mcp-core (existing) PyO3 wheel (_core.so + Python facade) Skill authors, plugin/addon code running inside a DCC interpreter
dcc-mcp-server (this dir) platform-specific Python 3.7+ binary wheels Operators, sidecar spawners, anyone who wants a standalone gateway
dcc-mcp-<dcc> (each repo) pure-Python plugin/addon glue DCC plugin loaders (userSetup.py, addon register(), …)

Layout

pkg/dcc-mcp-server-bin/
├── pyproject.toml              ← maturin config, bindings = "bin"
├── python/
│   └── dcc_mcp_server/
│       └── __init__.py         ← binary_path() helper for subprocess spawn
└── README.md                   ← this file

The Rust source is not duplicated here — pyproject.toml sets manifest-path = "../../crates/dcc-mcp-server/Cargo.toml" so maturin builds the existing workspace crate.

Local build

# Build a wheel for the current platform / Python
cd pkg/dcc-mcp-server-bin/
vx pip install maturin
vx maturin build --release

# Resulting wheel lands in ../../target/wheels/dcc_mcp_server-*.whl
vx pip install ../../target/wheels/dcc_mcp_server-*.whl
dcc-mcp-server --help

The wheel uses maturin bindings = "bin", so it does not load a Python extension module and has no CPython ABI dependency. Its metadata deliberately declares Requires-Python: >=3.7 so embedded Python 3.7 hosts such as Maya 2022 can install it directly.

Cross-platform CI release

The new .github/workflows/release-server-binary.yml workflow (also part of this PR) builds wheels for:

OS Arch Tag
manylinux x86_64 manylinux_2_28_x86_64
manylinux aarch64 manylinux_2_28_aarch64
Windows x86_64 win_amd64
Windows arm64 win_arm64
macOS x86_64 macosx_11_0_x86_64
macOS arm64 macosx_11_0_arm64

The workflow triggers on tags matching dcc-mcp-server-v* so it stays independent of the existing dcc-mcp-core release cycle.

Usage from a DCC plugin

# In a Maya plugin / Blender addon, after `pip install dcc-mcp-server`:
import os, subprocess
from dcc_mcp_server import binary_path

_proc = subprocess.Popen([
    str(binary_path()),
    "sidecar",
    "--dcc", "maya",
    "--host-rpc", "commandport://127.0.0.1:6000",
    "--watch-pid", str(os.getpid()),
])

That's the entire plugin → sidecar wiring. Per-DCC HostRpcClient implementations land in their respective adapter repos.

Release files for dcc-mcp-server 0.20.26

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distributions (wheels)

Table of built distributions (wheels) for dcc-mcp-server 0.20.26
File Interpreter ABI Platform
dcc_mcp_server-0.20.26-py3-none-win_amd64.whl Python 3 none Windows x86-64 Details
dcc_mcp_server-0.20.26-py3-none-manylinux2014_x86_64.manylinux_2_17_x86_64.whl Python 3 none Linux glibc 2.17+ x86-64 Details
dcc_mcp_server-0.20.26-py3-none-macosx_10_12_universal2.macosx_10_12_x86_64.macosx_11_0_arm64.whl Python 3 none macOS 10.12+ x86-64, macOS 11.0+ ARM64, macOS 10.12+ universal2 (ARM64, x86-64) Details

Total release size: 77.9 MB

Release files / dcc_mcp_server-0.20.26-py3-none-win_amd64.whl

Download URL dcc_mcp_server-0.20.26-py3-none-win_amd64.whl
Size 19.5 MB
Tags Python 3 Windows x86-64
SHA-256 checksum
How to use checksums
97a3b96ed86b3d76ea1210a7771859a8462a65a57bf0a7fea6a232be7b69f2de
BLAKE2b-256 checksum
How to use checksums
05028f36772c1b2b2ceb92f4d82df7cdd00a2d78e92e946d3761d97c7955c14f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.

Transparency log

Release files / dcc_mcp_server-0.20.26-py3-none-manylinux2014_x86_64.manylinux_2_17_x86_64.whl

Download URL dcc_mcp_server-0.20.26-py3-none-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 19.9 MB
Tags Linux glibc 2.17+ x86-64 Python 3
SHA-256 checksum
How to use checksums
8a15ddf6fab1fbb285c44b1f01c9981cf7e7350af2de95115d43e39d0c61e438
BLAKE2b-256 checksum
How to use checksums
d42f653670885dcb315a1d3cb1d3db4f79376c3eb30b1b4dcd0fdbc5545d34bc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.

Transparency log

Release files / dcc_mcp_server-0.20.26-py3-none-macosx_10_12_universal2.macosx_10_12_x86_64.macosx_11_0_arm64.whl

Download URL dcc_mcp_server-0.20.26-py3-none-macosx_10_12_universal2.macosx_10_12_x86_64.macosx_11_0_arm64.whl
Size 38.5 MB
Tags Python 3 macOS 10.12+ universal2 (ARM64, x86-64) macOS 10.12+ x86-64 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
18c9961035cd6cd74146b38e1e54196b98502190fed0b79d1f4f26b458ec0563
BLAKE2b-256 checksum
How to use checksums
46c439bba4ce5dad628765c899a169c4ccc840f26ec832a4753f8785c7e87647
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.20.26 This release

3 release files

0.20.9

3 release files

0.20.8

3 release files

0.20.7

3 release files

0.20.6

3 release files

0.20.5

3 release files

0.20.4

3 release files

0.20.3

3 release files

0.20.2

3 release files

0.20.1

3 release files

0.20.0

3 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page