The MCP server creates products, versions, and representations in the AYON database, but does NOT copy source files to the project anatomy (the flat_simple publish directory on disk).
After ayon_publish_model succeeds, the agent must manually cp files into ~/Documents/projects_privat/.../publish/modelMain/v1/. This is a two-step workaround instead of a proper publish.
Impact
The MCP does not fulfill the complete publish workflow. Every publish requires an additional manual file copy step.
Proposed Fix
Add a file transfer mechanism (v0.4.0 File Bridge):
Accept a source_path parameter (local filesystem path to the FBX/texture file)
The server copies the file from source_path into the correct anatomy location
Or: accept file bytes via the MCP transport and write locally
Context
Three AYON publish methods exist:
Web UI drag-drop → copies to server storage (not anatomy)
REST API → metadata only (what MCP uses now)
Pyblish pipeline → copies to anatomy via ayon publish --file manifest.json
The MCP should implement option 3 or a direct anatomy write.
## Problem
The MCP server creates products, versions, and representations in the AYON database, but does NOT copy source files to the project anatomy (the flat_simple publish directory on disk).
After `ayon_publish_model` succeeds, the agent must manually `cp` files into `~/Documents/projects_privat/.../publish/modelMain/v1/`. This is a two-step workaround instead of a proper publish.
## Impact
The MCP does not fulfill the complete publish workflow. Every publish requires an additional manual file copy step.
## Proposed Fix
Add a file transfer mechanism (v0.4.0 File Bridge):
- Accept a `source_path` parameter (local filesystem path to the FBX/texture file)
- The server copies the file from `source_path` into the correct anatomy location
- Or: accept file bytes via the MCP transport and write locally
## Context
Three AYON publish methods exist:
1. Web UI drag-drop → copies to server storage (not anatomy)
2. REST API → metadata only (what MCP uses now)
3. Pyblish pipeline → copies to anatomy via `ayon publish --file manifest.json`
The MCP should implement option 3 or a direct anatomy write.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
The MCP server creates products, versions, and representations in the AYON database, but does NOT copy source files to the project anatomy (the flat_simple publish directory on disk).
After
ayon_publish_modelsucceeds, the agent must manuallycpfiles into~/Documents/projects_privat/.../publish/modelMain/v1/. This is a two-step workaround instead of a proper publish.Impact
The MCP does not fulfill the complete publish workflow. Every publish requires an additional manual file copy step.
Proposed Fix
Add a file transfer mechanism (v0.4.0 File Bridge):
source_pathparameter (local filesystem path to the FBX/texture file)source_pathinto the correct anatomy locationContext
Three AYON publish methods exist:
ayon publish --file manifest.jsonThe MCP should implement option 3 or a direct anatomy write.