DeckCraft for your agent

Use DeckCraft 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:

Render slide 3 of kickoff.pptx and give me the 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: "deck" to check supported operations. Pass the selected operation to process_deck.

inspect

List slide titles, layouts, size and shape counts.

read_slide

Read one slide by its 1-based number, including its shapes and the exact plain speaker notes.

set_notes

Replace the speaker notes on one slide. Supply the exact current notes as expected_text. Use an empty string to clear the notes. Returns a new PPTX.

render_slide

Render one slide by its 1-based number at its native size as a PNG.

Files, limits and results

Your assistant uses create_upload and sends the bytes to the upload URL with HTTP PUT. It then calls process_deck 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. New notes and their expected text each accept up to 8,000 characters. Replacing notes uses plain text. Complex PowerPoint features and fonts can look different after saving or rendering; review the result.

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 DeckCraft 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_deck look like this:

{
  "file_id": "<uploaded file ID>",
  "request_id": "<new request ID>",
  "operation": {
    "type": "render_slide",
    "slide": 3
  }
}