How to create page images of documents for reports and tickets Leave feedback

Every rendered page is also saved to your output folder as <document>_page<N>.png. That makes the server a quick way to get page images for a ticket, a review note, or a slide.

Note

The commands and config snippets on this page are for the .NET build of the server — the only platform available today. Installation and client setup: MCP server for .NET. Other platforms will expose the same tools with their own launch command; everything else on this page applies unchanged.

Render pages 1, 4, and 9 of the specification and tell me where the files are.

The agent calls render_page three times. The files are named specification_page1.png, specification_page4.png, and specification_page9.png, so you can find them without asking.

• Bug reports — attach the page of the manual or the invoice that shows the problem.
• Document reviews — a thumbnail of each changed page in the review notes.
• Slides — a picture of the one diagram you want to show, without reformatting it.

Rendering is one page per call, and each image also travels back to the agent inline. Ask for the pages you need. If you only want the files, say so, so the agent does not describe every image:

Just save the images; you do not need to describe them.

Page numbers past the end still produce an image, named with the number you asked for. Check the page count with get_view_info first so a file called _page12.png really is page 12.

Evaluation-mode images carry a watermark. If the images leave your team, check get_license_status first.