Maya MCP Server

Control Autodesk Maya scenes with 71 typed tools for modeling, animation, shading, and more.

Remote serverstreamable-httpPython

What is the Maya MCP MCP server?

Most developer tooling work still happens through a UI a human drives. Maya MCP MCP server moves it into the conversation instead. Control Autodesk Maya scenes with 71 typed tools for modeling, animation, shading, and more.

The short version

Maya MCP is an open-source, local Model Context Protocol server for controlling Autodesk Maya through Maya's commandPort.

  • runs outside Maya, so the server stays isolated from Maya imports
  • talks to Maya over localhost only
  • exposes 71 typed tools instead of raw API calls
  • supports safer scene replacement flows for unsaved changes
  • leaves raw code execution disabled unless you opt in

The tools it exposes

The server publishes 14 tools. What each one is for:

  • Family — Count
  • health — 1
  • maya — 2
  • scene — 9
  • nodes — 7
  • attributes — 2
  • selection — 6
  • connections — 5
  • mesh — 3
  • viewport — 1
  • modeling — 15
  • shading — 3

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

What it needs from you

Configuration is passed through the environment: PYTHONPATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Maya MCP's toolset — Family, health, maya and 11 more — is a fair guide to whether it matches your workflow. It is maintained by GimbalGoats; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Maya MCP.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
FamilyCount
health1
maya2
scene9
nodes7
attributes2
selection6
connections5
mesh3
viewport1
modeling15
shading3
skin6
animation6

How to install the Maya MCP MCP server

{
  "mcpServers": {
    "maya": {
      "command": "uvx",
      "args": ["maya-mcp"],
      "env": {
        "PYTHONPATH": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
PYTHONPATHFilesystem location the server is allowed to use.Optional

Example prompts to try

  • Use Maya MCP to Family.
  • Use Maya MCP to health.
  • Use Maya MCP to maya.

Frequently asked questions

It connects Maya MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (Family, health, maya, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Maya MCP directly.