RELATED 01
TouchDesigner MCP
OFFICIAL SERVERBuild, wire and inspect operators and set parameters inside a running TouchDesigner project
88GitHub stars
31popularity score
DCC-MCP Core
One local MCP gateway in front of Maya, Blender, Houdini, Unreal, Photoshop and other creative apps
By DCC-MCP Rust Local · Streamable HTTP DesignMedia
55 popularity score ★ 73 ↓ 45k/mo
Connect your client
Local (once it is running)
Add in one click
Opens the app, which asks before it adds the server.
Or add it by command or config
Claude CodeTerminal
claude mcp add --transport http dcc-core http://127.0.0.1:9765/mcpCursor~/.cursor/mcp.json
{
"mcpServers": {
"dcc-core": {
"url": "http://127.0.0.1:9765/mcp"
}
}
}VS Code.vscode/mcp.json
{
"servers": {
"dcc-core": {
"type": "http",
"url": "http://127.0.0.1:9765/mcp"
}
}
}Codex~/.codex/config.toml
[mcp_servers.dcc-core]
url = "http://127.0.0.1:9765/mcp"Gemini CLITerminal
gemini mcp add --scope user --transport http dcc-core http://127.0.0.1:9765/mcpSettings 8
DCC_MCP_GATEWAY_PORT |
Optional: Port the gateway binds; default 9765, must match the port in the client URL. |
|---|---|
DCC_MCP_GATEWAY_HOST |
Optional: Bind address of the gateway; default 127.0.0.1. |
DCC_MCP_GATEWAY_PERSIST |
Optional: Keep the gateway running when no backends are registered; default false. |
DCC_MCP_GATEWAY_IDLE_TIMEOUT_SECS |
Optional: Seconds before shutdown after the last backend exits; 30 for the gateway CLI. |
DCC_MCP_GATEWAY_REMOTE_HOST |
Optional: Bind address of the secondary LAN listener; default 127.0.0.1. |
DCC_MCP_GATEWAY_REMOTE_PORT |
Optional: Port of the secondary listener; default 59765, 0 disables it. |
DCC_MCP_NO_ADMIN |
Optional: Turn off the built-in Admin UI. |
DCC_MCP_CUA_ALLOW_RAW_INPUT |
Optional: Set false to stop UI control from sending raw coordinate input; on by default. |
What it does
DCC-MCP Core is the shared runtime behind a family of adapters for digital content creation tools, game engines and pipeline systems. The part that acts as an MCP server is the `dcc-mcp-server` binary, a Rust program shipped as a PyPI wheel. Run as `dcc-mcp-server gateway`, it opens one Streamable HTTP endpoint on the local machine (http://127.0.0.1:9765/mcp by default) and puts every live application session that has registered with it behind that endpoint.
The gateway does not execute tools itself. Instead of listing every backend tool, it offers four discovery and dispatch tools: an assistant searches the capabilities of the connected apps, inspects one, loads a skill when needed, and calls it; the call is forwarded over HTTP to the app that owns it. What can actually be done therefore depends on which per-app adapters (dcc-mcp-maya, dcc-mcp-blender and so on, installed separately) are running and which skills they carry. The project's catalog lists 47 adapter entries. Adapters can also expose a desktop UI control fallback (ui_control__snapshot, ui_control__act and related tools) that screenshots and clicks inside one bound application window.
The same gateway also serves a REST twin of the tools (/v1/search, /v1/describe, /v1/call), a local Admin UI at /admin with call logs, traces and stats, and LAN or relay setups for studios. Its makers point shell-capable agents at the separate dcc-mcp-cli as the preferred path, with MCP as one entry point.
A detail the README leaves out: a gateway started by hand shuts itself down 30 seconds after the last registered app exits (300 seconds when an adapter starts it), unless DCC_MCP_GATEWAY_PERSIST is set, so a client may find the endpoint gone between sessions (docs/guide/gateway.md).
What it needs
| Runtime | Python 3.7+ |
|---|
The dcc-mcp-server wheel from PyPI (Python 3.7+ to install; binaries for Linux x86_64 manylinux2014, Windows x86_64 and macOS universal2). The gateway must be started before a client connects, e.g. `dcc-mcp-server gateway --port 9765`, or it is started automatically by a running adapter. To do anything useful, at least one supported application (Maya, Blender, Unreal and so on) with its dcc-mcp adapter installed and running.
Limits
Speaks Streamable HTTP only; there is no stdio launch command for the gateway, so clients connect by URL. With no adapter registered there is nothing to search or call. A manually started gateway exits 30 s after the last backend leaves unless DCC_MCP_GATEWAY_PERSIST=1. Its makers state it cannot interrupt code already running on an app's main thread, cannot guarantee rollback for host APIs without transactions, and has no single lossless mesh, rig or material model across apps. The legacy tools list_dcc_instances, get_dcc_instance and connect_to_dcc have been removed. The CLI installer checks a SHA-256, which its makers note is an integrity check, not a signature.
Who it suits
Suits studios and technical directors who already run several DCC apps or engines and want one local endpoint, with audit logs and an admin view, through which an assistant can drive them using tested, versioned skills instead of generated scripts. It is a local, self-run setup with no account needed. For a single app, a dedicated adapter alone (we also hold dcc-mcp-maya, dcc-mcp-blender and others from the same makers) may be simpler; agents that can run shell commands are pointed by its makers to dcc-mcp-cli instead of MCP.
Tools 4
search- Find capabilities across all connected app sessions by query
describe- Show the schema and details of one backend tool
load_skill- Load a skill package on a backend so its tools become callable
call- Run a backend tool by its slug, forwarded to the app that owns it