maya-dev

name	maya-dev
description	Pipeline stage — development workflow helpers for authoring Maya tools inside a live Maya session. Use to attach a local Python project, hot-reload its modules, run entrypoints or scripts, start debugpy, and capture Maya UI evidence, automate Qt controls, and return stable refs while iterating with an agent. Not for general scene editing: use domain skills first.
license	MIT
allowed-tools	Bash Read
metadata	{"dcc-mcp":{"dcc":"maya","layer":"domain","stage":"pipeline","version":"0.1.0","tags":["maya","development","debug","hot-reload","ui-capture"],"search-hint":"develop maya tools, attach python project, hot reload modules, run\nproject entrypoint, debugpy attach, capture maya ui screenshot, script\nstdout stderr traceback diagnostics","tools":"tools.yaml","groups":"groups.yaml"}}

maya-dev (Pipeline stage)

Development workflow helpers for agents working on Maya Python tools in a live Maya session. The intended loop is:

1. attach_project once for the project root.
2. Edit files in the normal workspace.
3. run_check or reload_modules + run_entrypoint.
4. Inspect the concise summary, artifact refs, session events, and optional UI screenshot.

Set DCC_MCP_MAYA_DEV_ROOTS to a path-list of trusted roots when a studio wants to restrict which local projects can be attached.

Scripts

• attach_project — Add a development project root to Maya's sys.path
• reload_modules — Purge or reload modules belonging to the attached project
• run_entrypoint — Import and call a Python entrypoint from the project
• run_script — Run a project-local .py script with captured output
• start_debugpy — Start a debugpy listener in the Maya process with attach metadata
• capture_ui — Capture the Maya main window or a named Qt widget as PNG
• ui_snapshot / ui_find / ui_action — Inspect and operate Maya Qt UI controls, with optional action evidence artifacts
• make_node_ref / resolve_node_ref — Build and resolve stable Maya node references
• run_check — Reload, run an entrypoint, capture diagnostics/artifacts/session events, optionally grab UI