Skip to main content

dcc-mcp-mobu

DCC-MCP · MOBU

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:

# 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:

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.

dcc-mcp-cli dcc-types
dcc-mcp-cli list
dcc-mcp-cli search --query "<task>" --dcc-type mobu
dcc-mcp-cli describe <tool-slug>
dcc-mcp-cli call <tool-slug> --json '{"key":"value"}'

dcc-types reports release-catalog support; list reports live sessions. If a tool belongs to an inactive progressive skill, call dcc-mcp-cli load-skill <skill-name> --dcc-type mobu before retrying. For post-task improvement, attach a stable session id with --meta-json, query dcc-mcp-cli stats --range 24h --session-id <task-id>, then pass the bounded evidence to the review_skill_improvement prompt from dcc-mcp-skills-creator.

An MCP adapter for Autodesk MotionBuilder, built on dcc-mcp-core.

It exposes a small, typed scene-management surface and runs MotionBuilder API calls on the application's UI thread.

Install

Follow the agent-first installation and lifecycle guide. It uses MotionBuilder's exact mobupy, stages a receipted Startup hook, verifies a typed host ping, and provides standard install/status/verify/uninstall/upgrade commands. A system-pip install is not a MotionBuilder installation.

Each adapter instance uses an OS-assigned port and registers it for CLI discovery. Connect through the stable gateway at http://127.0.0.1:9765/mcp; set DCC_MCP_MOBU_PORT only when a fixed direct endpoint is required.

Tools

  • mobu-scene.inspect_scene
  • mobu-scene.list_models
  • mobu-scene.save_scene

save_scene is destructive and requires an explicit absolute .fbx path.

Development

python -m pip install -e ".[dev]"
pytest
ruff check src tests tools
ruff format --check src tests tools
python tools/lint_skills.py
python -m build

License

MIT

Metadata

Release files for dcc-mcp-mobu 0.4.0

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

Source distribution (sdist)

Source distribution for dcc-mcp-mobu 0.4.0
File Size Uploaded
dcc_mcp_mobu-0.4.0.tar.gz 24.0 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for dcc-mcp-mobu 0.4.0
File Interpreter ABI Platform
dcc_mcp_mobu-0.4.0-py3-none-any.whl Python 3 none any Details

Total release size: 44.1 kB

Release files / dcc_mcp_mobu-0.4.0.tar.gz

Download URL dcc_mcp_mobu-0.4.0.tar.gz
Size 24.0 kB
Tags Source
SHA-256 checksum
How to use checksums
3ede68028ade1378076b72342dfe4882444c787261cfcb1b9ec9752f205eff2c
BLAKE2b-256 checksum
How to use checksums
e5b0c719a5e571ed61fad8d3d2022b81711978062e5fe3a695cf1765d85aaf0e
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 Aug 26, 2026.

Transparency log

Release files / dcc_mcp_mobu-0.4.0-py3-none-any.whl

Download URL dcc_mcp_mobu-0.4.0-py3-none-any.whl
Size 20.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
cc7971fc7975a1db99c0b5e0ee93a342d842e6fdf34a286b6f086c3746363b13
BLAKE2b-256 checksum
How to use checksums
12540f3298bd9e11d9ae4678fe1ecde5e1e19bd99cf8812a286b8bb43c1388e2
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 Aug 26, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.4.0 This release

2 release files

0.3.0

2 release files

0.2.0

2 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