Substance-3D-Designer-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sd_pingA | Report MCP, bridge, plugin, Designer version, session, and compatibility status. |
| sd_get_application_infoA | Read Designer version, Python, platform, open packages, graph, and capabilities. |
| sd_get_capabilitiesA | Read the runtime-probed capability matrix and verification status. |
| sd_list_packagesA | List packages currently open in Designer as structured references. |
| sd_save_packageA | Save one already-saved open package in place; never performs Save As. |
| sd_get_active_graphA | Read the current editable graph, package, node count, and selection count. |
| sd_list_graph_nodesB | List a bounded page of nodes from a structured graph reference. |
| sd_get_selectionB | Read the current graph node selection with a bounded result size. |
| sd_get_nodeA | Read one node by a structured current-session node reference. |
| sd_list_node_propertiesB | List runtime input and output properties, types, values, and connection state. |
| sd_create_nodeB | Create one verified atomic node at an explicit position without auto-connecting it. |
| sd_create_instance_nodeA | Create one instance from a resource returned by sd_search_library. |
| sd_move_nodesB | Move one to one hundred explicitly identified nodes to finite coordinates. |
| sd_delete_nodesA | Delete explicit nodes from one graph only when confirm is true. |
| sd_connect_nodesC | Connect explicit runtime properties after direction, type, and duplicate checks. |
| sd_disconnect_nodesC | Disconnect one explicit existing property connection. |
| sd_set_node_parameterC | Set a supported simple parameter after reading and validating its runtime SD type. |
| sd_search_libraryA | Search resources in currently loaded packages without UI scraping or guessed URLs. |
| sd_create_packageA | Create one unsaved Designer user package through the official package API. |
| sd_create_graphA | Create one empty compositing graph in an explicit open package. |
| sd_list_node_definitionsA | Search a bounded page of atomic definitions available in one graph. |
| sd_get_graph_snapshotA | Read a bounded versioned graph snapshot including explicit connections. |
| sd_open_graphC | Open one explicit graph resource in Designer's editor. |
| sd_create_graph_outputC | Create an Output node with explicit official usage metadata. |
| sd_save_package_asA | Save an open package to an absolute .sbs path after explicit confirmation. |
| sd_validate_graph_patchA | Dry-run a versioned additive graph patch without changing Designer. |
| sd_apply_graph_patchA | Apply a preflighted additive graph patch with rollback on failure. |
| sd_import_bitmapB | Import one existing local bitmap resource and optionally instantiate it. |
| sd_export_package_sbsarB | Export one saved package to .sbsar with explicit publication settings. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 29 tools
Most tools have clearly distinct resource-action pairs (e.g., create_node vs create_instance_node vs create_graph). However, sd_ping, sd_get_application_info, and sd_get_capabilities all report version/status/capability information, creating some overlap that could confuse an agent.
All tool names follow a consistent 'sd_verb_noun' snake_case pattern (e.g., sd_list_packages, sd_create_node, sd_delete_nodes). The only minor deviation is sd_get_active_graph using an adjective, but it still fits the pattern.
With 29 tools, this exceeds the 25+ threshold for 'too many' per the calibration. While the domain is broad, there is noticeable redundancy in info-gathering tools (ping, get_application_info, get_capabilities) and some niche tools (validate/apply_graph_patch) that could be consolidated or omitted.
The tool set covers the core lifecycle for packages, graphs, and nodes: create, read, update, delete, connect/disconnect, save, and export. Missing operations like package deletion, undo, or copy/paste are minor gaps that don't block primary workflows.