FigCraft for your agent

Use FigCraft in your agent’s chat

1. Connect once. Follow the MCP setup instructions to add all 13 toolsets to your agent.
2. Provide the file. Give your agent a path it can read, or attach the file if your client supports uploads. The agent needs file access and HTTP transfer tools.
3. Describe the task. In your agent’s chat, say which file to use, what to do and what result you want. Your agent calls the connected tool and returns the information or output file.

What to ask your agent

After connecting, replace the example filename with your own file and send this in your agent’s chat:

List the frames in prototype.figcraft, then export the Checkout frame as PNG.

No special command or required brand phrase. If your agent chooses another method, ask it to use the connected EasyRunCraft tools. Review the result before continuing.

Supported operations

Use editor_capabilities with editor: "fig" to check supported operations. Pass the selected operation to process_fig.

inspect

List pages and top-level frames with their IDs and dimensions.

add_rectangle

Add one rectangle directly to the selected page. Provide the 1-based page number and x, y, width and height in pixels. Returns an editable FigCraft copy.

render_frame

Export one top-level frame as PNG. Pass its ID and the 1-based page number from inspection.

export_page_pdf

Export a page as a PDF. Visible top-level frames export as separate PDF pages. If there are no frames, the page content exports together.

Files, limits and results

Your assistant uses create_upload and sends the bytes to the upload URL with HTTP PUT. It then calls process_fig with the uploaded file ID and a new request_id. Reuse the request ID only to retry the same request.

Each input and output file can be up to 20 MB for accounts without a subscription and Starter, or 100 MB on Creator and Studio. See plan file limits. Each account can have two active jobs and each native command has a 45-second limit. Rectangle and PNG frame dimensions are limited to 4096 pixels per side. Export requires unique page names.

Poll get_job at most once per second. Inspection data is in result; downloadable outputs are in file. Edits create a private copy. Open the FigCraft editor.

Files and jobs expire after 24 hours. Upload and download links expire after 10 minutes. Anyone holding a valid link can use it until it expires.

Tool-call example for agents and developers

Your agent handles the tool calls. For a direct integration, the arguments to process_fig look like this:

{
  "file_id": "<uploaded file ID>",
  "request_id": "<new request ID>",
  "operation": {
    "type": "render_frame",
    "page": 1,
    "frame_id": 42
  }
}