MCP and agent tools

UI library · Desktop guide · Connected applications · Technical architecture

MCP lets an assistant discover and use tools exposed by Tech Connector, a DCC application, or another trusted service. It is optional. Direct application controls, Pipelines, and manual workflows continue to work without importing any external MCP server.

Quick start

1. Open File > Settings and find Source & Runtime.
2. Choose MCP Servers to open MCP and Agent Tools.
3. Choose Restore built-in MCP tools if the Tech Connector servers are missing. Existing imported servers are preserved.
4. Review the list. Configured means the definition is valid. It does not mean the application is currently open or connected.
5. Open the DCC or engine and its Tech Connector bridge. Use Apps > Capability Status... or the application's menu under Apps > DCC or Apps > Engine to confirm the live bridge.
6. Restart an active routed chat after changing the MCP configuration.
7. Ask Chat for a read-only check first. For example: Check Blender through MCP and tell me which scene is open.

The manager separates Tech Connector servers from Imported servers, identifies local and remote connections, and hides credential values. Use Open config folder when you need to inspect or back up the active file.

Built-in coverage

Tech Connector provides managed MCP definitions for its knowledge service and the supported DCC and engine bridges:

• Maya
• Unreal Engine
• Blender
• Houdini
• Unity
• MotionBuilder
• 3ds Max
• Substance 3D Painter
• Photoshop
• GIMP
• Godot

Each managed host exposes status, available operations, validation, and controlled execution appropriate to its real bridge. Python-capable hosts can also expose indexed project functions and native API discovery. Applications with command or remote transports use typed operations instead of claiming a Python API they cannot run.

The default Unreal server has additional project scan, project snapshot, asset inspection, and wrapper-generation tools. The common host facade is also available to integrations that need the shared catalog contract.

Useful first prompts

Start with inspection so you can confirm routing and connection state without changing a project:

• Check Maya through MCP. Report the connected session and current scene.
• List the Blender MCP operations related to export. Do not run anything.
• Search the indexed MotionBuilder tools for take creation and show the exact signature.
• Inspect the Unreal project through MCP and summarize the loaded project state.
• Tell me which MCP server and tool you would use for this request before running it.

For a change, name the host, target, and desired result. Tech Connector should show or request the required approval before a mutating tool runs. Inspect the resulting scene, asset, or file afterward.

What the labels mean

• Configured: the server definition has the fields needed to start or contact it.
• Needs attention: the definition is incomplete or cannot be translated safely.
• Local process: Tech Connector starts a trusted local command for the server.
• Remote server: the definition contacts a URL. Network availability and authentication are separate checks.
• Tech Connector: a built-in managed definition.
• Imported: a user-managed definition brought in from another client or configuration file.

Configuration validity is not live readiness. A host can be configured while Maya, Unreal, or another application is closed. A localhost port can also exist without a valid authenticated Tech Connector session. Use a status tool or Capability Status to confirm the live connection.

Import an existing setup

The manager detects common Claude Desktop, Claude, Cursor, GitHub Copilot, Windsurf, VS Code workspace, portable workspace, and Codex configurations. Select a detected setup and choose Import selected, or choose Choose file... for another JSON or TOML configuration.

Before import, Tech Connector asks you to trust the configuration because a local MCP server can start a program with your user permissions. Import behavior is conservative:

• Existing server names are preserved instead of overwritten.
• Invalid definitions are skipped and reported.
• Environment and header values are not displayed in the manager.
• A recoverable backup is created when the target configuration already exists.
• Imported servers remain available when built-in definitions are restored.

Restart an active routed chat after import so it receives the updated tool list.

Safety and approval

Read-only discovery is available without project mutation permission. A mutating built-in operation requires approval on that call and the installation policy TECH_CONNECTOR_MCP_ALLOW_MUTATION=1.

Native callable or arbitrary host-code execution also requires TECH_CONNECTOR_MCP_ALLOW_RAW_EXECUTION=1. Keep these policies disabled unless the MCP client, configuration, project, and requested operation are trusted. Prefer a registered typed operation when one exists.

Importing a server does not automatically grant it permission to edit a project. The server's own behavior and the client approval path still matter, so inspect third-party definitions before use.

Troubleshooting

A built-in server is missing

Open MCP and Agent Tools and choose Restore built-in MCP tools. Confirm the active configuration file shown in the window, then restart the routed chat.

The server says Configured, but Chat cannot reach the app

Open the application and its Tech Connector bridge. Check Apps > Capability Status.... If the status reports an open port but no verified session, restart or refresh the in-app bridge so it creates a current authenticated session.

Chat does not see newly imported tools

Restart the active routed chat. Tool discovery occurs when the MCP session starts, not every time a prompt is sent.

A call asks for approval

Read the requested host, operation, parameters, and target. Approve only if they match the intended change. If the installation policies are disabled, use a typed read-only action or ask the installation owner to review the policy.

A native API is not listed

Confirm that the host bridge supports Python execution and that the requested path is under an approved native namespace. Unity, Photoshop, GIMP, and Godot currently use their typed command transports rather than a Python namespace.

For integration developers

Every common host sidecar exposes shared tool families for status, sessions, operation catalogs, capability manifests, workflow catalogs, offline qualification, validation, and execution. It also exposes each registered typed operation as an individual MCP tool. Hosts with indexed project functions or live Python namespaces add catalog, schema, and controlled invocation tools.

See Host MCP integration for configuration, runtime scoping, policy variables, and server contracts.