Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

mcp-for-maya

PYPI · MCP-FOR-MAYA

Spatial awareness for AI agents in Autodesk Maya: scene checks, checkpoints, captures (Beta)

Available components

0 this week 93 Trust /100

Last scanned (4 hours ago)

Scores higher than 94% of PyPI servers

Category Design and Media

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 16 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to Xxx91n/mcp-for-maya). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 6 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability61
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 8413 tokens (~336/item across 25 items; 25 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (88% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 26 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 18 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
    • Stability: 0.97 → pass security
  • 17 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
    • Stability: pass → 0.97 functional
  • 16 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
    • Schema quality: 258 → 336 ▼ functional
    • Package version: 0.7.0 → 0.8.0 functional
  • 15 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
  • 8 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 22 Nov 2026 · Analysed pypi/mcp-for-maya@0.8.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo Xxx91n/mcp-for-maya
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Xxx91n/mcp-for-maya/.github/workflows/release.yml@refs/tags/v0.8.0
Rekor log index 3917265829
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:b62d590235e908f0883316326f0302b7dacc6509ac50c2e32b984fca24f5c731

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 16 packages
Packages resolved 16
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 25 exposed · ~7,272 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
add_session ~128

Manually add a Maya session at a specific host and port. Boundary: Disambiguated from list_sessions (report the sessions the SessionManager already discovered) and maya_setup_guide (diagnose and repair a connection) — add_session registers a host:port you already know. Use this when auto-discovery doesn't find your Maya session, or to connect to a Maya instance on a specific port.

NameTypeReqDescription
hoststring–The session host (default: "127.0.0.1")
portinteger–The session port number (default: 7001)
NameTypeReqDescription
hoststringyes–
maya_versionstring––
pidintegeryes–
portintegeryes–
scene_namestring––
scene_pathstring––
session_keystringyes–
userstringyes–

No examples provided.

asset_import ~329

Import a Poly Haven CC0 model into Maya (find ids via asset_search). Boundary: Disambiguated from asset_search (host-side id and metadata lookup that touches no Maya session) — asset_import is the mutating half and needs a live session to import into. Pipeline: host downloads FBX + textures from the Poly Haven whitelist (https-only, size caps, per-file md5 verify) into the platformdirs cache -> Maya imports the local FBX (explicit meters unit handling) -> texture maps auto-wire by PH naming convention (diff/albedo -> color sRGB; rough/metal -> Raw single-channel; nor_gl -> bump2d normal) -> polycount gate -> group as GRP_asset_<id> -> bbox/metadata report. Idempotent by default: a second call with the same asset_id reports the existing group instead of duplicating (force=True re-imports).

NameTypeReqDescription
allow_high_polycountboolean–Override the polycount guard (the override is written to the call record).
asset_idstringyesPoly Haven asset id (case-sensitive, e.g. 'Camera_01').
forceboolean–Re-import even when GRP_asset_<id> already exists.
max_polycountinteger–Face-count guard (default 100000); imports over the limit are deleted and rejected.
resolutionstring–Texture tier '1k' (default), '2k', '4k', '8k'.
session_key––Maya session key.
NameTypeReqDescription
resultstringyes–

No examples provided.

asset_search ~179

Search the Poly Haven CC0 asset index (host-side, no Maya needed). Boundary: Disambiguated from asset_import (downloads the asset into a live Maya scene and mutates it) — asset_search only resolves ids and metadata, so it needs no session and changes nothing. Queries https://api.polyhaven.com/assets and returns matching asset metadata. Read-only and idempotent - pure lookup.

NameTypeReqDescription
asset_typestring–"models" (default), "hdris", or "textures". Note: asset_import handles models only.
limitinteger–Result cap, 1-20 (default 20). total_count always reports the full match count.
querystring–Free-text search (matches id, name, categories, tags). Empty returns the unfiltered index page (up to limit).
NameTypeReqDescription
resultstringyes–

No examples provided.

camera_create ~162

Create a camera positioned for a specific shot type. Boundary: Disambiguated from camera_orbit (animates a turntable around a point over many frames) — camera_create frames one static shot and adds no animation. Supports the 8 built-in shot types: extreme_wide, wide, medium, close, extreme_close, over_shoulder, bird_eye, low_angle.

NameTypeReqDescription
azimuthnumber–Horizontal angle in degrees (default 30).
elevationnumber–Vertical angle in degrees (default 15).
namestring–Camera name.
session_key––Maya session key.
shot_typestring–Shot type (default "medium").
targetstringyesTarget object name to look at.
NameTypeReqDescription
resultstringyes–

No examples provided.

camera_orbit ~152

Create an orbiting camera with turntable animation around a point. Side effects: creates a new camera and animation curves in the scene and marks the scene dirty. Not idempotent — each call adds another camera. Requires an active Maya session. Boundary: Disambiguated from camera_create (static shot-type framing; use camera_orbit only when an animated orbit is needed).

NameTypeReqDescription
centerstringyesOrbit center as a JSON string "[x, y, z]".
framesinteger–Number of frames for one full orbit.
namestring–Camera name.
radiusnumber–Orbit radius in scene units.
session_key––Maya session key.
NameTypeReqDescription
resultstringyes–

No examples provided.

execute_code ~315

Execute arbitrary Python code in an active Maya session. Runs arbitrary code with full session privileges of the connected Maya process. Execution is irreversible and cannot be undone (modifications do not register an automatic undo chunk). The return value shape is governed by the result_type envelope parameter. Requires an established Maya session (discoverable via list_sessions). Under safe_mode (MAYA_MCP_SAFE_MODE, opt-in, default off) the code payload passes a deny-by-default allowlist checked on the parsed code before dispatch: imports outside the v1 roots (maya/math/json/re/collections/ itertools/functools/dataclasses/typing), denied builtins (eval/exec/open/__import__/getattr/setattr/...), __builtins__ references (any use of a denied name rejects, not just calls), dunder attribute access, and unparseable input are rejected with safe_mode_rejected naming the triggering rule id. Successful responses carry mode: "safe" on their structured payload. This catches slips, it is not a sandbox — code that passes still runs with full session privileges.

NameTypeReqDescription
codestringyesPython code to execute in Maya.
result_typestring–Return envelope handling for the execution result: - "NONE": Execute statements, don't capture result (returns None) - "JSON": Evaluate expression, JSON-encode result - "RAW": Evaluate expression, re…
session_key––Maya session key (optional if only one session exists).

No output schema declared.

No examples provided.

list_sessions ~194

List all active Maya sessions. Boundary: Disambiguated from add_session (register a host:port by hand) and maya_setup_guide (diagnose an empty result) — list_sessions only reports what is already connected. Returns a list of session information including: - session_key: Session key used to interact with tools and resources - host: Session host address - port: Session port number - pid: Maya process ID - user: Logged-in user - maya_version: Maya version string - scene_name: Current scene filename - scene_path: Full path to current scene Note: To detect new or removed sessions, clients should call this tool periodically (e.g., every 10-30 seconds) and compare results. The SessionManager automatically scans for new Maya sessions in the background. If this returns an empty list, call maya_setup_guide() for connection help.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

maya_setup_guide ~303

Maya connection setup guide and diagnostics. Boundary: Disambiguated from list_sessions (read the current session set) and add_session (attach a host:port you already know) — maya_setup_guide diagnoses and repairs the connection itself. Use this tool when list_sessions returns empty or when setting up Maya MCP for the first time. Provides platform-aware diagnostics, auto-installation of userSetup.py, and step-by-step fallback instructions.

NameTypeReqDescription
actionstring–What to do: - "diagnose": Run connection diagnostics and return status - "install": Merge the managed block into userSetup.py. Existing files without the block require a second call with confirm=…
confirmboolean–Required to write into an existing userSetup.py that has no mcp-for-maya managed block (first install call is dry-run).
dry_runboolean–Preview the install: return the proposed block without writing anything.
portinteger–Maya command port number (default: 7001)
remove_empty_fileboolean–On uninstall, delete the file when it only contained the managed block.
target_version––Specific Maya version (e.g., "2024"). If None, targets all detected versions.

Structured output declared, but exposes no named fields.

No examples provided.

scene_aesthetics ~242

Score the scene's look on 5 design dimensions. Scores the scene's look across 5 design dimensions: 1. Color Theory: 60-30-10 rule, temperature balance, harmony type, saturation variety, contrast 2. Spatial Composition: golden ratio proportions, rule-of-thirds alignment, visual weight balance 3. Proportion & Scale: human ergonomic reference, size hierarchy (hero/secondary/tertiary) 4. Lighting Quality: layer composition (key/fill/rim/accent), color temperature consistency 5. Visual Flow: sight line clarity, circulation paths, visual rhythm patterns Returns an overall score (0-100) with grade (S/A/B/C/D/F) and improvement suggestions. Boundary: Disambiguated from scene_review (scene_aesthetics evaluates visual design theory and artistic harmony in depth, while scene_review is a broad check of the whole scene).

NameTypeReqDescription
formatstring–Output format - "json" (default) or "cos" (a short score summary: the overall score, each dimension's score, and the suggestions).
session_key––Maya session key.
NameTypeReqDescription
resultstringyes–

No examples provided.

scene_assert ~227

Verify scene state matches expected values. Use this after modifications to confirm the scene is in the desired state. This is the check step (the last of ICEV's four steps). bbox_min/bbox_max compare world-axis boxes built from each shape's own box, transformed once: a rotated parent no longer widens them layer by layer, but geometry that does not fill its own box (an L-shape, a character mesh) can still read up to one axis-alignment too wide. Boundary: Disambiguated from scene_validate (checks relational spatial constraints across zones rather than exact expected values for named objects).

NameTypeReqDescription
expectationsstringyesJSON string defining expected state. Format: {"obj_name": {"position": [x,y,z], "bbox_max": [x,y,z], ...}} Supported properties: position, bbox_max, bbox_min, exists, material. Position and bbox valu…
formatstring–Output format - "cos" or "json".
session_key––Maya session key.
NameTypeReqDescription
resultstringyes–

No examples provided.

scene_checkpoint ~241

Save the current scene to a `.ma` file on disk under checkpoints/. Boundary: Disambiguated from scene_checkpoint_list (list the checkpoint files already written) and scene_rollback (open one and point the scene at it) — scene_checkpoint is the save half. Writes a self-contained .ma into a checkpoints/ directory next to the scene file. A scene that was never saved to disk needs an explicit name, and its temporary checkpoint goes under the Maya workspace — returned with original_file_status="no_original_file" and scene_rebound_to=null. Same-name checkpoints are rejected unless overwrite=True (the old file is preserved via rename). Honest bounds: the file contains no undo history — after scene_rollback, call scene_snapshot to rebuild context. References are flattened (self-contained, no write-back). Assumes one scene file per session.

NameTypeReqDescription
name––Checkpoint name (^[A-Za-z0-9_-]+$). Required when the scene was never saved to disk.
overwriteboolean–Replace a same-name checkpoint, preserving the old file.
session_key––Maya session key.
NameTypeReqDescription
resultstringyes–

No examples provided.

scene_checkpoint_list ~97

List all saved checkpoints for the current scene state. Boundary: Disambiguated from scene_checkpoint (save a new checkpoint) and scene_rollback (open one and point the scene at it) — scene_checkpoint_list only reads what is already on disk. Saved scenes list <scene_dir>/checkpoints; a scene never saved to disk lists the workspace checkpoints instead (adhoc flag per entry).

NameTypeReqDescription
session_key––Maya session key.
NameTypeReqDescription
resultstringyes–

No examples provided.

scene_describe ~369

API-level self-description of ONE node (not spatial). Boundary: scene_inspect answers WHERE an object is (position, bbox, neighbors); scene_nodes discovers candidate node names; scene_describe answers WHAT the node is at the API level - exact node type, per-attribute metadata, and connection wiring - so you can compose accurate execute_code/setAttr/connectAttr calls against real names.

NameTypeReqDescription
attrs––Attribute names to describe; None (default) lists every attribute listAttr reports UP TO the response budget (limit) - over-budget output is truncated and disclosed via attrs_truncated + total_count,…
include_connectionsboolean–Return connection wiring {src_plug, dst_plug, direction} (default True); the same budget applies (connections_truncated + total_connections; no cursor in v1 - narrow and re-query).
include_valuesboolean–Also return value + soft_min/soft_max per attr (default False). Reading a value can trigger DG evaluation inside Maya - still read-only, but the eval may cost time on heavy graphs.
limitinteger–Max items returned per face (attrs and connections). Soft default 200; a caller may relax explicitly to the hard cap 1000 - bounds response size only, not the per-attribute query cost.
nodestringyesNode name (short name or long DAG path).
session_key––Maya session key (auto-selected if one session).
NameTypeReqDescription
resultstringyes–

No examples provided.

scene_export ~277

Export the Maya scene (or named objects) to a local file. Writes through cmds.file with prompt=False forced (a modal dialog would hang the command channel). Formats: fbx, obj, usd (Alembic is not supported - its AbcExport API is not a cmds.file surface). The selection set is restored after every objects= export and the scene's modified flag is untouched. destructive_hint is False but note: overwrite=True permanently replaces the target file - that path is not recoverable.

NameTypeReqDescription
format––"fbx", "obj", or "usd". Optional when the path carries a recognizable extension; a missing extension is appended for an explicit format, and a conflicting extension+format pair is an error, never a g…
objects––Node names to export. None (default) exports the whole scene via exportAll; a list is pre-validated (any missing name aborts - no partial export) and drives exportSelected.
overwriteboolean–Replace an existing target file (default False).
pathstringyesTarget file path on the Maya host. Normalized and auto-parented (missing directories are created). An existing file is rejected unless overwrite=True.
session_key––Maya session key.
NameTypeReqDescription
resultstringyes–

No examples provided.

scene_inspect ~265

Deep inspection of a specific object or zone. Returns detailed properties including transform, BBox, material, mesh stats, and optionally nearby objects with distances. Object positions, box corners, sizes, neighbor distances and zone centers/boxes are in the scene's current linear unit (cm, m or mm). JSON object results name that unit. Centimetre output keeps its previous shape; non-centimetre zone results and the CoS view add the unit. An object's BBox is the node's own box, without its ancestors' transforms. The zone branch reports world-axis boxes built from each shape's own box transformed once, so a rotated parent no longer widens them layer by layer; geometry that does not fill its own box can still read up to one axis-alignment too wide. Boundary: Disambiguated from scene_snapshot (broad whole-scene spatial overview) and scene_describe (API-level attribute metadata, types, and connection wiring).

NameTypeReqDescription
formatstring–Output format - "cos" or "json".
include_neighborsboolean–Whether to include nearby objects (default True).
session_key––Maya session key.
targetstringyesObject name or zone name to inspect.
NameTypeReqDescription
resultstringyes–

No examples provided.

scene_measure ~638

Measure the spatial relationship between two objects. Call this in the compute step (the second of ICEV's four steps), to turn a spatial question into a number before you execute a change: size a clearance before moving something, prove two objects interpenetrate before you separate them, or get the axis detail behind an overlap that scene_validate reported. Read-only and idempotent: it queries world-space bounding boxes and never modifies the scene, so no checkpoint file is written. Requires an active Maya session. Every mode measures world-space AABBs, not the mesh surface and not the object origin. Each shape's own box is transformed once, so a rotated parent no longer widens the result layer by layer; geometry that does not fill its own box (an L-shape, a character mesh) can still measure up to one axis-alignment too wide. The modes differ in what the number means: center distance between the AABB midpoints. surface distance between the closest facing AABB corners — an axis-aligned approximation, so it over-reports clearance for rotated or concave geometry. clearance SIGNED, and 0 is NOT a "merely touching" signal. Per axis the gap is +separated / 0=touching / -penetrating: > 0 euclidean distance across the STRICTLY SEPARATED axes only. Penetrating axes contribute 0, so they are invisible in this number. = 0 no axis is strictly separated and at least one axis is exactly touching. The other axes may be deeply penetrating, so 0 does NOT mean the boxes just touch. < 0 all three axes penetrate; the value is the SHALLOWEST penetration depth, the minimum translation needed to pull them apart. bbox_overlap is true if and only if all three axes strictly penetrate. A single penetrating axis already makes it read false, so it can…

NameTypeReqDescription
formatstring–Output format - "cos" or "json".
modestring–What the returned number means — see the list above.
obj_astringyesFirst object name.
obj_bstringyesSecond object name.
session_key––Maya session key.
NameTypeReqDescription
resultstringyes–

No examples provided.

scene_nodes ~288

Bounded enumeration of scene nodes - including non-DAG nodes. Boundary: scene_snapshot is the low-resolution spatial overview you call once per workflow; scene_nodes is the name-discovery complement for the API layer - it lists nodes a spatial view never shows (materials, shadingEngines, tool nodes) and pages honestly: has_more/next_cursor tell you when the list was cut (for attribute schema and connection inspection, call scene_describe).

NameTypeReqDescription
cursor––Opaque page token from a previous call's next_cursor; valid while the scene is unchanged.
dag_onlyboolean–Only DAG nodes (transforms/shapes); False includes dependency nodes such as materials and utility nodes.
include_type_countsboolean–Also return per-type counts over the full match set (not just the page).
inheritedboolean–See type.
limitinteger–Page size (default 50, hard-capped at 100).
pattern––Maya glob pattern on names (e.g. "GEO_*").
session_key––Maya session key (auto-selected if one session).
type––Node type filter. With inherited=True (default) derived types match too (ls type= semantics, e.g. type="light" matches spotLight/directionalLight); inherited=False pins the exact type.
NameTypeReqDescription
resultstringyes–

No examples provided.

scene_plan ~537

Plan a scene layout: organization checks plus layout suggestions. Checks the scene and produces an actionable plan: - Organization check: finds orphan meshes, empty groups, default names - Zone analysis: coverage and spatial balance across zones - Layout suggestions: spacing, overlap, and clustering detection - Conflict prevention: predicts near-miss collisions - Action plan: prioritized step-by-step execution guide With recommend_assets=True, also recommends Poly Haven models across the built-in scene zones (entrance, display, furniture, lighting; shell, ip_core, and path are skipped with no search): reads fresh zone geometry (after auto_fix completes when auto_fix=True), resolves a target object per zone from objective (full DAG path, unique short name, or single measurable zone object; otherwise falls back to the zone's world-axis bounding box, built from shape boxes transformed once, so a rotated parent no longer widens it by layer), searches the models index in a worker thread under a 5s soft time budget reusing the 300s models index cache, checks words, deduplicates (capped at 3 per zone and 12 total), and screens candidates in metres (0.5x-1.5x per sorted axis for an object target; upper limit only for zone_bbox). Recommendations are advisory references — search only, no download and no import — and a search timeout, network failure (returning partial/offline status), or corrupt metadata never drops or changes the plan itself. Clearances and collisions are not verified. Blockout first: check organization and proportions before committing to detailed modeling. Accepts a plain-language objective. Boundary: Disambiguated from scene_review (scene_plan focuses on forward-looking layout planning and actionable auto_fix reorganization, whereas scene_review gives an overall diagnostic score).

NameTypeReqDescription
auto_fixboolean–If True, auto-fix safe issues (remove empty groups, reparent orphans).
formatstring–Output format - "json" (default) or "cos".
objectivestring–Natural language goal description. e.g., "set up entrance area with display window and clear circulation"
recommend_assetsboolean–If True, attach advisory Poly Haven model recommendations across the mapped built-in zones (entrance, display, furniture, lighting; shell/ip_core/path skipped) to the plan. This reaches the Poly Have…
session_key––Maya session key.
NameTypeReqDescription
resultstringyes–

No examples provided.

scene_render_preview ~369

Single-frame playblast preview from a camera (clean, no HUD). Boundary: Disambiguated from scene_viewport_snapshot (capture the panel as the artist sees it, HUD and selection highlights included) — scene_render_preview renders a chosen camera with the HUD suppressed. GUI sessions only - headless sessions get a structured gui_session_required error. Side-effect disclosures (read_only_hint is honest): 1. Switching the panel camera via the modelPanel camera flag is instantaneous, visible, and NOT undoable in Maya. 2. Everything is put back: the panel camera is restored on every path - success or failure - so terminal state equals entry. 3. The current time may visibly jump during capture; it is restored afterwards (playblast timeline quirk). 4. viewer=False: no playblast window pops up. 5. On failure the restore is still attempted; a failed restore is logged, never raised over the error result. 6. Only a killed Maya process can skip the restore.

NameTypeReqDescription
camera––Camera to look through (default: the panel's current camera).
formatstring–"jpeg" (default) or "png". png recommended for wireframe/line-art review.
heightinteger–Frame height (default 360). Same /4 rule.
max_sizeinteger–Longest-side cap for the returned image.
qualityinteger–JPEG quality 1-100.
session_key––Maya session key.
widthinteger–Frame width in pixels (default 640). Rounded UP to a multiple of 4 server-side (playblast constraint); the actual size may also be clamped by the viewport - trust the returned metadata, not the reque…

No output schema declared.

No examples provided.

scene_review ~257

Check a whole scene - all the aspects worth checking after operations. Runs spatial integrity, overlap detection, zone coverage, aesthetics, constraint validation, orphan detection, naming, componentization, conflicts, lighting quality, and scene organization. Returns a score (0-100) and detailed issue list. Checks you add in the Maya session with `_mcp_scene.register_validator(...)` (call it through execute_code) are reported in a separate "custom" section - `validators` per rule, `score`/`max_score` in weight points, `issues` for what did not pass. The built-in score is unchanged and the section is absent when nothing is registered. Boundary: Disambiguated from scene_validate (narrow rule-based spatial constraint checking) and scene_aesthetics (in-depth 5-dimension aesthetic theory scoring). Use this after any major scene modification to verify quality.

NameTypeReqDescription
checksstring–Comma-separated check names or "all". Options: spatial, overlaps, zones, aesthetics, constraints, orphans, naming, components, conflicts, lighting, organization
formatstring–Output format - "json" or "cos".
session_key––Maya session key.
NameTypeReqDescription
resultstringyes–

No examples provided.

scene_rollback ~487

Open a checkpoint file and point the scene at its original path (S2). Boundary: Disambiguated from scene_checkpoint (save a checkpoint from the current scene) and scene_checkpoint_list (list the ones already written) — scene_rollback is the read-back half. Before opening, the current scene is saved to a file first (auto_before_rollback); if that fails, the read-back aborts — pass discard_current_state=True to escape (the result reports safety_snapshot="skipped_by_user"). The scene points back only when it has a file path at read-back time; otherwise it stays on the checkpoint path (S1) and scene_rebound_to is null. The checkpoint file carries no undo history — call scene_snapshot afterwards to rebuild context. The result also says scene_modified_before: whether the scene still had changes that were never saved at the moment this call read the flag — a read of its own, just before the rollback request and before any file is opened. It is the same Maya flag scene_snapshot reports; after the open, that flag describes the checkpoint, not the scene being replaced. The value never changes what this tool does: a changed scene and a clean scene take the same path, and the copy written before the switch behaves exactly as before (safety_snapshot reports "skipped_by_user" only when discard_current_state lets a failed save through). The one new failure is Maya refusing to answer that question: the call then errors, with nothing opened yet, instead of printing a made-up "clean". That read is its own round trip, so it is worth saying what it covers when calls overlap: two scene_rollback calls for one session can each run their own read and their own switch. The value then describes the scene as it was at that read, which may be a scene the other call has already replaced. Nothing is gated by that difference, and scene_name_before still names the scene the rollback itself read (empty when the scene was never saved).

NameTypeReqDescription
discard_current_stateboolean–Escape hatch — proceed even if saving the current scene fails.
filenamestringyesCheckpoint filename from scene_checkpoint_list (cp_*.ma or prev_*.ma).
session_key––Maya session key.
NameTypeReqDescription
resultstringyes–

No examples provided.

scene_snapshot ~390

Get a complete spatial overview of the current Maya scene. Returns a structured description of ALL objects with positions, sizes, and types. Call this once at the start of each task to see the whole scene before changing it. Sizes are world-axis bounding boxes. Each shape's own box is transformed once, so a rotated parent no longer widens a size layer by layer; geometry that does not fill its own box (an L-shape, a character mesh) can still read up to one axis-alignment too wide. The first line ends with MODIFIED=y or MODIFIED=n. y means the scene has changes that were never saved; n means it has none. This is Maya's own flag for the whole scene, so it says nothing about which object changed. Changes made through this server's own tools count too, so y does not mean a person edited the scene. JSON output carries the same fact as the top-level scene_modified field. The flag is read again on every call and never comes from the cache, while the object list may be a few seconds old. Object positions, box corners and zone centers/boxes are in the scene's current linear unit (cm, m or mm); JSON and the CoS header name that unit. Boundary: Disambiguated from scene_inspect (deep-dive inspection of specific objects or zones) and scene_nodes (granular DAG/DG node name discovery with pagination).

NameTypeReqDescription
detailstring–Detail level - "compact" (fast), "standard" (+materials/mesh stats), "full" (+vertices).
formatstring–Output format - "cos" (CoS: short one-line-per-object text, compact) or "json" (full JSON).
session_key––Maya session key (auto-selected if only one session).
NameTypeReqDescription
resultstringyes–

No examples provided.

scene_validate ~274

Validate scene against spatial constraints. Checks the scene for constraint violations like minimum clearance, object limits, overlaps, and height requirements. This is a read-only check without auto_fix mutations (it cannot modify or repair objects; for automated fixes, see scene_plan with auto_fix=True). Because it is non-destructive, it needs no undo or rollback checkpoint. Requires an active Maya session. Boundary: Disambiguated from scene_review (a full check of scene quality across 11 checks) and scene_assert (verifies specific numeric values or object existence).

NameTypeReqDescription
formatstring–Output format - "cos" or "json".
rulesstringyesJSON string with constraint rules. Format: [{"type": "min_clearance", "zone": "entrance", "value": 180}, {"type": "max_objects", "value": 5000}, {"type": "no_overlap", "objects": ["wall_a", "shelf_…
session_key––Maya session key.
NameTypeReqDescription
resultstringyes–

No examples provided.

scene_viewport_snapshot ~227

Capture the active viewport as an image (WYSIWYG). Boundary: Disambiguated from scene_render_preview (playblast a frame from a chosen camera with the HUD suppressed) — scene_viewport_snapshot captures the panel exactly as the artist sees it, HUD included. GUI sessions only - headless (mayapy/batch/native-channel) sessions get a structured gui_session_required error. The capture is what the artist sees: viewport HUD, selection highlights and ornaments included. That is a feature - the agent verifies exactly what the user is looking at. A cmds.refresh(force=True) runs first so the frame is current.

NameTypeReqDescription
formatstring–"jpeg" (default, small) or "png". png recommended for wireframe/line-art review.
max_sizeinteger–Longest-side pixel cap for the returned image (default 800 - keeps base64 well under client image token limits).
qualityinteger–JPEG quality 1-100 (ignored for png).
session_key––Maya session key.

No output schema declared.

No examples provided.

write_module ~325

Create a virtual in-memory Python module in an active Maya session. Injects reusable Python functions into the target Maya session's sys.modules. Modules are virtual and in-memory: they do not persist across Maya restarts, and existing modules are protected unless overwrite=True is explicitly set. Requires an active Maya session. Under safe_mode (MAYA_MCP_SAFE_MODE, opt-in, default off) this code payload passes the same deny-by-default allowlist as execute_code: non-allowlisted imports, denied builtin names (any reference, not just calls), __builtins__ references, dunder attribute access, and unparseable input are rejected with safe_mode_rejected naming the triggering rule id. Successful responses carry mode: "safe" on their structured payload. Under the code allowlist, execute_code payloads can only import the v1 allowlisted roots, so a module defined here whose root is not one of those roots is not importable by name from allowlisted code. Boundary: Use write_module to define reusable libraries and helper functions; use execute_code for one-shot imperative execution or expression evaluation.

NameTypeReqDescription
codestringyesPython source code for the module.
namestringyesModule name. Can be a dotted path (e.g., 'mypackage.utils') in which case parent packages are created automatically.
overwriteboolean–If True, overwrite and replace existing module. If False, raise error if module already exists.
session_key––Maya session key (optional if only one active session exists).
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the mcp-for-maya server?

mcp-for-maya runs locally as a PyPI package, launched with uvx mcp-for-maya. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · mcp-for-maya

# add to Claude Code
claude mcp add xxx91n-mcp-for-maya -- uvx mcp-for-maya
Common questions

What is the mcp-for-maya server?

mcp-for-maya is listed in the public MCP registry as io.github.Xxx91n/mcp-for-maya. Spatial awareness for AI agents in Autodesk Maya: scene checks, checkpoints, captures (Beta). This page covers its PyPI package (mcp-for-maya).

Is the mcp-for-maya server safe to use?

mcp-for-maya scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the mcp-for-maya server expose?

mcp-for-maya exposes 25 tools: scene_snapshot, scene_inspect, scene_measure, scene_assert, scene_validate, and 20 more. Their descriptions and schemas cost roughly 7,272 tokens of context every time the server is loaded.

Is the mcp-for-maya server still maintained?

mcp-for-maya is still listed as active in the MCP registry. We last reached this channel on 22 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the mcp-for-maya server under?

mcp-for-maya declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the mcp-for-maya server?

VerifyMCP ran 16 checks on mcp-for-maya, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.