DCC-MCP Core

Name: DCC-MCP Core
Author: dcc-mcp

by dcc-mcpversion 0.20.51i★ –iRuns on your computer

Registry nameio.github.dcc-mcp/dcc-mcp-core

Install

Overview

Description from the maker (original English)

Agent control plane for DCC and engine hosts: one MCP endpoint, one tool contract.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: Streamable HTTP
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: DCC_MCP_GATEWAY_PORT

You need

PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "dcc-core": {
      "command": "uvx",
      "args": [
        "dcc-mcp-server"
      ],
      "env": {
        "DCC_MCP_GATEWAY_PORT": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add dcc-core --env DCC_MCP_GATEWAY_PORT=your-value -- uvx dcc-mcp-server

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "dcc-core": {
      "command": "uvx",
      "args": [
        "dcc-mcp-server"
      ],
      "env": {
        "DCC_MCP_GATEWAY_PORT": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "dcc-core": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "dcc-mcp-server"
      ],
      "env": {
        "DCC_MCP_GATEWAY_PORT": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

DCC_MCP_GATEWAY_PORT env
Port the machine-wide gateway binds. One agent endpoint fronts every live DCC backend, so the port in the transport URL has to match this value.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account dcc-mcp, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32464 servers in this category
Published to the registry more recently than 79% of the other 32464 servers in this category
Basic checks equal to or better than 100% of the other 32464 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is DCC-MCP Core safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.20.51) reached the registry 9 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, yontu

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

yontu

by senrecep

Türkçe yazı denetimi: TDK kuralları, yapay zekâ izleri, metin türüne göre üslup.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

dcc-mcp-core

中文 | English

Website · Marketplace · Showcase · For Agents · Ecosystem

One MCP control plane for every DCC: an AI agent turns one prompt into a finished Blender material in 60 seconds.

pip install dcc-mcp-core

Try this → Blender material 60s Showcase: the shortest path from one prompt to a rendered material in a live Blender session, powered by dcc-mcp-blender. See Quick start: operate a DCC for the full CLI path.

Skill-first, Rust-powered control plane for a growing creative-tool ecosystem.

dcc-mcp-core connects agents to desktop DCCs, game engines, 2D tools, production systems, asset providers, profilers, and custom studio hosts through discoverable MCP and REST capabilities. It provides the gateway, Skills, structured results, main-thread dispatch, diagnostics, IPC, workflows, and packaged CLI/server binaries needed to operate real sessions.

One protocol, across every registered host. Every host adapter in this ecosystem implements the same MCP protocol and the same tool contract. The registry is the source of truth, and the count is reproducible from a checkout:

rg -c '^    tags: \[.*"adapter".*\]' dcc-mcp-catalog.yml

That reports 48 adapter entries in dcc-mcp-catalog.yml. See the complete generated host list for every current entry and its install metadata. The count includes experimental discovery-only PhotoCraft; it does not establish release-qualified support or automatic installation for every entry. Selected examples include:

Area	Selected hosts
Desktop DCC	Maya, Blender, Houdini, 3ds Max, Cinema 4D, Nuke, Katana, MotionBuilder, ZBrush, Mari, Substance 3D Designer, Substance 3D Painter, Marmoset
Engines and real-time	Unreal, Unity, Godot, Tiled, TouchDesigner
Design, image, video	Photoshop, Illustrator, GIMP, Krita, After Effects, Premiere, Kdenlive, PowerPoint, OBS, ComfyUI
CAD, procedural, interchange	FreeCAD, OpenSCAD, SketchUp, Material Maker, LiquiGen, OpenUSD
Production tracking and QA	Flow Production Tracking (ShotGrid), RenderDoc, Shogun, Wwise

The full list, with install metadata, is published in the ecosystem directory.

Three shared contracts keep it one matrix. Host coverage is only useful if the adapters stay interchangeable. Three contracts published by core are what stop host adapters from becoming unrelated servers:

Contract	What it guarantees	Where to verify
Core shared contract	One shared asset-import contract (`asset_import`), one discovery decision schema (`dcc-discovery-decision-v1`), and postcondition write-then-read-back so a tool proves its own result	`python/dcc_mcp_core/asset_import.py`, `contracts/dcc-discovery-decision-v1.schema.json`, `python/dcc_mcp_core/runtime/postcondition.py`
Recipe runtime	`recipes__list` / `recipes__get` / `recipes__validate` / `recipes__apply` driven by a declarative `RECIPES.yaml`, so a host ships capabilities as data instead of a bespoke server	`skills/mesh-ops/RECIPES.yaml`
Marketplace Skill contract	Every published entry carries `examplePrompts`; `Skills`, `Studio` and `Infrastructure` entries must also declare `recovery` and `undo`, so failures have a next step and edits have one rollback step	Enforced in dcc-mcp/marketplace by `validate_marketplace.py` — run `python scripts/validate_marketplace.py prompt-contract` (see `prompt-contract.md`)

How to compare us. Compare host coverage and contract completeness — both reproducible from the commands and files above. We do not claim a ranking, and we do not compare on stars or tool counts.

Features

Bundled agent skill. Every checkout and every release ships llms.txt — a compact index — and llms-full.txt, the full API reference. Both are machine-readable, so an agent can read them straight from the repository and start working without installing a Skill, browsing the marketplace, or scraping rendered docs.
Skills as the production unit. Ship capability as a versioned SKILL.md package with tools.yaml, progressive discovery, lint and schema validation, and hot reload (DccSkillHotReloader).
Main-thread dispatch. Actions are queued onto the DCC's main thread, so calls are safe against applications that crash when scripted off-thread.
Structured results and postconditions. Every call returns typed results, and the shared postcondition contract writes then reads back so a tool has to prove its own effect.
Multi-instance routing. One gateway fronts every live DCC session and publishes gateway://instances, so an agent talks to one endpoint no matter how many hosts are running.
UI Control as a fallback. For tools with no API at all, bounded screenshot-and-click automation brings them into the same control plane (DCC UI Control).

Choose your entry point

You want to…	Start with
Control a running DCC from an agent or CI job	Install the `dcc-mcp` Agent Skill, then use dcc-mcp-cli
Expose a DCC adapter over MCP/REST	create_skill_server
Start a server from a resolved package (Rez)	dcc-mcp-core serve
Add tools without Python registration code	SKILL.md + tools.yaml
Discover and install reusable Skills	DCC-MCP Marketplace
Build a new DCC adapter	new-adapter-onboarding.md
Understand routing and multi-instance behavior	gateway.md
Integrate from any HTTP client	rest-api-surface.md

The current contract

The default agent path is CLI + REST:

dcc-mcp-cli dcc-types (when adapter support is unclear)

-> list -> search -> describe -> load-skill (only when needed) -> call

The gateway keeps tools/list bounded. It advertises the canonical discovery/dispatch wrappers (search, describe, load_skill, and call) instead of fanning every backend tool into one large list. Backend capabilities are discovered by search, inspected by describe, and invoked through the wrapper or the REST twin (POST /v1/search, /v1/describe, /v1/call).

When a concrete DCC session is needed, read gateway://instances; each entry already includes its mcp_url. Do not use the removed legacy instance tools (list_dcc_instances, get_dcc_instance, or connect_to_dcc). Wrapper inputs belong inside arguments; do not put backend fields beside tool_slug.

For direct per-DCC MCP connections, the compatibility discovery names (search_tools, describe_tool, and call_tool) remain available where the server exposes them. New gateway integrations should use the canonical names above.

Why dcc-mcp-core exists

The shortest DCC agent demo asks a model to write and run a mayapy, hython, or Blender Python script. A production pipeline cannot depend on getting the right script from the model on every turn. Repeated code generation costs tokens, varies with the model and context, and leaves every adapter to rebuild transport, main-thread dispatch, validation, process lifecycle, routing, and diagnostics.

dcc-mcp-core moves that common engineering into one reusable control plane:

Layer	Reused capability
Integration	MCP and REST endpoints, Host RPC/IPC, typed schemas, resources, prompts, and structured results
DCC runtime	Main-thread affinity, readiness, multi-instance routing, async jobs, cancellation, checkpoints, workflows, artefacts, and UI Control
Skill delivery	`SKILL.md` packages, progressive discovery, lint/schema validation, hot reload, persistence, marketplace distribution, and project/team scopes
Operations	CLI, gateway, Admin UI, policies, audit records, traces, logs, metrics, health checks, and VRS replay

This project provides the infrastructure for agents to control DCC applications; it does not build or prescribe the agent itself. Agents and models will change, while studio interfaces, permission boundaries, and pipeline knowledge still need to be maintained. The framework turns those investments into reusable engineering assets.

Existing tools need AI access too

Adding an AI-facing interface to a new tool is usually straightforward. The harder problem is making years of existing tools usable by agents when they have no API, cannot be modified, or expose part of a workflow only through a window or modal dialog.

For that gap, dcc-mcp-core provides the bounded Computer Use-style DCC UI Control capability. It combines exact-window screenshots, semantic controls when available, scoped actions, waits, recording, policy checks, audit, and result verification. Native Skills/APIs remain the preferred path; UI Control lets legacy and interface-only workflows join the same agent control plane without pretending that every application has a clean programmable API.

MCP is an entry point, not the ceiling

MCP is the industry-standard agent interface we reuse, not the limit of the framework. A stable Python, C++, HTTP, command-port, or native plugin interface can be integrated under the same discovery, execution, safety, and operations contracts.

We also include useful vendor capabilities instead of replacing them. Unreal Engine 5.8 introduced an experimental built-in MCP server and Toolset Registry. The Unreal Official MCP Bridge enables and calls those official toolsets through DCC MCP without redistributing them. Vendor tools, DCC-MCP tools, and studio tools can share one agent-facing workflow.

Skills are the production unit

A Skill turns proven pipeline knowledge into a versioned, typed, testable, and distributable operation. A lower-cost model may struggle to invent scene-editing logic from scratch but remain effecti

Only the beginning is shown; read the rest in the repo

DCC-MCP Core

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

yontu

README from the maker

dcc-mcp-core

Features

Choose your entry point

The current contract

Why dcc-mcp-core exists

Existing tools need AI access too

MCP is an entry point, not the ceiling

Skills are the production unit