How your agent works with TextureCraft
Everything TextureCraft can do is a command in its own command registry: the same commands as its menus and shortcuts. Your agent finds them and runs them; it does not need a list from us in advance.
- Upload your file with
create_upload, then open it withtexture_open_document. - Read it with
texture_read_document. - Find the commands you need with
texture_list_commands, searching with a few words, and read their parameters. - Run them with
texture_run_command. If a command reports an error, adjust the parameters and run it again. - Save or export with a command, download the result with
texture_get_file, thentexture_close_document.
Tools
| Tool | Purpose |
|---|---|
texture_open_document | Start a private session: open an uploaded file, or a new blank document. Returns document_id and revision. |
texture_list_commands | List TextureCraft's commands, read live from the editor running in this session: every command id with its label and parameter documentation. Search with a few words or page through all of them. Free. |
texture_read_document | Read the current document in this session. |
texture_run_command | Run a command found with list_commands, with its documented parameters. Include the current revision and a unique request_id; a repeated request_id returns the first result instead of running twice. |
texture_quote | See what a request will cost before running it. |
texture_stage_file | Copy another uploaded file (an image, font, media or resource) into the session for a command that needs it. |
texture_get_file | Get a file the session produced (an export or saved copy) as a private download. |
texture_close_document | Close the session after downloading what you need. This ends its undo history. |
Long operations return a job_id: poll get_job until it finishes. Commands that need a desktop window, a printer, a local device or a local file path cannot run in a server session.
The website Agent
The AI Agent inside the TextureCraft editor works the same way, on the document you have open: it reads the document, lists commands, runs them, and your editor updates as it goes, with normal undo.
Resources and saved copies
Projects that reference media, fonts or other files need those files too: upload them and add each with texture_stage_file. Sessions can end on close, idle expiry or service restart, so download your results. MCP files are temporarily stored on EasyRunCraft servers for processing. They expire after 2 hours without activity on that file. Processing, file quotes, result retrieval and downloads renew the idle deadline. Ordinary chat and capability discovery do not. Active processing and transfers are protected from cleanup. Expired files cannot be accessed and are deleted automatically while the service is running; cleanup resumes on restart after an outage. Keep the downloaded edited results: local copies are not deleted by server expiry. Account and billing records are retained separately. You can ask your agent to delete a remote file version earlier.
Credits
Each successful MCP atomic operation costs 1 credit, including file inspection, editing, audio conversion, video export and animation rendering. One complete task may need several atomic operations. Credits are reserved before execution and charged only on success. Failed or cancelled tasks release the reservation. Uploads, quotes, capability checks, status polling and downloads have no separate charge. MCP credits pay for file processing, not AI model tokens. Your external agent’s model usage is billed by its provider.