dcc-mcp-marmoset
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@dcc-mcp-marmosetinspect the current Toolbag scene"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
dcc-mcp-marmoset
Typed DCC-MCP control for Marmoset Toolbag 4.03+ and 5.x. A pure-Python
Toolbag plugin executes mset calls on mset.callbacks.onPeriodicUpdate; an
external DccServerBase process owns MCP, discovery, jobs, and gateway
registration.
Install
python -m pip install dcc-mcp-marmosetIn Toolbag, choose Edit > Plugins > Show User Plugin Folder, copy that folder path, then run:
dcc-mcp-marmoset-install --plugin-dir "C:\path\shown\by\Toolbag"Choose Edit > Plugins > Refresh, then launch dcc_mcp_marmoset. The
plugin starts one host-bound adapter process per Toolbag process; relaunching
the plugin reuses that runtime. Toolbag requires one visible plugin window to
keep callbacks alive, so the adapter uses a single compact DCC-MCP lifetime
window. Closing it stops the plugin. See install.md for details.
Related MCP server: Maya MCP
Agent workflow
Shell-capable agents use the shared CLI:
dcc-mcp-cli list
dcc-mcp-cli search --query "inspect Toolbag scene" --dcc-type marmoset
dcc-mcp-cli load-skill marmoset-scene --dcc-type marmoset
dcc-mcp-cli search --query "inspect Toolbag scene" --dcc-type marmoset
dcc-mcp-cli describe <tool-slug>
dcc-mcp-cli call <tool-slug> --json '{"max_objects":500}'Use the exact slugs returned by search. IDE-only clients may connect to the
gateway MCP endpoint at http://127.0.0.1:9765/mcp.
Typed tools
marmoset_scene__pingmarmoset_scene__inspect_scenemarmoset_scene__import_modelmarmoset_scene__create_pbr_materialmarmoset_scene__set_visibilitymarmoset_scene__save_scenemarmoset_scene__render_camera
The adapter deliberately exposes no arbitrary Python execution. Its bridge is loopback-only, uses a per-launch random token, caps messages at 1 MiB, and expires queued requests before host mutation. Camera rendering is an async Core job backed by a monolithic Toolbag render call; check job/output state before retrying after a timeout.
Development
vx uv venv .venv --python 3.12
vx uv pip install --python .venv -e ".[dev]"
.venv\Scripts\python -m pytest
.venv\Scripts\python -m ruff check src tests tools
.venv\Scripts\python -m ruff format --check src tests tools
.venv\Scripts\python tools\lint_skills.pyThe host API contract follows Marmoset's official Python scripting guide and Toolbag 5 Python API reference.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/dcc-mcp/dcc-mcp-marmoset'
If you have feedback or need assistance with the MCP directory API, please join our Discord server