Nova Creative

View saved version →

---
name: creative-workflows
description: Create and revise images, videos, talking avatars, audio, 3D and batch variations in saved Nova workflows through connected MCP tools. Use for Nova projects, assets, reviewed GPU rental and installation, usage approval, progress and cancellation.
---

# Nova Creative workflows

Use the connected Nova Creative MCP server and its existing result UI. Preserve the service's hosting and OAuth authentication. If connection is required, use the host's OAuth connection flow; never ask for passwords or copy access tokens into chat or files.

## MCP execution boundary

For Nova project, graph, asset, generation and run operations, call this installed plugin's connected MCP tools directly. A request to create, open, revise or monitor a Nova workflow is not a request to build a local app or operate the Nova website.

- Stay with the current agent and the user's selected chat model. Do not spawn subagents, hand the task to another model, or change host model settings for routine Nova work unless the user explicitly requests delegation or a model change. Choosing a supported image/video provider from Nova's catalog is a separate workflow setting, not a reason to switch the chat model.
- Do not open browser tabs/windows, use browser or desktop automation, navigate to Studio, or click website controls to perform or verify Nova operations. Return project/download links for the user to open. Opening a project means reading its saved workflow through MCP, not launching its URL.
- The host's native Nova confirmation cards and the editor returned by `object_editor_open` are supported MCP UI, not a browser fallback. Let the user interact with them; never automate their confirmation buttons or call their UI-only tools from model reasoning.
- Discover the actual Nova tool namespace/schemas and check `nova_status` when connection/readiness is uncertain. If tools are absent, disconnected, unsupported or return an error, report the specific MCP blocker and one supported next step. Do not substitute a browser, shell/curl/CLI, another MCP connection/account, direct provider calls, or a different image-generation tool.
- These are defaults for Nova operations. An explicit user request to open a website or use a browser for a separate task can authorize that scoped action; routine workflow creation, editing, status checks or troubleshooting do not imply that request.

## Resume without changing execution path

On a follow-up or after context compaction, continue through the same connected Nova MCP tools. Carry forward the selected project ID, saved revision, returned run ID and pending confirmation state. Reread the workflow before mutations and recheck the run before retrying. Do not interpret a context reset, a long wait, a project URL or a tool error as permission to start a browser session or delegate the task. If identifiers or connection evidence are missing, recover them with MCP or ask one concise question; do not guess or repeat generation.

## Reuse supplied references

Use `asset_list` to find references already uploaded to Nova; they do not need to be reattached to chat. Reuse the selected owned asset ID/URL, and resolve ambiguous filenames before choosing a reference.

For a newly selected file, follow the actual host schema of `asset_import`. Some hosts accept an absolute local `file` path and upload it for the tool; raw remote MCP expects the host-provided attachment object. Do not interchange these schemas or invent file IDs/download URLs. `asset_upload` accepts selected file bytes as base64 up to the live inline limit (currently 16 MB); attachment import currently allows up to 64 MB. Use `nova_capabilities` for current limits and supported media. The remote server itself never reads client disk paths. Persist the returned owned asset ID/URL, not a temporary attachment download URL.

For many files, use an exposed batch-upload tool only if this connected server supports it, otherwise import the selec

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 2 — file references are metadata, not package contents.